[Touch-packages] [Bug 1103353] Re: Invalid GnuTLS cipher suite strings causes libldap to crash
Kindly notice that the fix mentioned above for .40, was dated not quite a year ago. I'm not a ubuntu expert, but I think this page: https://launchpad.net/ubuntu/+source/openldap explains the fix mentioned above is not available as a backport for trusty, nor native in utopic, nor even being tested in vivid. Is it available on Ubuntu but I just missed it somehow? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1103353 Title: Invalid GnuTLS cipher suite strings causes libldap to crash Status in openldap package in Ubuntu: Triaged Status in openldap package in Debian: Fix Released Bug description: If the cipher suite string is unacceptable to GnuTLS, libldap_r-2.4 crashes due to a double free. GnuTLS is extremely picky about the cipher suite strings it accepts; as a first measure, try LDAP cipher suite string SECURE256 or NORMAL. If that stops the crash, then you have encountered this bug. Typically, the crash report begins with something like *** glibc detected *** APPLICATION: double free or corruption (!prev) /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7fc68cff0b96] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x38769)[0x7fc68bb13769] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x3570e)[0x7fc68bb1070e] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(ldap_pvt_tls_init_def_ctx+0x1d)[0x7fc68bb108ed] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x35965)[0x7fc68bb10965] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x35a6d)[0x7fc68bb10a6d] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(ldap_int_tls_start+0x5d)[0x7fc68bb1149d] The actual double free happens in openldap/libraries/libldap/tls2.c:ldap_int_tls_init_ctx(), in the ldap_pvt_tls_ctx_free(lo-ldo_tls_ctx); call in the error_exit: path. The root cause of the double free is lack of GnuTLS return value checks when calling gnutls_priority*() functions. The code simply assumes they succeed, and when GnuTLS fails to provide a valid context due to those failures, ldap_int_tls_init_ctx() tries to free the never-fully-initialized context. A simple fix is to create GnuTLS security contexts using the configured cipher suite string, instead of NORMAL as openldap/libraries/libldap/tls_g.c now does. If the cipher suite string is invalid, then do not create the context at all. This is caught earlier in ldap_int_tls_init_ctx(), and avoids the crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1103353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433666] [NEW] openldap won't install, aborts w/ double free each run
Public bug reported: Using root@email2:/tmp# dpkg -l | grep ldap ii ldap-utils 2.4.31-1+nmu2ubuntu8 amd64 OpenLDAP utilities ii libldap-2.4-2:amd64 2.4.31-1+nmu2ubuntu8 amd64 OpenLDAP libraries ii libldap-2.4-2-dbg:amd64 2.4.31-1+nmu2ubuntu8 amd64 Debugging information for OpenLDAP libraries ii libldap2-dev:amd64 2.4.31-1+nmu2ubuntu8 amd64 OpenLDAP development libraries ii php5-ldap 5.5.9+dfsg-1ubuntu4.6amd64 LDAP module for php5 root@email2:/tmp# dpkg -l | grep slapd iF slapd 2.4.31-1+nmu2ubuntu8 amd64 OpenLDAP server (slapd) iU slapd-dbg 2.4.31-1+nmu2ubuntu8 amd64 Debugging information for the OpenLDAP server (slapd) root@email2:/tmp# apt-get install fails when it first tries to run slapd. The installation aborts, incomplete. Using the debugger, here are the results: gdb /usr/sbin/openldap -h ldap://localhost:389/ -g openldap -u openldap -F /etc/ldap/slapd.d -d Any ... 55099a62 2.5.13.0 (objectIdentifierMatch): 55099a62 matchingRuleUse: ( 2.5.13.0 NAME 'objectIdentifierMatch' APPLIES ( supportedControl $ supportedExtension $ supportedFeatures $ supportedApplicationContext ) ) TLS: could not set cipher list HIGH+TLSv1. *** Error in `/usr/sbin/slapd': double free or corruption (top): 0x7f416ea278a0 *** Program received signal SIGABRT, Aborted. 0x7f416af92cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x7f416af92cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x7f416af960d8 in __GI_abort () at abort.c:89 #2 0x7f416afcf394 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f416b0ddb28 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/posix/libc_fatal.c:175 #3 0x7f416afdb66e in malloc_printerr (ptr=optimized out, str=0x7f416b0ddc38 double free or corruption (top), action=1) at malloc.c:4996 #4 _int_free (av=optimized out, p=optimized out, have_lock=0) at malloc.c:3840 #5 0x7f416c41ee11 in tlsg_ctx_free (ctx=0x7f416ea275a0) at tls_g.c:275 #6 0x7f416c41c058 in ldap_int_tls_init_ctx (lo=0x7f416e957428, is_server=optimized out) at tls2.c:245 #7 0x7f416c87a5ae in main (argc=optimized out, argv=0x7fff9189) at ../../../../servers/slapd/main.c:864 (gdb) This verion was installed over a previous openldap built against openssl. Gnutls//openlda should not crash the install because it doesn't like the formatting of an option string. Trusty lts ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: gnutls openssl slapd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1433666 Title: openldap won't install, aborts w/ double free each run Status in openldap package in Ubuntu: New Bug description: Using root@email2:/tmp# dpkg -l | grep ldap ii ldap-utils 2.4.31-1+nmu2ubuntu8 amd64OpenLDAP utilities ii libldap-2.4-2:amd64 2.4.31-1+nmu2ubuntu8 amd64OpenLDAP libraries ii libldap-2.4-2-dbg:amd64 2.4.31-1+nmu2ubuntu8 amd64Debugging information for OpenLDAP libraries ii libldap2-dev:amd64 2.4.31-1+nmu2ubuntu8 amd64OpenLDAP development libraries ii php5-ldap 5.5.9+dfsg-1ubuntu4.6 amd64LDAP module for php5 root@email2:/tmp# dpkg -l | grep slapd iF slapd 2.4.31-1+nmu2ubuntu8 amd64OpenLDAP server (slapd) iU slapd-dbg 2.4.31-1+nmu2ubuntu8 amd64Debugging information for the OpenLDAP server (slapd) root@email2:/tmp# apt-get install fails when it first tries to run slapd. The installation aborts, incomplete. Using the debugger, here are the results: gdb /usr/sbin/openldap -h ldap://localhost:389/ -g openldap -u openldap -F /etc/ldap/slapd.d -d Any ... 55099a62 2.5.13.0 (objectIdentifierMatch): 55099a62 matchingRuleUse: ( 2.5.13.0 NAME 'objectIdentifierMatch' APPLIES ( supportedControl $ supportedExtension $ supportedFeatures $ supportedApplicationContext ) ) TLS: could not set cipher list HIGH+TLSv1. *** Error in `/usr/sbin/slapd': double free or corruption (top): 0x7f416ea278a0 *** Program received signal SIGABRT, Aborted. 0x7f416af92cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56../nptl/sysdeps/unix/sysv/linux/raise.c: No such file
[Touch-packages] [Bug 1103353] Re: Invalid GnuTLS cipher suite strings causes libldap to crash
I just now noted the remark above suggesting the remedy to programs which crash abort when having a string parsing error is to not feed it strings it doesn't like. I suppose, mutatis mutandis, were the string one 99 of 100 leave defaulted it could be overlooked. However does anyone really think the string configuring the allowed ciphers isn't tweaked every few months in any serious deployment? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1103353 Title: Invalid GnuTLS cipher suite strings causes libldap to crash Status in openldap package in Ubuntu: Triaged Status in openldap package in Debian: Fix Released Bug description: If the cipher suite string is unacceptable to GnuTLS, libldap_r-2.4 crashes due to a double free. GnuTLS is extremely picky about the cipher suite strings it accepts; as a first measure, try LDAP cipher suite string SECURE256 or NORMAL. If that stops the crash, then you have encountered this bug. Typically, the crash report begins with something like *** glibc detected *** APPLICATION: double free or corruption (!prev) /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7fc68cff0b96] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x38769)[0x7fc68bb13769] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x3570e)[0x7fc68bb1070e] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(ldap_pvt_tls_init_def_ctx+0x1d)[0x7fc68bb108ed] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x35965)[0x7fc68bb10965] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x35a6d)[0x7fc68bb10a6d] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(ldap_int_tls_start+0x5d)[0x7fc68bb1149d] The actual double free happens in openldap/libraries/libldap/tls2.c:ldap_int_tls_init_ctx(), in the ldap_pvt_tls_ctx_free(lo-ldo_tls_ctx); call in the error_exit: path. The root cause of the double free is lack of GnuTLS return value checks when calling gnutls_priority*() functions. The code simply assumes they succeed, and when GnuTLS fails to provide a valid context due to those failures, ldap_int_tls_init_ctx() tries to free the never-fully-initialized context. A simple fix is to create GnuTLS security contexts using the configured cipher suite string, instead of NORMAL as openldap/libraries/libldap/tls_g.c now does. If the cipher suite string is invalid, then do not create the context at all. This is caught earlier in ldap_int_tls_init_ctx(), and avoids the crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1103353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1103353] Re: Invalid GnuTLS cipher suite strings causes libldap to crash
If this were a library used in a game or a bug in a screensaver I could see letting a formatting error in a string crash abort any program using the library sit for a year. I'm staggered really to experience this for a package as widely touted as gnutls, contending to be a replacement for openssl, and especially in a business supporting group like ubuntu that aims for site installs. I think this 11-month 'maintainers have higher priorities' event is a strong sign gnutls just is so not ready for mission critical deployment that whatever priority it may have on launchpad--- in the maintainers minds this is a 'might fix, won't deploy'. I've compiled it against openssl, and it's solid. Though I've stuck with ubuntu for many years now I have to agree with the sentiment upstream: this is a confidence buster. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1103353 Title: Invalid GnuTLS cipher suite strings causes libldap to crash Status in openldap package in Ubuntu: Triaged Status in openldap package in Debian: Fix Released Bug description: If the cipher suite string is unacceptable to GnuTLS, libldap_r-2.4 crashes due to a double free. GnuTLS is extremely picky about the cipher suite strings it accepts; as a first measure, try LDAP cipher suite string SECURE256 or NORMAL. If that stops the crash, then you have encountered this bug. Typically, the crash report begins with something like *** glibc detected *** APPLICATION: double free or corruption (!prev) /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7fc68cff0b96] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x38769)[0x7fc68bb13769] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x3570e)[0x7fc68bb1070e] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(ldap_pvt_tls_init_def_ctx+0x1d)[0x7fc68bb108ed] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x35965)[0x7fc68bb10965] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x35a6d)[0x7fc68bb10a6d] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(ldap_int_tls_start+0x5d)[0x7fc68bb1149d] The actual double free happens in openldap/libraries/libldap/tls2.c:ldap_int_tls_init_ctx(), in the ldap_pvt_tls_ctx_free(lo-ldo_tls_ctx); call in the error_exit: path. The root cause of the double free is lack of GnuTLS return value checks when calling gnutls_priority*() functions. The code simply assumes they succeed, and when GnuTLS fails to provide a valid context due to those failures, ldap_int_tls_init_ctx() tries to free the never-fully-initialized context. A simple fix is to create GnuTLS security contexts using the configured cipher suite string, instead of NORMAL as openldap/libraries/libldap/tls_g.c now does. If the cipher suite string is invalid, then do not create the context at all. This is caught earlier in ldap_int_tls_init_ctx(), and avoids the crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1103353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1103353] Re: Invalid GnuTLS cipher suite strings causeslibldapto crash
On 04/07/2015 01:32 PM, Oleg Strikov wrote: Client may crash itself by passing incorrect cipher suite to the API. While that's sad, it doesn't crash slapd itself To the contrary, it certainly does crash slapd itself. Anyone upgrading will at some point silently switch from a slapd that used openssl to gnutls --- without the package warning about nor updating the apropos config string. As a result, apt-get update;apt-get upgrade results in slapd crashing with a double free as it loads the previous conf file. Most package maintainers would refer to this as a regression inasmuch as the typical upgrade process fails to start and without any obvious warning. The answer may be found by spending many hours googling for 'what the heck'. For over a year this has gone unfixed. At least improve the upgrade script to warn the installer and prevent slapd from starting until some flag is set noting the user has corrected the string and is aware the developers won't fix the issue. In the alternative, I think a much better approach is to put a versions of all these and related packages compiled against openSSL in the appropriate repository. It is not material to me whether this is fixed or not as I've removed all packages using gnutls until it's more mature, and won't revisit this again for at least four years. In fact I'm looking for other distros like Mint that actually check whether upgrades generate regressions and classify risk assessments that allow only proven upgrades to succeed. It's really quite an eye-opener to me that a distro aiming to be deployed outside the sole-user world doesn't see this as a problem. -- Harry G Coin Quiet Fountain LLC 2118 Lundy Ln Bettendorf, Iowa 52722 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1103353 Title: Invalid GnuTLS cipher suite strings causes libldap to crash Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Precise: In Progress Status in openldap source package in Trusty: In Progress Status in openldap package in Debian: Fix Released Bug description: If the cipher suite string is unacceptable to GnuTLS, libldap_r-2.4 crashes due to a double free. GnuTLS is extremely picky about the cipher suite strings it accepts; as a first measure, try LDAP cipher suite string SECURE256 or NORMAL. If that stops the crash, then you have encountered this bug. Typically, the crash report begins with something like *** glibc detected *** APPLICATION: double free or corruption (!prev) /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7fc68cff0b96] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x38769)[0x7fc68bb13769] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x3570e)[0x7fc68bb1070e] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(ldap_pvt_tls_init_def_ctx+0x1d)[0x7fc68bb108ed] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x35965)[0x7fc68bb10965] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x35a6d)[0x7fc68bb10a6d] /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(ldap_int_tls_start+0x5d)[0x7fc68bb1149d] The actual double free happens in openldap/libraries/libldap/tls2.c:ldap_int_tls_init_ctx(), in the ldap_pvt_tls_ctx_free(lo-ldo_tls_ctx); call in the error_exit: path. The root cause of the double free is lack of GnuTLS return value checks when calling gnutls_priority*() functions. The code simply assumes they succeed, and when GnuTLS fails to provide a valid context due to those failures, ldap_int_tls_init_ctx() tries to free the never-fully-initialized context. A simple fix is to create GnuTLS security contexts using the configured cipher suite string, instead of NORMAL as openldap/libraries/libldap/tls_g.c now does. If the cipher suite string is invalid, then do not create the context at all. This is caught earlier in ldap_int_tls_init_ctx(), and avoids the crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1103353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473158] [NEW] /:pushd /tmp | echo is a no-op
Public bug reported: /:lsb_release -rd Description:Ubuntu 15.04 Release:15.04 /:apt-cache policy bash bash: Installed: 4.3-11ubuntu2 Candidate: 4.3-11ubuntu2 Version table: *** 4.3-11ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status /:bash --version GNU bash, version 4.3.30(1)-release (x86_64-pc-linux-gnu) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. /:popd bash: popd: directory stack empty /:pushd /tmp /tmp / /tmp:popd / /:pushd /tmp | cat /tmp / /: # !!! Pipe after pushd fails to change the current directory to /tmp /:popd bash: popd: directory stack empty ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1473158 Title: /:pushd /tmp | echo is a no-op Status in bash package in Ubuntu: New Bug description: /:lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 /:apt-cache policy bash bash: Installed: 4.3-11ubuntu2 Candidate: 4.3-11ubuntu2 Version table: *** 4.3-11ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status /:bash --version GNU bash, version 4.3.30(1)-release (x86_64-pc-linux-gnu) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. /:popd bash: popd: directory stack empty /:pushd /tmp /tmp / /tmp:popd / /:pushd /tmp | cat /tmp / /: # !!! Pipe after pushd fails to change the current directory to /tmp /:popd bash: popd: directory stack empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1473158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700319] Re: GTK3 menus don't work over SSH forwarding
I installed this patch on 3.22.10, it did not solve the problem of no menu entries listed when menu headings chosen in virt-manager. I also tried the latest upstream version, 3.22.21, which still has the same problem via x11 and no other time. The errors in the paste below occur when the "File" menu item is clicked once in the virt-manager via ssh / x11 forwarding (obviously it works locally). The relevant error is: (virt-manager:12201): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed a few times, followed by *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug [administrator@ceo1homenx ~]$ virt-manager --debug [Mon, 02 Oct 2017 20:51:21 virt-manager 12201] DEBUG (cli:261) Launched with command line: /usr/share/virt-manager/virt-manager --debug [Mon, 02 Oct 2017 20:51:21 virt-manager 12201] DEBUG (virt-manager:183) virt-manager version: 1.4.1 [Mon, 02 Oct 2017 20:51:21 virt-manager 12201] DEBUG (virt-manager:184) virtManager import: [Mon, 02 Oct 2017 20:51:23 virt-manager 12201] DEBUG (virt-manager:214) PyGObject version: 3.22.0 [Mon, 02 Oct 2017 20:51:23 virt-manager 12201] DEBUG (virt-manager:218) GTK version: 3.22.10 [Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (engine:496) libguestfs inspection support: False [Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (systray:156) Showing systray: False [Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (engine:1037) processing cli command uri= show_window= domain= [Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (engine:1039) No cli action requested, launching default window [Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (manager:203) Showing manager [Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (engine:401) window counter incremented to 1 [Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (engine:161) Loading stored URIs: qemu+ssh://administra...@noc1.ll.quietfountain.com/system qemu+ssh://administra...@noc1.ri.mamabosso.com/system qemu+ssh://administra...@noc2.ll.quietfountain.com/system qemu+ssh://administra...@noc2.ri.mamabosso.com/system qemu:///system [Mon, 02 Oct 2017 20:51:24 virt-manager 12201] DEBUG (engine:140) Initial gtkapplication activated (virt-manager:12201): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (virt-manager:12201): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (virt-manager:12201): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (virt-manager:12201): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (virt-manager:12201): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (virt-manager:12201): Gtk-WARNING **: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node arrow, owner GtkMenu) (virt-manager:12201): Gtk-WARNING **: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node arrow, owner GtkMenu) *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (virt-manager:12201): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkImageMenuItem) (virt-manager:12201): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkMenuItem) (virt-manager:12201): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkImageMenuItem) (virt-manager:12201): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkImageMenuItem) (virt-manager:12201): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (virt-manager:12201): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (virt-manager:12201): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (virt-manager:12201): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (virt-manager:12201): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (virt-manager:12201): Gtk-WARNING **: Negative content
[Touch-packages] [Bug 1700319] Re: GTK3 menus don't work over SSH forwarding
Just to be clear: This is a regression. It worked in 3.16. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1700319 Title: GTK3 menus don't work over SSH forwarding Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: When connecting remotely (either SSH X11 forwarding or direct to X11 server), drop down menus do not display properly. Bug upstream in gtk3: https://bugzilla.gnome.org/show_bug.cgi?id=780101 Client: Ubuntu 17.04 - gtk3-3.22.11-0ubuntu3 Server: Windows 10 Cygwin/X 1.19.2-1 Programs exhibiting this problem: evince 3.24.0 (and any other gtk3 apps with menus along the top). Patch applied to gtk3 in cygwin to fix this problem and attached to this post: https://github.com/cygwinports/gtk3/blob/master/3.22.10-xrandr12-compat.patch Console errors: (evince:7390): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner: assertion 'G_IS_DBUS_PROXY (proxy)' failed (evince:7390): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: The name org.freedesktop.portal.Desktop is not owned (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node arrow, owner GtkMenu) (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node arrow, owner GtkMenu) *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkModelMenuItem) (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkModelMenuItem) (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkModelMenuItem) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1700319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811159] [NEW] temporary freeze under opengl, not xrender, 18.10 & kernel 4.20
Public bug reported: Several times an hour, usually when switching focus from one window to another, all but the mouse will stop changing for a few seconds to a minute or so. If a video is playing the sound will proceed as if normal but the screen will not change. The shape of the mouse will not change. This is with stock ubuntu 18.10 under opengl with nouveau and i915 drivers active (xrandr). I tried using the latest possible ubuntu- compiled kernel, 4.20 with exactly the same results. This did not happen before sometime after the cosmic native initial install. When I change kde to 'xrender' -- the problem disappears. The oft reported dmesg content is: [83492.038575] WARNING: CPU: 2 PID: 2114 at drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x6d/0x80 [nouveau] [83492.038576] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter bpfilter cmac bnep bridge stp llc snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp i915 kvm_intel kvmgt vfio_mdev crct10dif_pclmul crc32_pclmul nouveau mdev vfio_iommu_type1 ghash_clmulni_intel vfio aesni_intel kvm aes_x86_64 crypto_simd snd_hda_codec_hdmi cryptd uvcvideo ttm glue_helper videobuf2_vmalloc snd_hda_intel irqbypass videobuf2_memops btusb intel_cstate drm_kms_helper snd_hda_codec snd_usb_audio videobuf2_v4l2 btrtl dell_wmi videobuf2_common dell_smbios btbcm snd_seq_dummy intel_rapl_perf btintel sparse_keymap drm dcdbas videodev dell_wmi_descriptor snd_seq_oss snd_usbmidi_lib snd_hda_core mxm_wmi media joydev input_leds 8250_dw wmi_bmof snd_seq_midi snd_hwdep snd_seq_midi_event bluetooth snd_pcm snd_rawmidi mei_me idma64 snd_seq snd_seq_device i2c_algo_bit [83492.038598] mei fb_sys_fops syscopyarea sysfillrect mac_hid virt_dma ecdh_generic sysimgblt snd_timer snd soundcore acpi_pad sch_fq_codel parport_pc ppdev lp sunrpc parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c hid_generic usbhid uas hid usb_storage alx i2c_i801 ahci mdio intel_lpss_pci libahci intel_lpss wmi pinctrl_sunrisepoint video pinctrl_intel [83492.038611] CPU: 2 PID: 2114 Comm: Xorg Not tainted 4.20.0-042000-generic #201812232030 [83492.038611] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.1.7 07/17/2018 [83492.038625] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau] [83492.038626] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 48 89 45 e8 e8 a1 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb f2 e8 ba c3 7e cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 [83492.038627] RSP: 0018:ba4a0308fbc0 EFLAGS: 00010282 [83492.038628] RAX: fffe RBX: ba4a0308fbf0 RCX: [83492.038629] RDX: 0010 RSI: ba4a0308fb30 RDI: ba4a0308fbd0 [83492.038629] RBP: ba4a0308fbe0 R08: c0d05b90 R09: [83492.038630] R10: 91cc290bd310 R11: 0030 R12: ba4a0308fc28 [83492.038630] R13: 91cc2bec60b0 R14: R15: 91cc290ba800 [83492.038631] FS: 7f5a5f2f0a80() GS:91cc2ea8() knlGS: [83492.038632] CS: 0010 DS: ES: CR0: 80050033 [83492.038633] CR2: 7f5a5800c000 CR3: 00043f42e003 CR4: 003606e0 [83492.038633] DR0: DR1: DR2: [83492.038634] DR3: DR6: fffe0ff0 DR7: 0400 [83492.038634] Call Trace: [83492.038659] nouveau_vma_del+0x75/0xc0 [nouveau] [83492.038682] nouveau_gem_object_close+0x1e0/0x1f0 [nouveau] [83492.038692] drm_gem_object_release_handle+0x34/0xa0 [drm] [83492.038698] drm_gem_handle_delete+0x61/0x90 [drm] [83492.038703] ? drm_gem_handle_create+0x40/0x40 [drm] [83492.038709] drm_gem_close_ioctl+0x25/0x30 [drm] [83492.038715] drm_ioctl_kernel+0xad/0xf0 [drm] [83492.038720] drm_ioctl+0x237/0x420 [drm] [83492.038726] ? drm_gem_handle_create+0x40/0x40 [drm] [83492.038728] ? do_iter_write+0xdd/0x190 [83492.038750] nouveau_drm_ioctl+0x73/0xc0 [nouveau] [83492.038752] do_vfs_ioctl+0xa9/0x640 [83492.038754] ? __sys_recvmsg+0x88/0xa0 [83492.038755] ksys_ioctl+0x67/0x90 [83492.038756] __x64_sys_ioctl+0x1a/0x20 [83492.038758] do_syscall_64+0x5a/0x110 [83492.038759] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [83492.038760] RIP: 0033:0x7f5a606273c7 [83492.038761] Code: 00 00 90 48 8b 05 c9 3a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 99 3a 0d 00 f7 d8 64 89 01 48 [83492.038762] RSP: 002b:7ffd2a2c6438 EFLAGS: 3246 ORIG_RAX: 0010 [83492.038763] RAX: ffda RBX: 555e65a090c0 RCX: 7f5a606273c7 [83492.038763] RDX: 7ffd2a2c6470 RSI: 40086409 RDI: 0012 [83492.038764] RBP: 7ffd2a2c6470 R08: 555e64a01d78 R09: 0001 [83492.038764] R10:
[Touch-packages] [Bug 1811159] Re: temporary freeze under opengl, not xrender, 18.10 & kernel 4.20
And... spoke too soon. It happens under xrender as well. Shorter freezes, frequency is the same. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1811159 Title: temporary freeze under opengl, not xrender, 18.10 & kernel 4.20 Status in xorg package in Ubuntu: New Bug description: Several times an hour, usually when switching focus from one window to another, all but the mouse will stop changing for a few seconds to a minute or so. If a video is playing the sound will proceed as if normal but the screen will not change. The shape of the mouse will not change. This is with stock ubuntu 18.10 under opengl with nouveau and i915 drivers active (xrandr). I tried using the latest possible ubuntu- compiled kernel, 4.20 with exactly the same results. This did not happen before sometime after the cosmic native initial install. When I change kde to 'xrender' -- the problem disappears. The oft reported dmesg content is: [83492.038575] WARNING: CPU: 2 PID: 2114 at drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x6d/0x80 [nouveau] [83492.038576] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter bpfilter cmac bnep bridge stp llc snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp i915 kvm_intel kvmgt vfio_mdev crct10dif_pclmul crc32_pclmul nouveau mdev vfio_iommu_type1 ghash_clmulni_intel vfio aesni_intel kvm aes_x86_64 crypto_simd snd_hda_codec_hdmi cryptd uvcvideo ttm glue_helper videobuf2_vmalloc snd_hda_intel irqbypass videobuf2_memops btusb intel_cstate drm_kms_helper snd_hda_codec snd_usb_audio videobuf2_v4l2 btrtl dell_wmi videobuf2_common dell_smbios btbcm snd_seq_dummy intel_rapl_perf btintel sparse_keymap drm dcdbas videodev dell_wmi_descriptor snd_seq_oss snd_usbmidi_lib snd_hda_core mxm_wmi media joydev input_leds 8250_dw wmi_bmof snd_seq_midi snd_hwdep snd_seq_midi_event bluetooth snd_pcm snd_rawmidi mei_me idma64 snd_seq snd_seq_device i2c_algo_bit [83492.038598] mei fb_sys_fops syscopyarea sysfillrect mac_hid virt_dma ecdh_generic sysimgblt snd_timer snd soundcore acpi_pad sch_fq_codel parport_pc ppdev lp sunrpc parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c hid_generic usbhid uas hid usb_storage alx i2c_i801 ahci mdio intel_lpss_pci libahci intel_lpss wmi pinctrl_sunrisepoint video pinctrl_intel [83492.038611] CPU: 2 PID: 2114 Comm: Xorg Not tainted 4.20.0-042000-generic #201812232030 [83492.038611] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.1.7 07/17/2018 [83492.038625] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau] [83492.038626] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 48 89 45 e8 e8 a1 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb f2 e8 ba c3 7e cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 [83492.038627] RSP: 0018:ba4a0308fbc0 EFLAGS: 00010282 [83492.038628] RAX: fffe RBX: ba4a0308fbf0 RCX: [83492.038629] RDX: 0010 RSI: ba4a0308fb30 RDI: ba4a0308fbd0 [83492.038629] RBP: ba4a0308fbe0 R08: c0d05b90 R09: [83492.038630] R10: 91cc290bd310 R11: 0030 R12: ba4a0308fc28 [83492.038630] R13: 91cc2bec60b0 R14: R15: 91cc290ba800 [83492.038631] FS: 7f5a5f2f0a80() GS:91cc2ea8() knlGS: [83492.038632] CS: 0010 DS: ES: CR0: 80050033 [83492.038633] CR2: 7f5a5800c000 CR3: 00043f42e003 CR4: 003606e0 [83492.038633] DR0: DR1: DR2: [83492.038634] DR3: DR6: fffe0ff0 DR7: 0400 [83492.038634] Call Trace: [83492.038659] nouveau_vma_del+0x75/0xc0 [nouveau] [83492.038682] nouveau_gem_object_close+0x1e0/0x1f0 [nouveau] [83492.038692] drm_gem_object_release_handle+0x34/0xa0 [drm] [83492.038698] drm_gem_handle_delete+0x61/0x90 [drm] [83492.038703] ? drm_gem_handle_create+0x40/0x40 [drm] [83492.038709] drm_gem_close_ioctl+0x25/0x30 [drm] [83492.038715] drm_ioctl_kernel+0xad/0xf0 [drm] [83492.038720] drm_ioctl+0x237/0x420 [drm] [83492.038726] ? drm_gem_handle_create+0x40/0x40 [drm] [83492.038728] ? do_iter_write+0xdd/0x190 [83492.038750] nouveau_drm_ioctl+0x73/0xc0 [nouveau] [83492.038752] do_vfs_ioctl+0xa9/0x640 [83492.038754] ? __sys_recvmsg+0x88/0xa0 [83492.038755] ksys_ioctl+0x67/0x90 [83492.038756] __x64_sys_ioctl+0x1a/0x20 [83492.038758] do_syscall_64+0x5a/0x110 [83492.038759] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [83492.038760] RIP: 0033:0x7f5a606273c7 [83492.038761] Code: 00 00 90 48 8b 05 c9 3a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff
[Touch-packages] [Bug 1843857] [NEW] IPMasquerade=yes -> ignored on eoan
Public bug reported: I'm testing out eoan, I have a [Network] section with IPMasquerade=yes. The system starts without complaint from systemd in the logs, but I see no evidence of source natting going on. I'm not sure of sub-dependencies, but I think source natting depends on libiptc-dev, which I don't see among the listings in eoan. I found Systemd-networkd updates 'iptables-legacy' with the source natting/masquerade detail -- which is disused by default. So it has no effect and doesn't throw an error. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1843857 Title: IPMasquerade=yes -> ignored on eoan Status in systemd package in Ubuntu: New Bug description: I'm testing out eoan, I have a [Network] section with IPMasquerade=yes. The system starts without complaint from systemd in the logs, but I see no evidence of source natting going on. I'm not sure of sub-dependencies, but I think source natting depends on libiptc-dev, which I don't see among the listings in eoan. I found Systemd-networkd updates 'iptables-legacy' with the source natting/masquerade detail -- which is disused by default. So it has no effect and doesn't throw an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1843857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
Just tried it three times, all normal, nothing in the logs except a few netfilter reports of correctly dropped packets. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd package in Ubuntu: New Bug description: Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-cosmic dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-cosmic:cvnQEMU:ct1:cvrpc-i440fx-cosmic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-cosmic dmi.sys.vendor: QEMU mtime.conffile..etc.systemd.resolved.conf: 2020-04-18T10:41:34.662328 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
This has been happening perhaps 3 times every 7 days, no obvious cause I can see. The system is a virtual machine that's just a router. No user activity, nobody logged in to the mate gui. Wish I had more to offer by way of a clue but that's it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd package in Ubuntu: New Bug description: Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-cosmic dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-cosmic:cvnQEMU:ct1:cvrpc-i440fx-cosmic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-cosmic dmi.sys.vendor: QEMU mtime.conffile..etc.systemd.resolved.conf: 2020-04-18T10:41:34.662328 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
crash log ** Attachment added: "_usr_lib_systemd_systemd.0.crash" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+attachment/5356610/+files/_usr_lib_systemd_systemd.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd package in Ubuntu: New Bug description: Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-cosmic dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-cosmic:cvnQEMU:ct1:cvrpc-i440fx-cosmic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-cosmic dmi.sys.vendor: QEMU mtime.conffile..etc.systemd.resolved.conf: 2020-04-18T10:41:34.662328 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873607] [NEW] systemd segv coredump, reboot/poweroff ignored.
Public bug reported: Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-cosmic dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-cosmic:cvnQEMU:ct1:cvrpc-i440fx-cosmic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-cosmic dmi.sys.vendor: QEMU mtime.conffile..etc.systemd.resolved.conf: 2020-04-18T10:41:34.662328 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd package in Ubuntu: New Bug description: Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2
[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
And again: root@noc1:~# Broadcast message from systemd-journ...@noc1.1.quietfountain.com (Tue 2020-04-28 12:32:15 CDT): systemd[1]: Caught , dumped core as pid 25084. Broadcast message from systemd-journ...@noc1.1.quietfountain.com (Tue 2020-04-28 12:32:15 CDT): systemd[1]: Freezing execution. root@noc1:~# from the syslog: Apr 28 12:31:46 noc1 rssmonitor.py[18369]: rssmain: Running: systemctl daemon-reload Apr 28 12:31:46 noc1 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Apr 28 12:31:46 noc1 systemd[1]: /lib/systemd/system/virtlockd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-sock → /run/libvirt/virtlockd-sock; please update the unit file accordingly. Apr 28 12:31:46 noc1 systemd[1]: /lib/systemd/system/virtlockd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-admin-sock → /run/libvirt/virtlockd-admin-sock; please update the unit file accordingly. Apr 28 12:31:46 noc1 systemd[1]: /lib/systemd/system/virtlogd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-sock → /run/libvirt/virtlogd-sock; please update the unit file accordingly. Apr 28 12:31:46 noc1 systemd[1]: /lib/systemd/system/virtlogd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-admin-sock → /run/libvirt/virtlogd-admin-sock; please update the unit file accordingly. Apr 28 12:31:46 noc1 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 28 12:31:46 noc1 systemd[1]: Reloading. Apr 28 12:31:46 noc1 kernel: [37890.433153] systemd[1]: segfault at 50 ip 55c2dd32d6f0 sp 7ffef173c7b0 error 4 in systemd[55c2dd2d4000+ae000] Apr 28 12:31:46 noc1 kernel: [37890.433172] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48> 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 28 12:31:47 noc1 rssmonitor.py[18369]: rssmain: Ran OK: systemctl daemon-reload The last entry means the systemctl daemon-reload command returned a normal 0 exit code. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd package in Ubuntu: Confirmed Bug description: Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output
Re: [Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
Still on eoan. Staying with Ubuntu depends on freeipa support. Presently only the freeipa client is supported past eoan, so the future is unclear. Can the fix be backported? On 5/13/20 3:03 PM, Dan Streetman wrote: > @hcoin are you still on Eoan or have you moved up to Focal yet? If > you're on Focal, could you test the version from -proposed? > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Bug description: [impact] during systemctl daemon-reload, systemd sometimes segfaults while serializing a service. [test case] problem is intermittent, but the upstream bug suggests a reproducer. Also see original description. [regression potential] this adjusts serialization, so any regression would likely occur during serialization/deserialization, e.g. at daemon-reload. [scope] This is needed for Bionic and later. this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41 which is included starting in v234. The commit to fix it is e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in any release. The PR to fix this is https://github.com/systemd/systemd/pull/15546 [other info] there is an additional PR that further avoids the error, but has not yet been accepted, and may not be accepted as it may not be necessary. https://github.com/systemd/systemd/pull/15370 [original description] Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output lines suppressed due to ratelimiting Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.7 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 18:09:06 2020 InstallationDate: Installed on 2019-11-01 (169 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcKernelCmdLine:
Re: [Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
Trying it now on 1 of 4 previously affected systems. Accepted all 'proposed' items, including changes to libvirt. Will advise. On 5/14/20 3:19 PM, Brian Murray wrote: > Hello Harry, or anyone else affected, > > Accepted systemd into eoan-proposed. The package will build now and be > available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.9 > in a few hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed. Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested, what testing has been > performed on the package and change the tag from verification-needed- > eoan to verification-done-eoan. If it does not fix the bug for you, > please add a comment stating that, and change the tag to verification- > failed-eoan. In either case, without details of your testing we will not > be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance for helping! > > N.B. The updated package will be released to -updates after the bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > ** Changed in: systemd (Ubuntu Eoan) > Status: In Progress => Fix Committed > > ** Tags added: verification-needed-eoan > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Bug description: [impact] during systemctl daemon-reload, systemd sometimes segfaults while serializing a service. [test case] problem is intermittent, but the upstream bug suggests a reproducer. Also see original description. [regression potential] this adjusts serialization, so any regression would likely occur during serialization/deserialization, e.g. at daemon-reload. [scope] This is needed for Bionic and later. this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41 which is included starting in v234. The commit to fix it is e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in any release. The PR to fix this is https://github.com/systemd/systemd/pull/15546 [other info] there is an additional PR that further avoids the error, but has not yet been accepted, and may not be accepted as it may not be necessary. https://github.com/systemd/systemd/pull/15370 [original description] Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl
Re: [Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
No issues so far. Thanks for checking. On May 20, 2020 5:30:40 PM CDT, Dan Streetman <1873...@bugs.launchpad.net> wrote: >@hcoin I assume no more segfaults with the updated pkg? can we mark >this verified for eoan? > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1873607 > >Title: > systemd segv coredump, reboot/poweroff ignored. > >Status in systemd: > Fix Released >Status in systemd package in Ubuntu: > Fix Released >Status in systemd source package in Bionic: > Fix Committed >Status in systemd source package in Eoan: > Fix Committed >Status in systemd source package in Focal: > Fix Committed >Status in systemd source package in Groovy: > Fix Released > >Bug description: > [impact] > > during systemctl daemon-reload, systemd sometimes segfaults while > serializing a service. > > [test case] > > problem is intermittent, but the upstream bug suggests a reproducer. > Also see original description. > > [regression potential] > > this adjusts serialization, so any regression would likely occur > during serialization/deserialization, e.g. at daemon-reload. > > [scope] > > This is needed for Bionic and later. > > this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41 > which is included starting in v234. The commit to fix it is > e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in > any release. > > The PR to fix this is https://github.com/systemd/systemd/pull/15546 > > [other info] > >there is an additional PR that further avoids the error, but has not >yet been accepted, and may not be accepted as it may not be necessary. > https://github.com/systemd/systemd/pull/15370 > > [original description] > > Proximate syslog: > >Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all >netns del >Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: >ListenStream= references a path below legacy directory /var/run/, >updating /var/run/dbus/system_bus_socket → /r > un/dbus/system_bus_socket; please update the unit file accordingly. >Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: >PIDFile= references a path below legacy directory /var/run/, updating >/var/run/sssd.pid → /run/sssd.pid; plea > se update the unit file accordingly. >Apr 18 16:26:56 gate2 systemd[1]: >/lib/systemd/system/oddjobd.service:6: PIDFile= references a path below >legacy directory /var/run/, updating /var/run/oddjobd.pid → >/run/oddjobd.p > id; please update the unit file accordingly. >Apr 18 16:26:56 gate2 systemd[1]: >/lib/systemd/system/fail2ban.service:12: PIDFile= references a path >below legacy directory /var/run/, updating >/var/run/fail2ban/fail2ban.pid → /r > un/fail2ban/fail2ban.pid; please update the unit file accordingly. >Apr 18 16:26:56 gate2 systemd[1]: >/lib/systemd/system/certmonger.service:6: PIDFile= references a path >below legacy directory /var/run/, updating /var/run/certmonger.pid → >/run/cer > tmonger.pid; please update the unit file accordingly. > Apr 18 16:26:56 gate2 systemd[1]: Reloading. >Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 >ip 55946ed0d6f0 sp 7fff8409d210 error 4 in >systemd[55946ecb4000+ae000] >Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 >ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 >17 66 2e 0f 1f 84 00 00 00 00 00 <48 > > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d >Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl >daemon-reload >Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl >enable rssmonitor.service > Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled >Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk: systemd: 43 output >lines suppressed due to ratelimiting >Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid >2034. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: systemd 242-7ubuntu3.7 > ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 > Uname: Linux 5.3.0-46-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.8 > Architecture: amd64 > Date: Sat Apr 18 18:09:06 2020 > InstallationDate: Installed on 2019-11-01 (169 days ago) >InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 >(20191017) > Lsusb: > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > MachineType: QEMU Standard PC (i440FX + PIIX, 1996) > ProcEnviron: > SHELL=/bin/bash > LANG=en_US.UTF-8 > TERM=xterm-256color > XDG_RUNTIME_DIR= > PATH=(custom, no user) >ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic >root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ >quiet
[Touch-packages] [Bug 1885024] [NEW] systemd patch fixes: krb5kdc.log Read-only file system
Public bug reported: Jun 24 11:29:34 registry1 krb5kdc[1244]: Couldn't open log file /var/log/krb5kdc.log: Read-only file system can be fixed by adding ReadWriteDirectories= /var/log to the krb5-kdc.service unit ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1885024 Title: systemd patch fixes: krb5kdc.log Read-only file system Status in krb5 package in Ubuntu: New Bug description: Jun 24 11:29:34 registry1 krb5kdc[1244]: Couldn't open log file /var/log/krb5kdc.log: Read-only file system can be fixed by adding ReadWriteDirectories= /var/log to the krb5-kdc.service unit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1885024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894902] Re: 2 apparmor items missing for 'groovy'
** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1894902 Title: 2 apparmor items missing for 'groovy' Status in apparmor package in Ubuntu: New Status in ntpsec package in Ubuntu: New Bug description: need to add ~# cat /etc/apparmor.d/local/usr.sbin.ntpd /run/systemd/userdb/io.systemd.Machine wr, /etc/ssl/openssl.cnf r, otherwise you get Sep 8 16:07:44 noc4 kernel: [ 1843.949193] audit: type=1400 audit(1599599264.140:52): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/systemd/userdb/io.systemd.Machine" pid=16851 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Sep 8 16:11:22 noc4 kernel: [ 2062.263356] audit: type=1400 audit(1599599482.449:138): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/etc/ssl/openssl.cnf" pid=17639 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1894902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
