[Touch-packages] [Bug 1931630] Re: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail
In #ubuntu-ser...@irc.libera.chat I was told to move this issue to *linux-image-kvm*. How can I do that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1931630 Title: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail Status in procps package in Ubuntu: New Bug description: *procps* ships `/etc/sysctl.d/10-magic-sysrq.conf:kernel.sysrq = 176`, which is run by `systemd-sysctl.service`. This fails on a system run with a Linux image built for virtual machines *linux-image-kvm*, which has `CONFIG_MAGIC_SYSRQ` not set. ``` $ sudo /lib/systemd/systemd-sysctl Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Couldn't write '4194304' to 'kernel/pid_max': Invalid argument $ grep SYSRQ /boot/config-5.4.0-1009-kvm # CONFIG_MAGIC_SYSRQ is not set ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1931630/+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 1931612] Re: Print dialog box shows same printer twice
** Package changed: ubuntu => cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice Status in cups package in Ubuntu: New Bug description: I have set up a single HP printer which is attached to my network. The setup process went smoothly, and when I open the Printers system setup panel, I see only my printer there. However, when I print from an application, and that application uses the system print dialog box, my printer appears twice. One entry, matching the name correctly, works fine. The other, which a slightly changed name, does not work at all. See attached screenshot. Applications that have their own print dialog box do not have this problem. For example, Firefox shows only my printer once. Same thing with Libre Office. Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+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 1931612] [NEW] Print dialog box shows same printer twice
You have been subscribed to a public bug: I have set up a single HP printer which is attached to my network. The setup process went smoothly, and when I open the Printers system setup panel, I see only my printer there. However, when I print from an application, and that application uses the system print dialog box, my printer appears twice. One entry, matching the name correctly, works fine. The other, which a slightly changed name, does not work at all. See attached screenshot. Applications that have their own print dialog box do not have this problem. For example, Firefox shows only my printer once. Same thing with Libre Office. Description:Ubuntu 20.04.2 LTS Release:20.04 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Print dialog box shows same printer twice https://bugs.launchpad.net/bugs/1931612 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. -- 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 1920836] Re: Show Extended Security Maintenence status
** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+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 1931609] Re: gstreamer1.0-plugins-bad compilation from sources: missing cuda.h
I could not reproduce this in my Xubuntu 20.04 VM, so I believe it more of a support request than an actual bug in the package. ** Changed in: gst-plugins-bad1.0 (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+question/697484 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1931609 Title: gstreamer1.0-plugins-bad compilation from sources: missing cuda.h Status in gst-plugins-bad1.0 package in Ubuntu: Invalid Bug description: Try to compile gst-plugins-bad1.0 from sources returns the error on Ubuntu 20.04 LTS: /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -fno-strict-aliasing -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-fvisibility=hidden -pthread -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -fdebug-prefix-map=/tmp/gst/gst-plugins-bad1.0-1.16.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-error -c -o libgstbluez_la-gstavrcputil.lo `test -f 'gstavrcputil.c' || echo './'`gstavrcputil.c In file included from nvcuvid.h:38, from gstnvdec.h:33, from gstnvdec.c:32: cuviddec.h:39:10: fatal error: cuda.h: File not found 39 | #include | ^~~~ compilation terminated Steps to reproduce: apt source gstreamer1.0-plugins-bad sudo apt install build-essential sudo apt build-dep gstreamer1.0-plugins-bad cd gst-plugins-bad1.0-1.16.2/ debuild -us -uc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gstreamer1.0-plugins-bad (not installed) ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Jun 10 18:06:15 2021 InstallationDate: Installed on 2018-04-05 (1162 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: gst-plugins-bad1.0 UpgradeStatus: Upgraded to focal on 2020-10-28 (225 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1931609/+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 1931630] [NEW] Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail
Public bug reported: *procps* ships `/etc/sysctl.d/10-magic-sysrq.conf:kernel.sysrq = 176`, which is run by `systemd-sysctl.service`. This fails on a system run with a Linux image built for virtual machines *linux-image-kvm*, which has `CONFIG_MAGIC_SYSRQ` not set. ``` $ sudo /lib/systemd/systemd-sysctl Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Couldn't write '4194304' to 'kernel/pid_max': Invalid argument $ grep SYSRQ /boot/config-5.4.0-1009-kvm # CONFIG_MAGIC_SYSRQ is not set ``` ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1931630 Title: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail Status in procps package in Ubuntu: New Bug description: *procps* ships `/etc/sysctl.d/10-magic-sysrq.conf:kernel.sysrq = 176`, which is run by `systemd-sysctl.service`. This fails on a system run with a Linux image built for virtual machines *linux-image-kvm*, which has `CONFIG_MAGIC_SYSRQ` not set. ``` $ sudo /lib/systemd/systemd-sysctl Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Couldn't write '4194304' to 'kernel/pid_max': Invalid argument $ grep SYSRQ /boot/config-5.4.0-1009-kvm # CONFIG_MAGIC_SYSRQ is not set ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1931630/+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 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
Just to put the information on the bug, I reproduced this failure on a Raspberry Pi, not a piece of the Scalingstack infrastructure in sight ;-) As far as I can tell it looked as if it's timing out waiting for network-online.target to become active. It seems as if installing network-manager makes the target take way longer to activate, so long that it is over autopkgtest's timeout. I suppose this isn't expected, so maybe the next step is to look into why that happens? -- 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/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) Status in Auto Package Testing: New Status in dnsmasq package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: Incomplete Status in glibc package in Ubuntu: Incomplete Status in isc-dhcp package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command ``` I have seen a bunch of packages including even gdm3 and glibc being blocked by that so I wanted to at least track down the issue until we can put it on someones task list to resolve. No one replied to my pings yet, but maybe that means someone is already debugging this and had enabled some debugging? By running the same in armhf container on arm64 VM on canonistack I've seen no issues. The test worked fine and had no hang/issues. root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services lxc 1 test_profile (__main__.AppArmorTest) AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352' test_help (__main__.CLITest) --help works and succeeds ... ok test_invalid_option (__main__.CLITest) Calling with invalid option fails ... ok test_version (__main__.CLITest) --version works and succeeds ... ok test_cpushares (__main__.CgroupsTest) service with CPUShares ... ok test_simple (__main__.CgroupsTest) simple service ... ok test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not work in containers' test_log_for_service (__main__.JournalTest) ... ok test_no_options (__main__.JournalTest) ... ok test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_failing (__main__.SeccompTest) ... ok test_0_init (__main__.ServicesTest) Verify that init is systemd ... ok test_cron (__main__.ServicesTest) ... ok test_dbus (__main__.ServicesTest) ... ok test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found' test_logind (__main__.ServicesTest) ... ok test_network_manager (__main__.ServicesTest) ... ok test_no_failed (__main__.ServicesTest) No failed units ... ok test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' -- Ran 23 tests in 5.589s OK (skipped=6) So I can not reproduce this on canonistack, but it blocks autopkgtests of various packages pretty reproducibly :-/ [1]: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+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 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
** Tags added: fr-1435 -- 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/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) Status in Auto Package Testing: New Status in dnsmasq package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: Incomplete Status in glibc package in Ubuntu: Incomplete Status in isc-dhcp package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command ``` I have seen a bunch of packages including even gdm3 and glibc being blocked by that so I wanted to at least track down the issue until we can put it on someones task list to resolve. No one replied to my pings yet, but maybe that means someone is already debugging this and had enabled some debugging? By running the same in armhf container on arm64 VM on canonistack I've seen no issues. The test worked fine and had no hang/issues. root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services lxc 1 test_profile (__main__.AppArmorTest) AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352' test_help (__main__.CLITest) --help works and succeeds ... ok test_invalid_option (__main__.CLITest) Calling with invalid option fails ... ok test_version (__main__.CLITest) --version works and succeeds ... ok test_cpushares (__main__.CgroupsTest) service with CPUShares ... ok test_simple (__main__.CgroupsTest) simple service ... ok test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not work in containers' test_log_for_service (__main__.JournalTest) ... ok test_no_options (__main__.JournalTest) ... ok test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_failing (__main__.SeccompTest) ... ok test_0_init (__main__.ServicesTest) Verify that init is systemd ... ok test_cron (__main__.ServicesTest) ... ok test_dbus (__main__.ServicesTest) ... ok test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found' test_logind (__main__.ServicesTest) ... ok test_network_manager (__main__.ServicesTest) ... ok test_no_failed (__main__.ServicesTest) No failed units ... ok test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' -- Ran 23 tests in 5.589s OK (skipped=6) So I can not reproduce this on canonistack, but it blocks autopkgtests of various packages pretty reproducibly :-/ [1]: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+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 1915502] Re: "systemd --user" fails to start for non-local users
The relevant upstream bug report afaics is https://github.com/systemd/systemd/issues/7074 Am Do., 10. Juni 2021 um 20:14 Uhr schrieb Michael Biebl : > > Am Do., 10. Juni 2021 um 14:50 Uhr schrieb Dan Streetman > <1915...@bugs.launchpad.net>: > > > > Ok, so it does sound like this and bug 1916235 are the same issue. And > > this might be 'as designed', since upstream systemd wants systemd-logind > > to talk to systemd-userdb instead of directly connecting to NIS servers; > > however Debian (and Ubuntu) disable systemd-userdb. > > > > @rbalint @ahasenack @mbiebl, since Debian/Ubuntu disable systemd-userdb, > > should we also adjust the systemd-logind RestrictAddressFamilies= > > restriction (and IPAddressDeny= and/or IPAddressAllow=) to allow > > networking? I'm not sure why ProtectHostname= would also be needed, but > > I assume it's related to the tighter restrictions on systemd-logind. > > I think the nis package should ship a drop-in config for > systemd-logind, allowing network access in systemd-logind. > This shouldn't be enabled globally for all users. > > As for ldap: If you use the new libpam-ldapd, there should be no > problem, as the network access is delegated to a separate process > (nscld). ** Bug watch added: github.com/systemd/systemd/issues #7074 https://github.com/systemd/systemd/issues/7074 -- 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/1915502 Title: "systemd --user" fails to start for non-local users Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Bug description: systemd-logind fails to start the systemd --user process for non-local users on Ubuntu 20.04. This is a reproducible problem; all our systems are displaying the same symptoms. The systems are using Kerberos (Active Directory) for authentication, and NIS for account meta-data and authorisation (groups) A base installation is performed using the server 20.04 ISO image. No additional packages are selected. Post-install, I run: apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd I set up the NIS client (supply the default domain name, check ypbind is running and ypcat passwd is working) I then set up /etc/krb5.conf for kerberos authentication to a domain controller, confirm that kinit works and a kerberos ticket is issued. I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to the end of each. /etc/nsswitch.conf is modified to support compat mode, as well as systemd: passwd: compat systemd group: compat systemd shadow: compat I can log in remotely via ssh using my NIS account and Kerberos credentials. MY NIS meta-data looks like: amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh (where UID and GID are replaced with values unique to the organisation) On login, the following occurs: hostname:~> systemctl --user Failed to connect to bus: No such file or directory I put pam-systemd and systemd-logind into debug mode to get more information: Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from [redact] port 58849 ssh2: RSA SHA256:[redact] Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened for user amcvey by (uid=0) Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CreateSession cookie=2 reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd initializing Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user desktop= seat= vtnr=0 tty= display= remote=yes remote_user= remote_host=10.105.121.110 Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41 reply_cookie=0 signature=s
Re: [Touch-packages] [Bug 1915502] Re: "systemd --user" fails to start for non-local users
Am Do., 10. Juni 2021 um 14:50 Uhr schrieb Dan Streetman <1915...@bugs.launchpad.net>: > > Ok, so it does sound like this and bug 1916235 are the same issue. And > this might be 'as designed', since upstream systemd wants systemd-logind > to talk to systemd-userdb instead of directly connecting to NIS servers; > however Debian (and Ubuntu) disable systemd-userdb. > > @rbalint @ahasenack @mbiebl, since Debian/Ubuntu disable systemd-userdb, > should we also adjust the systemd-logind RestrictAddressFamilies= > restriction (and IPAddressDeny= and/or IPAddressAllow=) to allow > networking? I'm not sure why ProtectHostname= would also be needed, but > I assume it's related to the tighter restrictions on systemd-logind. I think the nis package should ship a drop-in config for systemd-logind, allowing network access in systemd-logind. This shouldn't be enabled globally for all users. As for ldap: If you use the new libpam-ldapd, there should be no problem, as the network access is delegated to a separate process (nscld). -- 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/1915502 Title: "systemd --user" fails to start for non-local users Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Bug description: systemd-logind fails to start the systemd --user process for non-local users on Ubuntu 20.04. This is a reproducible problem; all our systems are displaying the same symptoms. The systems are using Kerberos (Active Directory) for authentication, and NIS for account meta-data and authorisation (groups) A base installation is performed using the server 20.04 ISO image. No additional packages are selected. Post-install, I run: apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd I set up the NIS client (supply the default domain name, check ypbind is running and ypcat passwd is working) I then set up /etc/krb5.conf for kerberos authentication to a domain controller, confirm that kinit works and a kerberos ticket is issued. I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to the end of each. /etc/nsswitch.conf is modified to support compat mode, as well as systemd: passwd: compat systemd group: compat systemd shadow: compat I can log in remotely via ssh using my NIS account and Kerberos credentials. MY NIS meta-data looks like: amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh (where UID and GID are replaced with values unique to the organisation) On login, the following occurs: hostname:~> systemctl --user Failed to connect to bus: No such file or directory I put pam-systemd and systemd-logind into debug mode to get more information: Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from [redact] port 58849 ssh2: RSA SHA256:[redact] Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened for user amcvey by (uid=0) Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CreateSession cookie=2 reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd initializing Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user desktop= seat= vtnr=0 tty= display= remote=yes remote_user= remote_host=10.105.121.110 Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to create session: No such process Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a
[Touch-packages] [Bug 1915502] Re: "systemd --user" fails to start for non-local users
Slightly odd behaviour with systemd version 245.4-4ubuntu3.6. In /etc/systemd/system/systemd-logind.service.d/override.conf I have: [Service] RestrictAddressFamilies=AF_INET IPAddressAllow=any On a cold boot I don't get the user session started: amcvey@ottub2004tst01:~$ systemctl --user Failed to connect to bus: No such file or directory But switching to root, running 'systemctl daemon-reload; systemctl restart systemd-logind' and then logging in again as a user account seems to work. I didn't make any changes to the config files, just restart the systemd components. If I then add ProtectHostname=no and reboot it seems to allow it to boot from cold without having to run systemctl daemon-reload; systemctl restart systemd-logind again. -- 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/1915502 Title: "systemd --user" fails to start for non-local users Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Bug description: systemd-logind fails to start the systemd --user process for non-local users on Ubuntu 20.04. This is a reproducible problem; all our systems are displaying the same symptoms. The systems are using Kerberos (Active Directory) for authentication, and NIS for account meta-data and authorisation (groups) A base installation is performed using the server 20.04 ISO image. No additional packages are selected. Post-install, I run: apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd I set up the NIS client (supply the default domain name, check ypbind is running and ypcat passwd is working) I then set up /etc/krb5.conf for kerberos authentication to a domain controller, confirm that kinit works and a kerberos ticket is issued. I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to the end of each. /etc/nsswitch.conf is modified to support compat mode, as well as systemd: passwd: compat systemd group: compat systemd shadow: compat I can log in remotely via ssh using my NIS account and Kerberos credentials. MY NIS meta-data looks like: amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh (where UID and GID are replaced with values unique to the organisation) On login, the following occurs: hostname:~> systemctl --user Failed to connect to bus: No such file or directory I put pam-systemd and systemd-logind into debug mode to get more information: Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from [redact] port 58849 ssh2: RSA SHA256:[redact] Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened for user amcvey by (uid=0) Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CreateSession cookie=2 reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd initializing Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user desktop= seat= vtnr=0 tty= display= remote=yes remote_user= remote_host=10.105.121.110 Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to create session: No such process Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to /run/systemd/userdb/io.systemd.Multiplexer: No such file or directory Feb 12 09:51:32 myhostname systemd-logind[903]: n/a: varlink:
[Touch-packages] [Bug 1915502] Re: "systemd --user" fails to start for non-local users
I can confirm the workaround is good for me too. I don't seem to need
the "ProtectHostname=no" option though, and in fact, the workaround in
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1916235 is also
now working as well. Looking at the test system I used today it's
running systemd 245.4-4ubuntu3.2, whereas the version I originally
tested was 245.4-4ubuntu3.4. I'll try updating to ...3.6 and see what
that does.
--
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/1915502
Title:
"systemd --user" fails to start for non-local users
Status in systemd package in Ubuntu:
Incomplete
Status in systemd source package in Focal:
Incomplete
Bug description:
systemd-logind fails to start the systemd --user process for non-local
users on Ubuntu 20.04. This is a reproducible problem; all our
systems are displaying the same symptoms.
The systems are using Kerberos (Active Directory) for authentication,
and NIS for account meta-data and authorisation (groups)
A base installation is performed using the server 20.04 ISO image. No
additional packages are selected. Post-install, I run:
apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd
I set up the NIS client (supply the default domain name, check ypbind
is running and ypcat passwd is working)
I then set up /etc/krb5.conf for kerberos authentication to a domain
controller, confirm that kinit works and a kerberos ticket is issued.
I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to
the end of each.
/etc/nsswitch.conf is modified to support compat mode, as well as
systemd:
passwd: compat systemd
group: compat systemd
shadow: compat
I can log in remotely via ssh using my NIS account and Kerberos
credentials. MY NIS meta-data looks like:
amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh
(where UID and GID are replaced with values unique to the
organisation)
On login, the following occurs:
hostname:~> systemctl --user
Failed to connect to bus: No such file or directory
I put pam-systemd and systemd-logind into debug mode to get more
information:
Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from
[redact] port 58849 ssh2: RSA SHA256:[redact]
Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened
for user amcvey by (uid=0)
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call
sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=CreateSession cookie=2
reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd
initializing
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking
logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user
desktop= seat= vtnr=0 tty= display= remote=yes remote_user=
remote_host=10.105.121.110
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session
limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a
runtime_max_sec=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to
create session: No such process
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to
/run/systemd/userdb/io.systemd.Multiplexer: No such file or directory
Feb 12 09:51:32 myhostname systemd-logind[903]: n/a: varlink: setting state
idle-client
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: Sending message:
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"uid":198083,"service":"io.systemd.DynamicUser"}}
Feb 12 09:51:32 myhostname systemd-logind[903]:
[Touch-packages] [Bug 1931609] [NEW] gstreamer1.0-plugins-bad compilation from sources: missing cuda.h
Public bug reported: Try to compile gst-plugins-bad1.0 from sources returns the error on Ubuntu 20.04 LTS: /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -fno-strict-aliasing -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-fvisibility=hidden -pthread -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -fdebug-prefix-map=/tmp/gst/gst-plugins-bad1.0-1.16.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-error -c -o libgstbluez_la-gstavrcputil.lo `test -f 'gstavrcputil.c' || echo './'`gstavrcputil.c In file included from nvcuvid.h:38, from gstnvdec.h:33, from gstnvdec.c:32: cuviddec.h:39:10: fatal error: cuda.h: File not found 39 | #include | ^~~~ compilation terminated Steps to reproduce: apt source gstreamer1.0-plugins-bad sudo apt install build-essential sudo apt build-dep gstreamer1.0-plugins-bad cd gst-plugins-bad1.0-1.16.2/ debuild -us -uc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gstreamer1.0-plugins-bad (not installed) ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Jun 10 18:06:15 2021 InstallationDate: Installed on 2018-04-05 (1162 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: gst-plugins-bad1.0 UpgradeStatus: Upgraded to focal on 2020-10-28 (225 days ago) ** Affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1931609 Title: gstreamer1.0-plugins-bad compilation from sources: missing cuda.h Status in gst-plugins-bad1.0 package in Ubuntu: New Bug description: Try to compile gst-plugins-bad1.0 from sources returns the error on Ubuntu 20.04 LTS: /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../../gst-libs -I../../gst-libs -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DGST_USE_UNSTABLE_API -fno-strict-aliasing -DG_THREADS_MANDATORY -DG_DISABLE_CAST_CHECKS -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wwrite-strings -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Wno-multichar -Wnested-externs -g-fvisibility=hidden -pthread -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -fdebug-prefix-map=/tmp/gst/gst-plugins-bad1.0-1.16.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-error -c -o libgstbluez_la-gstavrcputil.lo `test -f 'gstavrcputil.c' || echo './'`gstavrcputil.c In file included from nvcuvid.h:38, from gstnvdec.h:33, from gstnvdec.c:32: cuviddec.h:39:10: fatal error: cuda.h: File not found 39 | #include | ^~~~ compilation terminated Steps to reproduce: apt source gstreamer1.0-plugins-bad sudo apt install build-essential sudo apt build-dep gstreamer1.0-plugins-bad cd gst-plugins-bad1.0-1.16.2/ debuild -us -uc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gstreamer1.0-plugins-bad (not installed) ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
** Changed in: apt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
insighttoolkit4 - skip, ...orig-data.tar.xz
jdeb- skip, just creates compressed .deb packages
jmol- skip, just local data archive
jq - skip,
[Touch-packages] [Bug 1931582] Re: Add LOGO to /etc/os-release
** Changed in: base-files (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1931582 Title: Add LOGO to /etc/os-release Status in base-files package in Ubuntu: Triaged Status in base-files package in Debian: New Bug description: /etc/os-release can provide a logo file, this is now used by gnome- control-center to show the logo into the info panel. If ubuntu would provide its logo name in such file we would be able to remove the downstream patch that forces the usage of /usr/share/icons/vendor/scalable/emblems/emblem-vendor.svg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1931582/+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 1931582] [NEW] Add LOGO to /etc/os-release
Public bug reported: /etc/os-release can provide a logo file, this is now used by gnome- control-center to show the logo into the info panel. If ubuntu would provide its logo name in such file we would be able to remove the downstream patch that forces the usage of /usr/share/icons/vendor/scalable/emblems/emblem-vendor.svg ** Affects: base-files (Ubuntu) Importance: Medium Status: Triaged ** Affects: base-files (Debian) Importance: Unknown Status: Unknown ** Description changed: /etc/os-release can provide a logo file, this is now used by gnome- control-center to show the logo into the info panel. If ubuntu would provide its logo name in such file we would be able to remove the downstream patch that forces the usage of /usr/share/icons/vendor/scalable/emblems/emblem-vendor.svg - - This issue should be probably be opened in debian too ** Bug watch added: Debian Bug tracker #989690 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989690 ** Also affects: base-files (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989690 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1931582 Title: Add LOGO to /etc/os-release Status in base-files package in Ubuntu: Triaged Status in base-files package in Debian: Unknown Bug description: /etc/os-release can provide a logo file, this is now used by gnome- control-center to show the logo into the info panel. If ubuntu would provide its logo name in such file we would be able to remove the downstream patch that forces the usage of /usr/share/icons/vendor/scalable/emblems/emblem-vendor.svg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1931582/+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 1931578] [NEW] ActivationPolicy=down causes delay at boot
Public bug reported: [impact] The ActivationPolicy= parameter was backported in bug 1664844, but when this is set to down (or always-down or manual) without also specifying RequiredForOnline=no, then there is a hang at boot waiting for the network to finish coming online. [test case] With the latest systemd, which includes support for ActivationPolicy=, configure an interface with ActivationPolicy=down and reboot. The boot will be delayed waiting for that interface. [regression potential] any regression would likely cause the system to encounter delay at boot, or to boot before configured interface(s) are fully online at boot, or to fail to correctly/fully configure interface(s). [scope] this is needed for all releases this is proposed upstream in: https://github.com/systemd/systemd/pull/19883 [other info] this is only needed for convenience, as any configuration using ActivationPolicy=down can also easily add RequiredForOnline=no ** Affects: systemd (Ubuntu) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Bionic) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Focal) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Groovy) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Hirsute) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Impish) Importance: Low Assignee: Dan Streetman (ddstreet) Status: In Progress ** Description changed: [impact] The ActivationPolicy= parameter was backported in bug 1664844, but when this is set to down (or always-down or manual) without also specifying RequiredForOnline=no, then there is a hang at boot waiting for the network to finish coming online. [test case] With the latest systemd, which includes support for ActivationPolicy=, configure an interface with ActivationPolicy=down and reboot. The boot will be delayed waiting for that interface. [regression potential] any regression would likely cause the system to encounter delay at boot, or to boot before configured interface(s) are fully online at boot, or to fail to correctly/fully configure interface(s). [scope] this is needed for all releases + this is proposed upstream in: + https://github.com/systemd/systemd/pull/19883 + [other info] this is only needed for convenience, as any configuration using ActivationPolicy=down can also easily add RequiredForOnline=no ** Also affects: systemd (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Impish) Status: New => In Progress ** Changed in: systemd (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Impish) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Hirsute) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Hirsute) Status: New => In Progress ** Changed in: systemd (Ubuntu Impish) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Groovy) Status: New => In Progress ** Changed in: systemd (Ubuntu Groovy) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Low -- 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/1931578 Title: ActivationPolicy=down causes delay at boot Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: In Progress Status in systemd source package in Impish: In Progress Bug description: [impact] The
[Touch-packages] [Bug 1915502] Re: "systemd --user" fails to start for non-local users
Thanks for that. I can confirm that
systemctl daemon-reload; systemctl restart systemd-logind
(in that order) avoids the need for a reboot, and for a couple of my
machines I am very grateful for this information.
--
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/1915502
Title:
"systemd --user" fails to start for non-local users
Status in systemd package in Ubuntu:
Incomplete
Status in systemd source package in Focal:
Incomplete
Bug description:
systemd-logind fails to start the systemd --user process for non-local
users on Ubuntu 20.04. This is a reproducible problem; all our
systems are displaying the same symptoms.
The systems are using Kerberos (Active Directory) for authentication,
and NIS for account meta-data and authorisation (groups)
A base installation is performed using the server 20.04 ISO image. No
additional packages are selected. Post-install, I run:
apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd
I set up the NIS client (supply the default domain name, check ypbind
is running and ypcat passwd is working)
I then set up /etc/krb5.conf for kerberos authentication to a domain
controller, confirm that kinit works and a kerberos ticket is issued.
I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to
the end of each.
/etc/nsswitch.conf is modified to support compat mode, as well as
systemd:
passwd: compat systemd
group: compat systemd
shadow: compat
I can log in remotely via ssh using my NIS account and Kerberos
credentials. MY NIS meta-data looks like:
amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh
(where UID and GID are replaced with values unique to the
organisation)
On login, the following occurs:
hostname:~> systemctl --user
Failed to connect to bus: No such file or directory
I put pam-systemd and systemd-logind into debug mode to get more
information:
Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from
[redact] port 58849 ssh2: RSA SHA256:[redact]
Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened
for user amcvey by (uid=0)
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call
sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=CreateSession cookie=2
reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd
initializing
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking
logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user
desktop= seat= vtnr=0 tty= display= remote=yes remote_user=
remote_host=10.105.121.110
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session
limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a
runtime_max_sec=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to
create session: No such process
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to
/run/systemd/userdb/io.systemd.Multiplexer: No such file or directory
Feb 12 09:51:32 myhostname systemd-logind[903]: n/a: varlink: setting state
idle-client
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: Sending message:
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"uid":198083,"service":"io.systemd.DynamicUser"}}
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state idle-client
→ awaiting-reply
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: New incoming message:
[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
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/1930910
Title:
Fix micmute hotkeys on HP ProBooks
Status in HWE Next:
New
Status in systemd package in Ubuntu:
In Progress
Bug description:
[Impact]
Micmute hotkey on many HP ProBooks don't work.
[Fix]
Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT
keyboard's scancode to micmute hotkey.
[Test]
With the one-liner fix, micmute hotkey works on all the ProBooks I tested.
[Where problems could occur]
The hwdb originally only matches a few ProBooks, the fix changes that to
match all ProBook models. So if there's any ProBook that uses the scancode for
another purpose, there will be a regression.
However, the risk is rather slim because HP explicitly states that all
ProBooks use the same scancode for mic mute hotkey.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+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 1915502] Re: "systemd --user" fails to start for non-local users
Ok, so it does sound like this and bug 1916235 are the same issue. And this might be 'as designed', since upstream systemd wants systemd-logind to talk to systemd-userdb instead of directly connecting to NIS servers; however Debian (and Ubuntu) disable systemd-userdb. @rbalint @ahasenack @mbiebl, since Debian/Ubuntu disable systemd-userdb, should we also adjust the systemd-logind RestrictAddressFamilies= restriction (and IPAddressDeny= and/or IPAddressAllow=) to allow networking? I'm not sure why ProtectHostname= would also be needed, but I assume it's related to the tighter restrictions on systemd-logind. > I don't understand why daemon-reexec differs from rebooting. daemon-reload and daemon-reexec only affect pid 1; you need to actually (also) restart systemd-logind after making a change to its unit file; reloading/reexecing pid 1 won't change anything about the running systemd-logind. -- 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/1915502 Title: "systemd --user" fails to start for non-local users Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Bug description: systemd-logind fails to start the systemd --user process for non-local users on Ubuntu 20.04. This is a reproducible problem; all our systems are displaying the same symptoms. The systems are using Kerberos (Active Directory) for authentication, and NIS for account meta-data and authorisation (groups) A base installation is performed using the server 20.04 ISO image. No additional packages are selected. Post-install, I run: apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd I set up the NIS client (supply the default domain name, check ypbind is running and ypcat passwd is working) I then set up /etc/krb5.conf for kerberos authentication to a domain controller, confirm that kinit works and a kerberos ticket is issued. I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to the end of each. /etc/nsswitch.conf is modified to support compat mode, as well as systemd: passwd: compat systemd group: compat systemd shadow: compat I can log in remotely via ssh using my NIS account and Kerberos credentials. MY NIS meta-data looks like: amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh (where UID and GID are replaced with values unique to the organisation) On login, the following occurs: hostname:~> systemctl --user Failed to connect to bus: No such file or directory I put pam-systemd and systemd-logind into debug mode to get more information: Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from [redact] port 58849 ssh2: RSA SHA256:[redact] Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened for user amcvey by (uid=0) Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CreateSession cookie=2 reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd initializing Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user desktop= seat= vtnr=0 tty= display= remote=yes remote_user= remote_host=10.105.121.110 Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to create session: No such process Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname systemd-logind[903]:
[Touch-packages] [Bug 1916235] Re: systemd generates errors when using NSS and LDAP
*** This bug is a duplicate of bug 1915502 ***
https://bugs.launchpad.net/bugs/1915502
I believe this is a dup of bug 1915502, so marking as such
** This bug has been marked a duplicate of bug 1915502
"systemd --user" fails to start for non-local users
--
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/1916235
Title:
systemd generates errors when using NSS and LDAP
Status in systemd:
Fix Released
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Ubuntu 20.04.2 LTS
systemd 245.4-4ubuntu3.4
The system is configured to use LDAP via nsswitch.conf:
passwd: files systemd ldap
group: files systemd ldap
shadow: files ldap
gshadow:files
Using libnss-ldap 265-5ubuntu1. When logging in with ssh there is a
slight delay, and in the logs I see:
Feb 19 12:49:54 myserver sshd[105417]: Accepted publickey for mylogin from
1.2.3.4 port 60796 ssh2: RSA SHA256:somekey
Feb 19 12:49:54 myserver sshd[105417]: pam_unix(sshd:session): session opened
for user mylogin by (uid=0)
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: could not connect to any
LDAP server as (null) - Can't contact LDAP server
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: failed to bind to LDAP
server ldaps://myldapserver.mydomain/: Can't contact LDAP server
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: reconnecting to LDAP
server...
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: could not connect to any
LDAP server as (null) - Can't contact LDAP server
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: failed to bind to LDAP
server ldaps://myldapserver.mydomain/: Can't contact LDAP server
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: reconnecting to LDAP
server (sleeping 1 seconds)...
Feb 19 12:49:55 myserver systemd-logind: nss_ldap: could not connect to any
LDAP server as (null) - Can't contact LDAP server
Feb 19 12:49:55 myserver systemd-logind: nss_ldap: failed to bind to LDAP
server ldaps://myldapserver.mydomain/: Can't contact LDAP server
Feb 19 12:49:55 myserver systemd-logind: nss_ldap: could not search LDAP
server - Server is unavailable
Feb 19 12:49:55 myserver systemd-logind[105119]: New session 331 of user
mylogin.
With debugging for the systemd-logind process I can see the additional
information:
Feb 19 12:55:22 myserver systemd-logind[106567]: Failed to do shadow
lookup for UID 12345, ignoring: Bad file descriptor
And with strace I see:
stat("/etc/ldap.conf", {st_mode=S_IFREG|0644, st_size=9102, ...}) = 0
geteuid() = 0
socket(AF_INET, SOCK_STREAM, IPPROTO_IP) = -1 EAFNOSUPPORT (Address family
not supported by protocol)
fcntl(-1, F_SETFD, FD_CLOEXEC) = -1 EBADF (Bad file descriptor)
sendto(33, "<83>Feb 19 12:56:59 systemd-logind: nss_ldap: could not connect
to any LDAP server as (null) - Can't contact LDAP server", 120, MSG_NOSIGNAL,
NULL, 0) = 120
sendto(33, "<86>Feb 19 12:56:59 systemd-logind: nss_ldap: failed to bind to
LDAP server ldaps://myldapserver.mydomain/: Can't contact LDAP server", 131,
MSG_NOSIGNAL, NULL, 0) = 131
sendto(33, "<86>Feb 19 12:56:59 systemd-logind: nss_ldap: reconnecting to
LDAP server...", 76, MSG_NOSIGNAL, NULL, 0) = 76
Looking in /usr/lib/systemd/system/systemd-logind.service we see:
RestrictAddressFamilies=AF_UNIX AF_NETLINK
IPAddressDeny=any
So the problem is that systemd-logind can't open an AF_INET socket.
And additionally, it can't make any network connections.
This only occurs in 20.04. In 20.10 this is fixed by a newer systemd,
and it doesn't appear to be present in older systemd versions (at
least, I don't have an issue on 18.04).
The fix, from systemd 246, which is included in 20.10, is:
https://github.com/systemd/systemd/pull/15377
I have applied this change (which patches cleanly to the systemd
source package in 20.04) and the problem is resolved.
A temporary workaround for others experiencing this issue would be to
run "systemctl edit systemd-logind" and enter the following:
[Service]
RestrictAddressFamilies=AF_INET
IPAddressAllow=any
Then restart the systemd-login service, or reboot. Obviously this
could have other implications for the security of the system - I'm not
sure if processes launched by systemd-logind also have more relaxed
permissions.
It'd be great if the above patch could be applied to the package in
20.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1916235/+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 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- 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/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) Status in Auto Package Testing: New Status in dnsmasq package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: Incomplete Status in glibc package in Ubuntu: Incomplete Status in isc-dhcp package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command ``` I have seen a bunch of packages including even gdm3 and glibc being blocked by that so I wanted to at least track down the issue until we can put it on someones task list to resolve. No one replied to my pings yet, but maybe that means someone is already debugging this and had enabled some debugging? By running the same in armhf container on arm64 VM on canonistack I've seen no issues. The test worked fine and had no hang/issues. root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services lxc 1 test_profile (__main__.AppArmorTest) AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352' test_help (__main__.CLITest) --help works and succeeds ... ok test_invalid_option (__main__.CLITest) Calling with invalid option fails ... ok test_version (__main__.CLITest) --version works and succeeds ... ok test_cpushares (__main__.CgroupsTest) service with CPUShares ... ok test_simple (__main__.CgroupsTest) simple service ... ok test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not work in containers' test_log_for_service (__main__.JournalTest) ... ok test_no_options (__main__.JournalTest) ... ok test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_failing (__main__.SeccompTest) ... ok test_0_init (__main__.ServicesTest) Verify that init is systemd ... ok test_cron (__main__.ServicesTest) ... ok test_dbus (__main__.ServicesTest) ... ok test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found' test_logind (__main__.ServicesTest) ... ok test_network_manager (__main__.ServicesTest) ... ok test_no_failed (__main__.ServicesTest) No failed units ... ok test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' -- Ran 23 tests in 5.589s OK (skipped=6) So I can not reproduce this on canonistack, but it blocks autopkgtests of various packages pretty reproducibly :-/ [1]: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+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 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
Marking auto package testing as affected based on @paelzer's observation that it occurs only on Ubuntu's CI infra. I've also triggered the test with hello to see current status and for confirmation. ** Also affects: auto-package-testing 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/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) Status in Auto Package Testing: New Status in dnsmasq package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: Incomplete Status in glibc package in Ubuntu: Incomplete Status in isc-dhcp package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command ``` I have seen a bunch of packages including even gdm3 and glibc being blocked by that so I wanted to at least track down the issue until we can put it on someones task list to resolve. No one replied to my pings yet, but maybe that means someone is already debugging this and had enabled some debugging? By running the same in armhf container on arm64 VM on canonistack I've seen no issues. The test worked fine and had no hang/issues. root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services lxc 1 test_profile (__main__.AppArmorTest) AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352' test_help (__main__.CLITest) --help works and succeeds ... ok test_invalid_option (__main__.CLITest) Calling with invalid option fails ... ok test_version (__main__.CLITest) --version works and succeeds ... ok test_cpushares (__main__.CgroupsTest) service with CPUShares ... ok test_simple (__main__.CgroupsTest) simple service ... ok test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not work in containers' test_log_for_service (__main__.JournalTest) ... ok test_no_options (__main__.JournalTest) ... ok test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_failing (__main__.SeccompTest) ... ok test_0_init (__main__.ServicesTest) Verify that init is systemd ... ok test_cron (__main__.ServicesTest) ... ok test_dbus (__main__.ServicesTest) ... ok test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found' test_logind (__main__.ServicesTest) ... ok test_network_manager (__main__.ServicesTest) ... ok test_no_failed (__main__.ServicesTest) No failed units ... ok test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' -- Ran 23 tests in 5.589s OK (skipped=6) So I can not reproduce this on canonistack, but it blocks autopkgtests of various packages pretty reproducibly :-/ [1]: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+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 1931299] Re: package libfreetype6-dev:amd64 2.10.2+dfsg-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a rem
Your log shows you've had this problem for 2.5 months or so. A few pointers: `sudo apt autoremove' is the command - i.e. there should be no package names in the command. Try to fix your installation: sudo apt-get update --fix-missing sudo apt-get install -f -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1931299 Title: package libfreetype6-dev:amd64 2.10.2+dfsg-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in freetype package in Ubuntu: New Bug description: I just need help. I have broken packages that are refusing to be fixed, they are limiting me from installing any software or opting for updates and upgrades. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libfreetype6-dev:amd64 2.10.2+dfsg-3 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 8 18:22:24 2021 DpkgTerminalLog: Removing libxft-dev:amd64 (2.3.3-0ubuntu1) ... Removing libfontconfig1-dev:amd64 (2.13.1-2ubuntu3) ... dpkg: error processing package libfreetype6-dev:amd64 (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal DuplicateSignature: package:libfreetype6-dev:amd64:2.10.2+dfsg-3 Removing libfontconfig1-dev:amd64 (2.13.1-2ubuntu3) ... dpkg: error processing package libfreetype6-dev:amd64 (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2021-03-26 (74 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.6, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: freetype Title: package libfreetype6-dev:amd64 2.10.2+dfsg-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1931299/+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 1929647] Re: debian helper tools for python never updates
** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1929647 Title: debian helper tools for python never updates Status in python-debian package in Ubuntu: New Bug description: software updater prompts new updates debian helper tools for python is always one of them but I cannot select the checkbox so debian helper tools for python never updates Here's the screen shot https://i.imgur.com/AjDd5yo.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+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 1664844] Re: No distinction between link-up and link-down interfaces
On a hirsute multipass instance: $ apt-cache policy systemd systemd: Installed: 247.3-3ubuntu3.1 Candidate: 247.3-3ubuntu3.1 Version table: *** 247.3-3ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 Packages 100 /var/lib/dpkg/status I have tried all 5 combinations of the ActivationPolicy setting for a dummy interface and confirmed that those work as expected. Same as before, I also did a reboot while making sure RequiredForOnline is set to no and things seem to be working as expected. Verified! ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- 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/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Status in netplan.io source package in Focal: New Status in systemd source package in Focal: Fix Committed Status in netplan.io source package in Groovy: New Status in systemd source package in Groovy: Fix Committed Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: Fix Committed Bug description: [Impact] Since very long, we had a feature request in netplan to determine the activation mode of a given network interface. We got requests to enable marking some interfaces as 'manual', meaning that networkd (or any other backend) would not control its state in any way, requiring the administrator to bring the interface up or down manually. The other request was to mark a interface as 'off', that is: forcing the network interface to always be down until the configuration option isn't changed. This was mainly requested for the networkd backend and requires the new feature of specifying ActivationPolicy= for interfaces, alongside the required netplan changes. This feature is present in systemd 248 - for netplan supported stable series we have decided to cherry-pick and backport this feature on top of current systemd. The networkd feature basically adds the following 5 ActivationPolicy modes: always-down, down, manual, up, always-up. For netplan purposes we only use 'always-down' and 'manual'. The netplan feature, hopefully landing as part of 0.103, is called 'activation-mode' and supports two values: 'manual' and 'off'. [Test Case] For the systemd part: * Bring up a VM test environment with either a dummy interface or an interface that can be safely manipulated. * Upgrade systemd to the -proposed version * For the target interface, create/modify the networkd configuration to include the ActivationPolicy= setting in [Link], for instance: [Match] Name=dummy0 [Network] Address=192.168.10.30/24 Gateway=192.168.10.1 [Link] ActivationPolicy=manual * Try all 5 combinations of ActivationPolicy values: always-down, down, manual, up, always-up - doing `sudo networkctl reload` everytime and checking if the interface behaves as expected. [Where problems could occur] The patchset modifies quite a lot of code in the networkd link handling code paths, so regressions could appear in how networkd manages links - maybe by suddenly certain interfaces not getting brought up as they were before. By code inspection, the implementation defaults to ACTIVATION_POLICY_UP as the default, equivalent to the current behavior, so this risk is small. --- [Original Description] [Old Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Old Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Old Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no
[Touch-packages] [Bug 1664844] Re: No distinction between link-up and link-down interfaces
In the meantime, continuing on with the verification. On a groovy multipass instance: $ apt-cache policy systemd systemd: Installed: 246.6-1ubuntu1.4 Candidate: 246.6-1ubuntu1.4 Version table: *** 246.6-1ubuntu1.4 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status I have tried all 5 combinations of the ActivationPolicy setting for a dummy interface and confirmed that those work as expected. Reboot tested with RequiredForOnline=no set manually - all good. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- 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/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Status in netplan.io source package in Focal: New Status in systemd source package in Focal: Fix Committed Status in netplan.io source package in Groovy: New Status in systemd source package in Groovy: Fix Committed Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: Fix Committed Bug description: [Impact] Since very long, we had a feature request in netplan to determine the activation mode of a given network interface. We got requests to enable marking some interfaces as 'manual', meaning that networkd (or any other backend) would not control its state in any way, requiring the administrator to bring the interface up or down manually. The other request was to mark a interface as 'off', that is: forcing the network interface to always be down until the configuration option isn't changed. This was mainly requested for the networkd backend and requires the new feature of specifying ActivationPolicy= for interfaces, alongside the required netplan changes. This feature is present in systemd 248 - for netplan supported stable series we have decided to cherry-pick and backport this feature on top of current systemd. The networkd feature basically adds the following 5 ActivationPolicy modes: always-down, down, manual, up, always-up. For netplan purposes we only use 'always-down' and 'manual'. The netplan feature, hopefully landing as part of 0.103, is called 'activation-mode' and supports two values: 'manual' and 'off'. [Test Case] For the systemd part: * Bring up a VM test environment with either a dummy interface or an interface that can be safely manipulated. * Upgrade systemd to the -proposed version * For the target interface, create/modify the networkd configuration to include the ActivationPolicy= setting in [Link], for instance: [Match] Name=dummy0 [Network] Address=192.168.10.30/24 Gateway=192.168.10.1 [Link] ActivationPolicy=manual * Try all 5 combinations of ActivationPolicy values: always-down, down, manual, up, always-up - doing `sudo networkctl reload` everytime and checking if the interface behaves as expected. [Where problems could occur] The patchset modifies quite a lot of code in the networkd link handling code paths, so regressions could appear in how networkd manages links - maybe by suddenly certain interfaces not getting brought up as they were before. By code inspection, the implementation defaults to ACTIVATION_POLICY_UP as the default, equivalent to the current behavior, so this risk is small. --- [Original Description] [Old Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Old Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Old Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should
[Touch-packages] [Bug 1664844] Re: No distinction between link-up and link-down interfaces
Ok, after discussing with Dan, it seems we'll let this through as-is. Actually it's not entirely clear to me why this works differently with 248.3 on impish. We decided that currently, by design, this is 'expected behavior' and requires explicitly setting RequiredForOnline=no. Dan will propose an upstream patch to change that behavior though. >From the netplan side we'll make sure to do that. -- 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/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Status in netplan.io source package in Focal: New Status in systemd source package in Focal: Fix Committed Status in netplan.io source package in Groovy: New Status in systemd source package in Groovy: Fix Committed Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: Fix Committed Bug description: [Impact] Since very long, we had a feature request in netplan to determine the activation mode of a given network interface. We got requests to enable marking some interfaces as 'manual', meaning that networkd (or any other backend) would not control its state in any way, requiring the administrator to bring the interface up or down manually. The other request was to mark a interface as 'off', that is: forcing the network interface to always be down until the configuration option isn't changed. This was mainly requested for the networkd backend and requires the new feature of specifying ActivationPolicy= for interfaces, alongside the required netplan changes. This feature is present in systemd 248 - for netplan supported stable series we have decided to cherry-pick and backport this feature on top of current systemd. The networkd feature basically adds the following 5 ActivationPolicy modes: always-down, down, manual, up, always-up. For netplan purposes we only use 'always-down' and 'manual'. The netplan feature, hopefully landing as part of 0.103, is called 'activation-mode' and supports two values: 'manual' and 'off'. [Test Case] For the systemd part: * Bring up a VM test environment with either a dummy interface or an interface that can be safely manipulated. * Upgrade systemd to the -proposed version * For the target interface, create/modify the networkd configuration to include the ActivationPolicy= setting in [Link], for instance: [Match] Name=dummy0 [Network] Address=192.168.10.30/24 Gateway=192.168.10.1 [Link] ActivationPolicy=manual * Try all 5 combinations of ActivationPolicy values: always-down, down, manual, up, always-up - doing `sudo networkctl reload` everytime and checking if the interface behaves as expected. [Where problems could occur] The patchset modifies quite a lot of code in the networkd link handling code paths, so regressions could appear in how networkd manages links - maybe by suddenly certain interfaces not getting brought up as they were before. By code inspection, the implementation defaults to ACTIVATION_POLICY_UP as the default, equivalent to the current behavior, so this risk is small. --- [Original Description] [Old Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Old Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Old Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan
[Touch-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1087 https://gitlab.freedesktop.org/mesa/mesa/-/issues/1087 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/1087 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mesa: Unknown Status in Mir: Triaged Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Triaged Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1497593] Re: webbrowser-app crashed with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed.
Related upstream bugs: https://gitlab.freedesktop.org/mesa/mesa/-/issues/1087 https://gitlab.freedesktop.org/mesa/mesa/-/issues/1080 When I last hit this problem myself it was due to nouveau not being thread safe (last seen in Mir/Unity8 bug 1553328). ** Summary changed: - webbrowser-app crashed with SIGABRT in nouveau_pushbuf_data() + webbrowser-app crashed with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. ** Summary changed: - webbrowser-app crashed with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. + Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. ** Tags removed: wily ** Tags added: bionic ** Tags added: focal ** Tags added: hirsute ** Package changed: webbrowser-app (Ubuntu) => libdrm (Ubuntu) ** Summary changed: - Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. + [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1087 https://gitlab.freedesktop.org/mesa/mesa/-/issues/1087 ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1080 https://gitlab.freedesktop.org/mesa/mesa/-/issues/1080 ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Confirmed ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/1080 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1497593 Title: [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. Status in Mesa: Unknown Status in libdrm package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: webbrowser-app crashed with SIGABRT in __assert_fail_base() ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: webbrowser-app 0.23+15.10.20150913-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 19 20:05:51 2015 ExecutablePath: /usr/bin/webbrowser-app InstallationDate: Installed on 2015-09-18 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150918) ProcCmdline: webbrowser-app Signal: 6 SourcePackage: webbrowser-app StacktraceTop: __assert_fail_base (fmt=0x7f1aba6fd028 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f1aa469f879 "kref", file=file@entry=0x7f1aa469f85a "../../nouveau/pushbuf.c", line=line@entry=726, function=function@entry=0x7f1aa469f8a0 "nouveau_pushbuf_data") at assert.c:92 __GI___assert_fail (assertion=0x7f1aa469f879 "kref", file=0x7f1aa469f85a "../../nouveau/pushbuf.c", line=726, function=0x7f1aa469f8a0 "nouveau_pushbuf_data") at assert.c:101 nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 Title: webbrowser-app crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1497593/+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 1623507] Re: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear().
*** This bug is a duplicate of bug 1553328 *** https://bugs.launchpad.net/bugs/1553328 ** This bug is no longer a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. ** This bug has been marked a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1623507 Title: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear(). Status in Canonical System Image: New Status in Mir: Triaged Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: Triaged Bug description: 16.10 first unity 8 run ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-system-compositor 0.7.1+16.10.20160824-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Sep 14 10:34:45 2016 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. G92 [GeForce 9800 GT] [3842:c988] InstallationDate: Installed on 2016-09-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 7 ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: mir::fatal_error_abort(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libmircommon.so.6 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.70-1 version.lightdm: lightdm 1.19.4-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623507/+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 1595238] Re: Unity 8 Desktop Preview System Settings do not work on nouveau [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file ../../../src/ubuntumirclient/gl
*** This bug is a duplicate of bug 1553328 *** https://bugs.launchpad.net/bugs/1553328 ** This bug is no longer a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. ** This bug has been marked a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1595238 Title: Unity 8 Desktop Preview System Settings do not work on nouveau [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file ../../../src/ubuntumirclient/glcontext.cpp, line 239] Status in Canonical System Image: New Status in qtubuntu package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: When I try to open System Settings, the Ubuntu logo keeps turning and nothing happens. I installed unity8-desktop-session-mir on my Xenial 16.04.1 Desktop where I use NVIDIA driver GF108[GeForce GT 530]. I also created a new user account with English (US) language settings, because Unity 8 does not work well when I use my own account with my language settings. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595238/+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 1623508] Re: unity8 crashed with SIGSEGV
*** This bug is a duplicate of bug 1553328 *** https://bugs.launchpad.net/bugs/1553328 ** This bug is no longer a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. ** This bug has been marked a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1623508 Title: unity8 crashed with SIGSEGV Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: 16.10 first unity 8 run16.10 first unity 8 run ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity8 8.14+16.10.20160831.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Sep 14 10:32:07 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2016-09-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) ProcCmdline: unity8 --mode=full-shell Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1623508/+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 1672793] Re: unity-system-compositor crashed with SIGSEGV
*** This bug is a duplicate of bug 1553328 *** https://bugs.launchpad.net/bugs/1553328 ** This bug is no longer a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. ** This bug has been marked a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1672793 Title: unity-system-compositor crashed with SIGSEGV Status in Unity System Compositor: New Status in unity-system-compositor package in Ubuntu: New Bug description: I just got this on the first login to my new Ubuntu user profile ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: unity-system-compositor 0.9.1+17.04.20170216-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Tue Mar 14 20:14:24 2017 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2013-09-15 (1275 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 13 --to-dm-fd 22 --vt 8 ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f8dc76dd07f:mov0x8(%r15),%edx PC (0x7f8dc76dd07f) ok source "0x8(%r15)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-system-compositor StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so Title: unity-system-compositor crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.75-1ubuntu1 version.lightdm: lightdm 1.21.5-0ubuntu1 version.mesa: libegl1-mesa-dev 13.0.4-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1672793/+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 1631627] Re: Unity 8 freezes on Nouveau
*** This bug is a duplicate of bug 1553328 *** https://bugs.launchpad.net/bugs/1553328 ** This bug is no longer a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. ** This bug has been marked a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1631627 Title: Unity 8 freezes on Nouveau Status in Canonical System Image: Incomplete Status in Mir: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: I installed Ubuntu 16.10 yesterday and Unity 8 constantly freezes after I do some clicking around the desktop (using Browser, System Settings and the like), I am running it on Nouveau driver for GTX970M, I refrained from installing proprietary drivers to test Unity 8, but it is unusable and after it freezes I can only power off my laptop as nothing works. Is this a known issue? Also Unity 7 does not load at all, but I will post a separate bug for that. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1631627/+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 1595238] Re: Unity 8 Desktop Preview System Settings do not work on nouveau [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file ../../../src/ubuntumirclient/gl
*** This bug is a duplicate of bug 1553328 *** https://bugs.launchpad.net/bugs/1553328 ** This bug is no longer a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings ** This bug has been marked a duplicate of bug 1497593 Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1595238 Title: Unity 8 Desktop Preview System Settings do not work on nouveau [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file ../../../src/ubuntumirclient/glcontext.cpp, line 239] Status in Canonical System Image: New Status in qtubuntu package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: When I try to open System Settings, the Ubuntu logo keeps turning and nothing happens. I installed unity8-desktop-session-mir on my Xenial 16.04.1 Desktop where I use NVIDIA driver GF108[GeForce GT 530]. I also created a new user account with English (US) language settings, because Unity 8 does not work well when I use my own account with my language settings. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595238/+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 1623507] Re: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear().
*** This bug is a duplicate of bug 1553328 *** https://bugs.launchpad.net/bugs/1553328 ** This bug is no longer a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings ** This bug has been marked a duplicate of bug 1497593 Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1623507 Title: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear(). Status in Canonical System Image: New Status in Mir: Triaged Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: Triaged Bug description: 16.10 first unity 8 run ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-system-compositor 0.7.1+16.10.20160824-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Sep 14 10:34:45 2016 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. G92 [GeForce 9800 GT] [3842:c988] InstallationDate: Installed on 2016-09-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 7 ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: mir::fatal_error_abort(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libmircommon.so.6 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.70-1 version.lightdm: lightdm 1.19.4-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623507/+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 1623508] Re: unity8 crashed with SIGSEGV
*** This bug is a duplicate of bug 1553328 *** https://bugs.launchpad.net/bugs/1553328 ** This bug is no longer a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings ** This bug has been marked a duplicate of bug 1497593 Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1623508 Title: unity8 crashed with SIGSEGV Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: 16.10 first unity 8 run16.10 first unity 8 run ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity8 8.14+16.10.20160831.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Sep 14 10:32:07 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2016-09-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) ProcCmdline: unity8 --mode=full-shell Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1623508/+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 1631627] Re: Unity 8 freezes on Nouveau
*** This bug is a duplicate of bug 1553328 *** https://bugs.launchpad.net/bugs/1553328 ** This bug is no longer a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings ** This bug has been marked a duplicate of bug 1497593 Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1631627 Title: Unity 8 freezes on Nouveau Status in Canonical System Image: Incomplete Status in Mir: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: I installed Ubuntu 16.10 yesterday and Unity 8 constantly freezes after I do some clicking around the desktop (using Browser, System Settings and the like), I am running it on Nouveau driver for GTX970M, I refrained from installing proprietary drivers to test Unity 8, but it is unusable and after it freezes I can only power off my laptop as nothing works. Is this a known issue? Also Unity 7 does not load at all, but I will post a separate bug for that. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1631627/+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 1672793] Re: unity-system-compositor crashed with SIGSEGV
*** This bug is a duplicate of bug 1553328 *** https://bugs.launchpad.net/bugs/1553328 ** This bug is no longer a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings ** This bug has been marked a duplicate of bug 1497593 Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1672793 Title: unity-system-compositor crashed with SIGSEGV Status in Unity System Compositor: New Status in unity-system-compositor package in Ubuntu: New Bug description: I just got this on the first login to my new Ubuntu user profile ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: unity-system-compositor 0.9.1+17.04.20170216-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Tue Mar 14 20:14:24 2017 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2013-09-15 (1275 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 13 --to-dm-fd 22 --vt 8 ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f8dc76dd07f:mov0x8(%r15),%edx PC (0x7f8dc76dd07f) ok source "0x8(%r15)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-system-compositor StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so Title: unity-system-compositor crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.75-1ubuntu1 version.lightdm: lightdm 1.21.5-0ubuntu1 version.mesa: libegl1-mesa-dev 13.0.4-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1672793/+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 1929657] Comment bridged from LTC Bugzilla
--- Comment From stefan.ra...@de.ibm.com 2021-06-10 03:55 EDT--- Makes me wonder if what we're seeing is a side-effect of --- Comment From stefan.ra...@de.ibm.com 2021-06-10 03:58 EDT--- Makes me wonder whether this could be a side-effect of the interface name, indeed. @Viktor/Niklas: Interface enP50s3832.170 gets an IP assigned, no problem. But enP53p0s0.171 does not, and Frank noticed that systemd spills out this message: enP53p0s0.171: link pending udev initialization... So could it be that systemd trips over the FID containing an alphabetic character, and never registers the interface as properly initialized..? -- 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/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965):
[Touch-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
I should have added that it would be best in this case to have the debug mode enabled for udevd, too: $ cat /etc/systemd/system/systemd-udevd.service.d/override.conf [Service] Environment=SYSTEMD_LOG_LEVEL=debug $ sudo systemctl daemon-reload && sudo systemctl restart systemd-udevd $ journalctl -b -u systemd-networkd -u systemd-udevd --no-pager (instead of -b you may do '--since="today"' and/or '--until="5 minutes ago"' or so to reduce the output) You may then trigger the udev rules directly, like: $ sudo udevadm trigger and once indirectly via netplan (and maybe via 'ip'). -- 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/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is
[Touch-packages] [Bug 1929647] Re: debian helper tools for python never updates
10jun still can't upgrade ** Attachment added: "10junnoinstallPeek 2021-06-10 09-51.gif" https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+attachment/5503784/+files/10junnoinstallPeek%202021-06-10%2009-51.gif -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1929647 Title: debian helper tools for python never updates Status in python-debian package in Ubuntu: New Bug description: software updater prompts new updates debian helper tools for python is always one of them but I cannot select the checkbox so debian helper tools for python never updates Here's the screen shot https://i.imgur.com/AjDd5yo.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+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 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
Without the recent PPC fixes s390x was broken as well, so I'm not saying "the
ppc fixes broke s390x":
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210608_073451_f187d@/log.gz
Instead there seems to be a new crash affecting s390x that has to be
looked at to be able to rev up the nss version.
Tagging server-next and subscribing the team as this is no more a +1 task.
If we are lucky the always dilligent locutus (who often merges nss) might come
by and give it a short as well when we have latter nss versions.
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1931104
Title:
Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-
proposed
Status in nss package in Ubuntu:
New
Bug description:
The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
Example:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz
Bad:
Installing CA into /var/lib/pki/pki-tomcat.
Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end
closed connection without response'))
ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote
end closed connection without response'))
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 995, in spawn
cert = deployer.setup_cert(client, tag)
File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py",
line 355, in setup_cert
return client.setupCert(request)
File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert
response = self.connection.post(
File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper
return func(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post
r = self.session.post(
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in
post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in
send
raise ConnectionError(err, request=request)
CA spawn failed:
Good:
nstalling CA into /var/lib/pki/pki-tomcat.
Notice: Trust flag u is set automatically if the private key is present.
/usr/lib/python3/dist-packages/urllib3/connection.py:455:
SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`,
falling back to check for a `commonName` for now. This feature is being removed
by major browsers and deprecated by RFC 2818. (See
https://github.com/urllib3/urllib3/issues/497 for details.)
warnings.warn(
==
INSTALLATION SUMMARY
==
...
The good test above was with:
ii libnss3:s390x2:3.61-1ubuntu2 s390xNetwork Security
Service libraries
ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite -
server
Worth to know, the good case test still fails later on with:
IOException: SocketException cannot write on socket: Failed to write to
socket: (-5938) Encountered end of file.
ERROR: CalledProcessError: Command '['pki', '-d',
'/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U',
'https://i-dogtag:8443', 'securitydomain-join', '--session',
'4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag',
'--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']'
returned non-zero exit status 255.
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 1038, in spawn
subsystem.join_security_domain(
File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201,
in join_security_domain
subprocess.check_call(cmd)
File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f
/etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join
--session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port
8080 --secure-port 8443
[Touch-packages] [Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
Reproducible, ppc64 is fixed and s390x broken by the latest 3.66 + fixes from
master.
Links:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210609_065306_2e698@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210609_121610_a71da@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210609_124415_d071b@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1931104
Title:
Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-
proposed
Status in nss package in Ubuntu:
New
Bug description:
The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
Example:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz
Bad:
Installing CA into /var/lib/pki/pki-tomcat.
Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end
closed connection without response'))
ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote
end closed connection without response'))
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 995, in spawn
cert = deployer.setup_cert(client, tag)
File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py",
line 355, in setup_cert
return client.setupCert(request)
File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert
response = self.connection.post(
File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper
return func(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post
r = self.session.post(
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in
post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in
send
raise ConnectionError(err, request=request)
CA spawn failed:
Good:
nstalling CA into /var/lib/pki/pki-tomcat.
Notice: Trust flag u is set automatically if the private key is present.
/usr/lib/python3/dist-packages/urllib3/connection.py:455:
SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`,
falling back to check for a `commonName` for now. This feature is being removed
by major browsers and deprecated by RFC 2818. (See
https://github.com/urllib3/urllib3/issues/497 for details.)
warnings.warn(
==
INSTALLATION SUMMARY
==
...
The good test above was with:
ii libnss3:s390x2:3.61-1ubuntu2 s390xNetwork Security
Service libraries
ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite -
server
Worth to know, the good case test still fails later on with:
IOException: SocketException cannot write on socket: Failed to write to
socket: (-5938) Encountered end of file.
ERROR: CalledProcessError: Command '['pki', '-d',
'/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U',
'https://i-dogtag:8443', 'securitydomain-join', '--session',
'4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag',
'--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']'
returned non-zero exit status 255.
File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in
main
scriptlet.spawn(deployer)
File
"/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py",
line 1038, in spawn
subsystem.join_security_domain(
File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201,
in join_security_domain
subprocess.check_call(cmd)
File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f
/etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join
--session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port
8080 --secure-port 8443 TKS i-dogtag 8443
Please check pkispawn logs in /var/log/pki/pki-tks-spawn.20210607093926.log
[Touch-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
Ok, the line that concerns me is: " enP53p0s0.171: link pending udev initialization... " It looks like systemd-networkd thinks that udev is not done with enP53p0s0.171 --> "pending", but configuring it with ip works - so could be networkd or also udevd. So lets expand the journal output with the udev messages and share it again: journalctl -b -u systemd-networkd -u systemd-udevd --no-pager Please can you also share the output of: apt-cache policy systemd udev netplan.io Investigations pointed me to: https://github.com/systemd/systemd/issues/15445#issuecomment-776856604 (changing the interface name at some point could be interesting, too...) Anyway, I'll mark this bug as affecting systemd now. ** Bug watch added: github.com/systemd/systemd/issues #15445 https://github.com/systemd/systemd/issues/15445 ** Also 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/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not
