[Touch-packages] [Bug 2017734] Re: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdk-pixbuf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2017734 Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned Status in gdk-pixbuf package in Ubuntu: Confirmed Bug description: Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 26 08:57:37 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2023-01-24 (91 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2017734/+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 2030505] Re: on ubuntu 22.04 systemd fails with per interface dns configurations
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/2030505 Title: on ubuntu 22.04 systemd fails with per interface dns configurations Status in systemd package in Ubuntu: Confirmed Bug description: Hi There, Systemd seems to work awesome, except when dns proxy is running on localhost ipaddress. The below fix seems to takescare of such cases. Unfortunately this is not included in the latest systemd versions on ubuntu22.04 LTS. Is it possible to consider our humble request and add this to the systemd versions supported on ubuntu22.04, it is creating lots of issues for our users. https://github.com/systemd/systemd/pull/25438 I am raising this ticket as requested below -snippet actionparsnip Aug 5, 2023, 6:26 PM (2 days ago) to me Your question #707538 on systemd in Ubuntu changed: https://answers.launchpad.net/ubuntu/+source/systemd/+question/707538 Status: Open => Answered actionparsnip proposed the following answer: I suggest you report a bug. Add your URL to the bug for visibility. You can start the process by running: ubuntu-bug systemd Thanks in advance Regards, Dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2030505/+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 2031942] Autopkgtest regression report (openssh/1:8.9p1-3ubuntu0.4)
All autopkgtests for the newly accepted openssh (1:8.9p1-3ubuntu0.4) for jammy have finished running. The following regressions have been reported in tests triggered by the package: ganeti/3.0.2-1ubuntu1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#openssh [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2031942 Title: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Jammy: Fix Committed Status in openssh source package in Lunar: Fix Committed Status in openssh source package in Mantic: Fix Released Bug description: [Impact] User of openssh reported an issue that affects Lunar and Jammy. If AuthorizedKeysCommand is set, an AuthorizedPrincipalsCommand configuration in sshd_config that comes after it is ignored. In this scenario, where AuthorizedPrincipalsCommand is needed and set, users relying on ssh certificates for authentication will be denied access. [Test Plan] Launch container: $ lxc launch ubuntu:jammy Shell into that container: $ lxc shell Create the main directory for our task (e.g. “reproducer”) # mkdir reproducer Go to that directory: # cd reproducer Create 2 more dirs that reflect users: # mkdir certuser keyonlyuser Go to the keyonlyuser: # cd keyonlyuser Do: # ssh-keygen -t ed25519 -f key Go to the certuser: # cd /root/reproducer/certuser/ Do: # ssh-keygen -t rsa -f ca # ssh-keygen -t ed25519 -f key # ssh-keygen -s ca -I key_id -n certuser key.pub Create a script '/root/reproducer/authorized_principals' with permissions 755 as follows: #!/bin/sh if [ "$1" = "otheruser" ]; then echo certuser fi Exit the file. Ensure you are in the /root/reproducer/ directory: # adduser --disabled-password otheruser (Enter multiple times, leave all fields blank) Then do the same for another user: # adduser --disabled-password keyonlyuser Create a script '/root/reproducer/authorized_keys' with permissions 755 as follows: #!/bin/sh if [ "$1" = "keyonlyuser" ]; then echo fi Go to the /etc/ssh/sshd_config file. Add at the top: AuthorizedKeysCommand /root/reproducer/authorized_keys %u AuthorizedKeysCommandUser root AuthorizedPrincipalsCommand /root/reproducer/authorized_principals %u AuthorizedPrincipalsCommandUser root TrustedUserCAKeys /root/reproducer/certuser/ca.pub Exit from the file and restart the ssh service: # systemctl restart ssh Use these commands to manifest the bug: # ssh keyonlyuser@localhost -i /root/reproducer/keyonlyuser/key # ssh otheruser@localhost -i /root/reproducer/certuser/key -o CertificateFile=/root/reproducer/certuser/key-cert.pub Expected results: both ssh commands should succeed. Actual results: the second ssh fails because the AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set. [Where problems could occur] * The patch itself modifies only the servconf.c, so regressions should be limited to the server configuration. * Since the fix touches pointers, there might be regression related to memory handling and fetching data. -original report-- Versions of OpenSSH from 8.7p1 to 9.3p1 contain the following code: if (*activep && options->authorized_keys_command == NULL) *charptr = xstrdup(str + len); However, this is executed for both authorized_keys_command and authorized_principals_command. As a result, if authorized_keys_command is set (for instance, if using ec2-instance-connect), any AuthorizedPrincipalsCommand configuration in sshd_config is ignored. This is fixed in 9.4p1 with the attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2031942/+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 2031942] Autopkgtest regression report (openssh/1:9.0p1-1ubuntu8.5)
All autopkgtests for the newly accepted openssh (1:9.0p1-1ubuntu8.5) for lunar have finished running. The following regressions have been reported in tests triggered by the package: ganeti/3.0.2-3 (armhf) gvfs/1.50.4-1 (arm64) lava/unknown (amd64) oz/unknown (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#openssh [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2031942 Title: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Jammy: Fix Committed Status in openssh source package in Lunar: Fix Committed Status in openssh source package in Mantic: Fix Released Bug description: [Impact] User of openssh reported an issue that affects Lunar and Jammy. If AuthorizedKeysCommand is set, an AuthorizedPrincipalsCommand configuration in sshd_config that comes after it is ignored. In this scenario, where AuthorizedPrincipalsCommand is needed and set, users relying on ssh certificates for authentication will be denied access. [Test Plan] Launch container: $ lxc launch ubuntu:jammy Shell into that container: $ lxc shell Create the main directory for our task (e.g. “reproducer”) # mkdir reproducer Go to that directory: # cd reproducer Create 2 more dirs that reflect users: # mkdir certuser keyonlyuser Go to the keyonlyuser: # cd keyonlyuser Do: # ssh-keygen -t ed25519 -f key Go to the certuser: # cd /root/reproducer/certuser/ Do: # ssh-keygen -t rsa -f ca # ssh-keygen -t ed25519 -f key # ssh-keygen -s ca -I key_id -n certuser key.pub Create a script '/root/reproducer/authorized_principals' with permissions 755 as follows: #!/bin/sh if [ "$1" = "otheruser" ]; then echo certuser fi Exit the file. Ensure you are in the /root/reproducer/ directory: # adduser --disabled-password otheruser (Enter multiple times, leave all fields blank) Then do the same for another user: # adduser --disabled-password keyonlyuser Create a script '/root/reproducer/authorized_keys' with permissions 755 as follows: #!/bin/sh if [ "$1" = "keyonlyuser" ]; then echo fi Go to the /etc/ssh/sshd_config file. Add at the top: AuthorizedKeysCommand /root/reproducer/authorized_keys %u AuthorizedKeysCommandUser root AuthorizedPrincipalsCommand /root/reproducer/authorized_principals %u AuthorizedPrincipalsCommandUser root TrustedUserCAKeys /root/reproducer/certuser/ca.pub Exit from the file and restart the ssh service: # systemctl restart ssh Use these commands to manifest the bug: # ssh keyonlyuser@localhost -i /root/reproducer/keyonlyuser/key # ssh otheruser@localhost -i /root/reproducer/certuser/key -o CertificateFile=/root/reproducer/certuser/key-cert.pub Expected results: both ssh commands should succeed. Actual results: the second ssh fails because the AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set. [Where problems could occur] * The patch itself modifies only the servconf.c, so regressions should be limited to the server configuration. * Since the fix touches pointers, there might be regression related to memory handling and fetching data. -original report-- Versions of OpenSSH from 8.7p1 to 9.3p1 contain the following code: if (*activep && options->authorized_keys_command == NULL) *charptr = xstrdup(str + len); However, this is executed for both authorized_keys_command and authorized_principals_command. As a result, if authorized_keys_command is set (for instance, if using ec2-instance-connect), any AuthorizedPrincipalsCommand configuration in sshd_config is ignored. This is fixed in 9.4p1 with the attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2031942/+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 2030505] Re: on ubuntu 22.04 systemd fails with per interface dns configurations
@Nick are you running pihole listening on some port on 127.0.0.x ?? You should be able to reproduce the problem fairly easily -- 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/2030505 Title: on ubuntu 22.04 systemd fails with per interface dns configurations Status in systemd package in Ubuntu: New Bug description: Hi There, Systemd seems to work awesome, except when dns proxy is running on localhost ipaddress. The below fix seems to takescare of such cases. Unfortunately this is not included in the latest systemd versions on ubuntu22.04 LTS. Is it possible to consider our humble request and add this to the systemd versions supported on ubuntu22.04, it is creating lots of issues for our users. https://github.com/systemd/systemd/pull/25438 I am raising this ticket as requested below -snippet actionparsnip Aug 5, 2023, 6:26 PM (2 days ago) to me Your question #707538 on systemd in Ubuntu changed: https://answers.launchpad.net/ubuntu/+source/systemd/+question/707538 Status: Open => Answered actionparsnip proposed the following answer: I suggest you report a bug. Add your URL to the bug for visibility. You can start the process by running: ubuntu-bug systemd Thanks in advance Regards, Dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2030505/+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 2030505] Re: on ubuntu 22.04 systemd fails with per interface dns configurations
WORKING logs from ubuntu 23.04 1……. dig google.com ; <<>> DiG 9.18.12-1ubuntu1.1-Ubuntu <<>> google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44609 ;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;google.com. IN A ;; ANSWER SECTION: google.com. 300 IN A 108.177.121.139 google.com. 300 IN A 108.177.121.101 google.com. 300 IN A 108.177.121.102 google.com. 300 IN A 108.177.121.113 google.com. 300 IN A 108.177.121.100 google.com. 300 IN A 108.177.121.138 ;; Query time: 88 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP) ;; WHEN: Wed Sep 06 13:26:32 PDT 2023 ;; MSG SIZE rcvd: 135  2…… resolvectl --version systemd 252 (252.5-2ubuntu3) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified 3…… resolvectl Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (enp0s25) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 3 (wlp3s0) Current Scopes: DNS Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 2001:558:feed::1 DNS Servers: 75.75.75.75 75.75.76.76 2001:558:feed::1 2001:558:feed::2 DNS Domain: hsd1.ca.comcast.net Link 4 (wg0) Current Scopes: DNS Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 127.0.0.5 DNS Servers: 127.0.0.5 DNS Domain: ~google.com ~icanhazip.com ~myvm.banyan.local ~starfall.com 4……. TCPDUMP on loopback interface shows packets for each new requests from the browser. Command used tcpdump -v -i lo host 127.0.0.5 -n -e tcpdump -i lo host 127.0.0.5 -n -e tcpdump: verbose output suppressed, use -v[v]... for full protocol decode listening on lo, link-type EN10MB (Ethernet), snapshot length 262144 bytes 13:15:13.688335 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 90: 127.0.0.1.43650 > 127.0.0.5.53: 37616+ [1au] ? accounts.google.com. (48) 13:15:13.688629 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 162: 127.0.0.5.53 > 127.0.0.1.43650: 37616 0/1/0 (120) 13:15:13.688735 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 79: 127.0.0.1.43650 > 127.0.0.5.53: 17606+ ? accounts.google.com. (37) 13:15:13.689592 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 162: 127.0.0.5.53 > 127.0.0.1.43650: 17606 0/1/0 (120) 13:15:13.691846 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 79: 127.0.0.1.52745 > 127.0.0.5.53: 31481+ A? accounts.google.com. (37) 13:15:13.691977 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 79: 127.0.0.1.51923 > 127.0.0.5.53: 35485+ Type65? accounts.google.com. (37) 13:15:13.758834 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 129: 127.0.0.5.53 > 127.0.0.1.51923: 35485 0/1/0 (87) 13:15:13.763131 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 95: 127.0.0.5.53 > 127.0.0.1.52745: 31481 1/0/0 A 74.125.124.84 (53) 13:15:13.900401 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 74: 127.0.0.1.35406 > 127.0.0.5.53: 53100+ ? www.google.com. (32) 13:15:13.900535 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 74: 127.0.0.1.35235 > 127.0.0.5.53: 32316+ A? www.google.com. (32) 13:15:13.900654 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 74: 127.0.0.1.37372 > 127.0.0.5.53: 6359+ Type65? www.google.com. (32) 13:15:13.901093 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 157: 127.0.0.5.53 > 127.0.0.1.35406: 53100 0/1/0 (115) 13:15:13.983575 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 170: 127.0.0.5.53 > 127.0.0.1.35235: 32316 6/0/0 A 142.251.172.103, A 142.251.172.104, A 142.251.172.99, A 142.251.172.105, A 142.251.172.147, A 142.251.172.106 (128) 13:15:15.441686 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 83: 127.0.0.1.43473 > 127.0.0.5.53: 7644+ PTR? 9.0.115.10.in-addr.arpa. (41) 5……. Logs from systems-resolved 2023-09-06T13:16:18.832452-07:00 devanath-lin systemd-resolved[666]: wg0: Bus client set DNS server list to: 127.0.0.5 2023-09-06T13:16:18.832537-07:00 devanath-lin systemd-resolved[666]: Sent message type=method_return sender=n/a destination=:1.161 path=n/a interface=n/a member=n/a cookie=110 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a 2023-09-06T13:16:18.837909-07:00 devanath-lin systemd-resolved[666]: Got message type=method_call sender=:1.162 destination=org.freedesktop.resolve1
[Touch-packages] [Bug 2030505] Re: on ubuntu 22.04 systemd fails with per interface dns configurations
We have a dns proxy running on 127.0.0.5:53. Below are the logs for ubuntu 22.04 LTS and is not working 1.. dig google.com ;; communications error to 127.0.0.53#53: timed out ;; communications error to 127.0.0.53#53: timed out ;; communications error to 127.0.0.53#53: timed out ; <<>> DiG 9.18.12-0ubuntu0.22.04.2-Ubuntu <<>> google.com ;; global options: +cmd ;; no servers could be reached 2.. resolvectl Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (ens33) Current Scopes: DNS Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 75.75.75.75 DNS Servers: 75.75.75.75 75.75.76.76 DNS Domain: hsd1.ca.comcast.net Link 3 (wg0) Current Scopes: DNS Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 127.0.0.5 DNS Servers: 127.0.0.5 DNS Domain: ~google.com ~icanhazip.com ~myvm.banyan.local Link 4 (docker0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported 3.TCPDUMP on loopback interface shows some packets for first request and after that there are no packets seen at all. Command used tcpdump -v -i lo host 127.0.0.5 -n -e 13:49:10.755476 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 87: (tos 0x0, ttl 64, id 37216, offset 0, flags [none], proto UDP (17), length 73) 10.115.0.12.41708 > 127.0.0.5.53: [bad udp cksum 0x89ca -> 0x5f03!] 27623+ [1au] A? mtalk.google.com. ar: . OPT UDPsize=65508 (45) 13:49:10.823942 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 103: (tos 0x0, ttl 64, id 20158, offset 0, flags [DF], proto UDP (17), length 89) 127.0.0.5.53 > 10.115.0.12.41708: [bad udp cksum 0x89da -> 0xea69!] 27623 q: A? mtalk.google.com. 1/0/1 mtalk.google.com. [5m] A 142.250.136.188 ar: . OPT UDPsize=512 (61) 13:49:14.005421 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 87: (tos 0x0, ttl 64, id 31594, offset 0, flags [none], proto UDP (17), length 73) 10.115.0.12.54467 > 127.0.0.5.53: [bad udp cksum 0x89ca -> 0xe4a5!] 44148+ [1au] A? drive.google.com. ar: . OPT UDPsize=65508 (45) 13:49:14.005498 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 87: (tos 0x0, ttl 64, id 9557, offset 0, flags [none], proto UDP (17), length 73) 10.115.0.12.35442 > 127.0.0.5.53: [bad udp cksum 0x89ca -> 0x39bb!] 41328+ [1au] Type65? drive.google.com. ar: . OPT UDPsize=65508 (45) 13:49:14.070235 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 137: (tos 0x0, ttl 64, id 20216, offset 0, flags [DF], proto UDP (17), length 123) 127.0.0.5.53 > 10.115.0.12.35442: [bad udp cksum 0x89fc -> 0xb9dc!] 41328 q: Type65? drive.google.com. 0/1/1 ns: google.com. [1m] SOA ns1.google.com. dns-admin.google.com. 561875416 900 900 1800 60 ar: . OPT UDPsize=512 (95) 13:49:14.071633 00:00:00:00:00:00 > 00:00:00:00:00:00, ethertype IPv4 (0x0800), length 183: (tos 0x0, ttl 64, id 20217, offset 0, flags [DF], proto UDP (17), length 169) 127.0.0.5.53 > 10.115.0.12.54467: [bad udp cksum 0x8a2a -> 0x5a27!] 44148 q: A? drive.google.com. 6/0/1 drive.google.com. [5m] A 209.85.234.138, drive.google.com. [5m] A 209.85.234.101, drive.google.com. [5m] A 209.85.234.139, drive.google.com. [5m] A 209.85.234.113, drive.google.com. [5m] A 209.85.234.102, drive.google.com. [5m] A 209.85.234.100 ar: . OPT UDPsize=512 (141) 4……..Logs on systems-resolved Sep 6 13:49:04 devanath-virtual-machine systemd-resolved[74204]: wg0: Bus client set DNS server list to: 127.0.0.5 Sep 6 13:49:04 devanath-virtual-machine systemd-resolved[74204]: Sent message type=method_return sender=n/a destination=:1.523 path=n/a interface=n/a member=n/a cookie=146 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a Sep 6 13:49:04 devanath-virtual-machine systemd-resolved[74204]: Got message type=method_call sender=:1.524 destination=org.freedesktop.resolve1 path=/org/freedesktop/resolve1 interface=org.freedesktop.resolve1.Manager member=SetLinkDomains cookie=2 reply_cookie=0 signature=ia(sb) error-name=n/a error-message=n/a Sep 6 13:49:04 devanath-virtual-machine systemd-resolved[74204]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=147 reply_cookie=0 signature=s error-name=n/a error-message=n/a Sep 6 13:49:04 devanath-virtual-machine systemd-resolved[74204]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.482 path=n/a interface=n/a member=n/a cookie=75 reply_cookie=147 signature=u error-name=n/a error-message=n/a Sep 6 13:49:04 devanath-virtual-machine systemd-resolved[74204]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus
[Touch-packages] [Bug 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
** Patch added: "lp1981103.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+attachment/5698057/+files/lp1981103.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
In Progress
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
everybody. Most servers provided by data centers like Hetzner
(Germany) are configure like that. After a do-release-upgrade you have
no working DNS anymore, unless you disable systemd-resolved. I don't
want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+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 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
I've attached a debdiff with the patches for fixing this one. I've
subscribed ubuntu-sponsors to kindly request sponsorship for mantic.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
In Progress
Bug description:
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
everybody. Most servers provided by data centers like Hetzner
(Germany) are configure like that. After a do-release-upgrade you have
no working DNS anymore, unless you disable systemd-resolved. I don't
want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+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 2031942] Please test proposed package
Hello Matthew, or anyone else affected, Accepted openssh into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssh/1:8.9p1-3ubuntu0.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2031942 Title: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Jammy: Fix Committed Status in openssh source package in Lunar: Fix Committed Status in openssh source package in Mantic: Fix Released Bug description: [Impact] User of openssh reported an issue that affects Lunar and Jammy. If AuthorizedKeysCommand is set, an AuthorizedPrincipalsCommand configuration in sshd_config that comes after it is ignored. In this scenario, where AuthorizedPrincipalsCommand is needed and set, users relying on ssh certificates for authentication will be denied access. [Test Plan] Launch container: $ lxc launch ubuntu:jammy Shell into that container: $ lxc shell Create the main directory for our task (e.g. “reproducer”) # mkdir reproducer Go to that directory: # cd reproducer Create 2 more dirs that reflect users: # mkdir certuser keyonlyuser Go to the keyonlyuser: # cd keyonlyuser Do: # ssh-keygen -t ed25519 -f key Go to the certuser: # cd /root/reproducer/certuser/ Do: # ssh-keygen -t rsa -f ca # ssh-keygen -t ed25519 -f key # ssh-keygen -s ca -I key_id -n certuser key.pub Create a script '/root/reproducer/authorized_principals' with permissions 755 as follows: #!/bin/sh if [ "$1" = "otheruser" ]; then echo certuser fi Exit the file. Ensure you are in the /root/reproducer/ directory: # adduser --disabled-password otheruser (Enter multiple times, leave all fields blank) Then do the same for another user: # adduser --disabled-password keyonlyuser Create a script '/root/reproducer/authorized_keys' with permissions 755 as follows: #!/bin/sh if [ "$1" = "keyonlyuser" ]; then echo fi Go to the /etc/ssh/sshd_config file. Add at the top: AuthorizedKeysCommand /root/reproducer/authorized_keys %u AuthorizedKeysCommandUser root AuthorizedPrincipalsCommand /root/reproducer/authorized_principals %u AuthorizedPrincipalsCommandUser root TrustedUserCAKeys /root/reproducer/certuser/ca.pub Exit from the file and restart the ssh service: # systemctl restart ssh Use these commands to manifest the bug: # ssh keyonlyuser@localhost -i /root/reproducer/keyonlyuser/key # ssh otheruser@localhost -i /root/reproducer/certuser/key -o CertificateFile=/root/reproducer/certuser/key-cert.pub Expected results: both ssh commands should succeed. Actual results: the second ssh fails because the AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set. [Where problems could occur] * The patch itself modifies only the servconf.c, so regressions should be limited to the server configuration. * Since the fix touches pointers, there might be regression related to memory handling and fetching data. -original report-- Versions of OpenSSH from 8.7p1 to 9.3p1 contain the following code: if (*activep && options->authorized_keys_command == NULL) *charptr = xstrdup(str + len); However, this is executed for both authorized_keys_command and authorized_principals_command. As a result, if authorized_keys_command is set (for instance, if using ec2-instance-connect), any AuthorizedPrincipalsCommand configuration in sshd_config is ignored. This is fixed in 9.4p1 with the attached patch. To manage notifications about this bug go to:
[Touch-packages] [Bug 2031942] Re: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set
Hello Matthew, or anyone else affected, Accepted openssh into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssh/1:9.0p1-1ubuntu8.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssh (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar ** Changed in: openssh (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2031942 Title: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Jammy: Fix Committed Status in openssh source package in Lunar: Fix Committed Status in openssh source package in Mantic: Fix Released Bug description: [Impact] User of openssh reported an issue that affects Lunar and Jammy. If AuthorizedKeysCommand is set, an AuthorizedPrincipalsCommand configuration in sshd_config that comes after it is ignored. In this scenario, where AuthorizedPrincipalsCommand is needed and set, users relying on ssh certificates for authentication will be denied access. [Test Plan] Launch container: $ lxc launch ubuntu:jammy Shell into that container: $ lxc shell Create the main directory for our task (e.g. “reproducer”) # mkdir reproducer Go to that directory: # cd reproducer Create 2 more dirs that reflect users: # mkdir certuser keyonlyuser Go to the keyonlyuser: # cd keyonlyuser Do: # ssh-keygen -t ed25519 -f key Go to the certuser: # cd /root/reproducer/certuser/ Do: # ssh-keygen -t rsa -f ca # ssh-keygen -t ed25519 -f key # ssh-keygen -s ca -I key_id -n certuser key.pub Create a script '/root/reproducer/authorized_principals' with permissions 755 as follows: #!/bin/sh if [ "$1" = "otheruser" ]; then echo certuser fi Exit the file. Ensure you are in the /root/reproducer/ directory: # adduser --disabled-password otheruser (Enter multiple times, leave all fields blank) Then do the same for another user: # adduser --disabled-password keyonlyuser Create a script '/root/reproducer/authorized_keys' with permissions 755 as follows: #!/bin/sh if [ "$1" = "keyonlyuser" ]; then echo fi Go to the /etc/ssh/sshd_config file. Add at the top: AuthorizedKeysCommand /root/reproducer/authorized_keys %u AuthorizedKeysCommandUser root AuthorizedPrincipalsCommand /root/reproducer/authorized_principals %u AuthorizedPrincipalsCommandUser root TrustedUserCAKeys /root/reproducer/certuser/ca.pub Exit from the file and restart the ssh service: # systemctl restart ssh Use these commands to manifest the bug: # ssh keyonlyuser@localhost -i /root/reproducer/keyonlyuser/key # ssh otheruser@localhost -i /root/reproducer/certuser/key -o CertificateFile=/root/reproducer/certuser/key-cert.pub Expected results: both ssh commands should succeed. Actual results: the second ssh fails because the AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set. [Where problems could occur] * The patch itself modifies only the servconf.c, so regressions should be limited to the server configuration. * Since the fix touches pointers, there might be regression related to memory handling and fetching data. -original report-- Versions of OpenSSH from 8.7p1 to 9.3p1 contain the following code: if (*activep && options->authorized_keys_command == NULL) *charptr = xstrdup(str + len); However, this is executed for both authorized_keys_command and authorized_principals_command. As a result, if
[Touch-packages] [Bug 2031942] Re: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set
** Description changed: [Impact] - * User of openssh reported an issue that affects Lunar and Jammy. + User of openssh reported an issue that affects Lunar and Jammy. - * This crash is caused by the wrong pointer manipulation in the if - statement. The fix is to change the code to check if the value pointed - to by the pointer 'charptr' is NULL. + If AuthorizedKeysCommand is set, an AuthorizedPrincipalsCommand + configuration in sshd_config that comes after it is ignored. In this + scenario, where AuthorizedPrincipalsCommand is needed and set, users + relying on ssh certificates for authentication will be denied access. [Test Plan] Launch container: $ lxc launch ubuntu:jammy Shell into that container: $ lxc shell Create the main directory for our task (e.g. “reproducer”) # mkdir reproducer Go to that directory: # cd reproducer Create 2 more dirs that reflect users: # mkdir certuser keyonlyuser Go to the keyonlyuser: # cd keyonlyuser Do: # ssh-keygen -t ed25519 -f key Go to the certuser: # cd /root/reproducer/certuser/ Do: # ssh-keygen -t rsa -f ca # ssh-keygen -t ed25519 -f key # ssh-keygen -s ca -I key_id -n certuser key.pub Create a script '/root/reproducer/authorized_principals' with permissions 755 as follows: #!/bin/sh if [ "$1" = "otheruser" ]; then echo certuser fi Exit the file. Ensure you are in the /root/reproducer/ directory: # adduser --disabled-password otheruser (Enter multiple times, leave all fields blank) Then do the same for another user: # adduser --disabled-password keyonlyuser Create a script '/root/reproducer/authorized_keys' with permissions 755 as follows: #!/bin/sh if [ "$1" = "keyonlyuser" ]; then echo fi Go to the /etc/ssh/sshd_config file. Add at the top: AuthorizedKeysCommand /root/reproducer/authorized_keys %u AuthorizedKeysCommandUser root AuthorizedPrincipalsCommand /root/reproducer/authorized_principals %u AuthorizedPrincipalsCommandUser root TrustedUserCAKeys /root/reproducer/certuser/ca.pub Exit from the file and restart the ssh service: # systemctl restart ssh Use these commands to manifest the bug: # ssh keyonlyuser@localhost -i /root/reproducer/keyonlyuser/key # ssh otheruser@localhost -i /root/reproducer/certuser/key -o CertificateFile=/root/reproducer/certuser/key-cert.pub Expected results: both ssh commands should succeed. Actual results: the second ssh fails because the AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set. [Where problems could occur] * The patch itself modifies only the servconf.c, so regressions should be limited to the server configuration. * Since the fix touches pointers, there might be regression related to memory handling and fetching data. -original report-- Versions of OpenSSH from 8.7p1 to 9.3p1 contain the following code: if (*activep && options->authorized_keys_command == NULL) *charptr = xstrdup(str + len); However, this is executed for both authorized_keys_command and authorized_principals_command. As a result, if authorized_keys_command is set (for instance, if using ec2-instance-connect), any AuthorizedPrincipalsCommand configuration in sshd_config is ignored. This is fixed in 9.4p1 with the attached patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2031942 Title: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Jammy: In Progress Status in openssh source package in Lunar: Fix Committed Status in openssh source package in Mantic: Fix Released Bug description: [Impact] User of openssh reported an issue that affects Lunar and Jammy. If AuthorizedKeysCommand is set, an AuthorizedPrincipalsCommand configuration in sshd_config that comes after it is ignored. In this scenario, where AuthorizedPrincipalsCommand is needed and set, users relying on ssh certificates for authentication will be denied access. [Test Plan] Launch container: $ lxc launch ubuntu:jammy Shell into that container: $ lxc shell Create the main directory for our task (e.g. “reproducer”) # mkdir reproducer Go to that directory: # cd reproducer Create 2 more dirs that reflect users: # mkdir certuser keyonlyuser Go to the keyonlyuser: # cd keyonlyuser Do: # ssh-keygen -t ed25519 -f key Go to the certuser: # cd /root/reproducer/certuser/ Do: # ssh-keygen -t rsa -f ca # ssh-keygen -t ed25519 -f key # ssh-keygen -s ca -I key_id -n certuser key.pub Create a script '/root/reproducer/authorized_principals'
[Touch-packages] [Bug 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
** Changed in: mesa Status: Unknown => Fix Released -- 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/2033967 Title: Laptop screen blinked, no tty works and 200 dmesg errors per second Status in Mesa: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Bug description: I was using my laptop and suddenly the screen blinked. After that, all I could do was to move the mouse, no interaction worked. Trying to change to a TTY would open the black screen but the text cursor wasn't blinking and nothing happened. I accessed the laptop via SSH and used: screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace To reload xfwm4. After that, the graphical interface started working again. However, no TTY is accessible and there are 200 dmesg errors per second. These are the errors that repeat endlessly: [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) And while I was writing this report, another problem happened: [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=2, emitted seq=6 [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process obs pid 38687 thread obs:cs0 pid 38694 [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin! [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 0x0100 != 0x [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.731204] [ cut here ] [44566.731205] WARNING: CPU: 15 PID: 29333 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk snd_rawmidi uvcvideo [44566.731465] snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq at h10k_pci [44566.731504] ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd r8169 video i2c_piix4 i2c_hid xhci_pci_renesas nvme_common realtek wmi hid [44566.731529] CPU: 15 PID: 29333 Comm: kworker/u32:1 Tainted: PW O 6.2.0-31-generic #31~22.04.1-Ubuntu [44566.731531] Hardware name: LENOVO 82MJ/LNVNB161216, BIOS H3CN36WW(V2.06) 09/30/2022 [44566.731533] Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched] [44566.731539] RIP: 0010:amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731702] Code: 31 f6 31 ff c3 cc cc
[Touch-packages] [Bug 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
I believe this likely needs the VCN fixes from https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 backported. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9728 https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Invalid ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 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/2033967 Title: Laptop screen blinked, no tty works and 200 dmesg errors per second Status in Mesa: Unknown Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Bug description: I was using my laptop and suddenly the screen blinked. After that, all I could do was to move the mouse, no interaction worked. Trying to change to a TTY would open the black screen but the text cursor wasn't blinking and nothing happened. I accessed the laptop via SSH and used: screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace To reload xfwm4. After that, the graphical interface started working again. However, no TTY is accessible and there are 200 dmesg errors per second. These are the errors that repeat endlessly: [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) And while I was writing this report, another problem happened: [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=2, emitted seq=6 [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process obs pid 38687 thread obs:cs0 pid 38694 [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin! [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 0x0100 != 0x [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.731204] [ cut here ] [44566.731205] WARNING: CPU: 15 PID: 29333 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk snd_rawmidi uvcvideo [44566.731465] snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq at h10k_pci [44566.731504] ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd r8169 video
[Touch-packages] [Bug 1914839] Re: package upgrade should replace /etc/ssl/certs/ca-certificates.crt atomically
This was fixed in ca-certificates version 20211016 which is what Jammy released with. As of today, all Ubuntu releases from Bionic onward ship 20230311 so marking as fix released. ** Changed in: ca-certificates (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1914839 Title: package upgrade should replace /etc/ssl/certs/ca-certificates.crt atomically Status in ca-certificates package in Ubuntu: Fix Released Status in ca-certificates package in Debian: Fix Released Bug description: While upgrading the ca-certificates package, a process got the error: SSL_ca_file /etc/ssl/certs/ca-certificates.crt does not exist This file should be replaced atomically, with no time gap where the file does not exist. (I am flagging this as a security vulnerability because, while I did not experience any security issue, I can imagine at least the possibility of this being exploitable in some way in some circumstances.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1914839/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
** Tags removed: kinetic ubuntu-22.04 ubuntu-desktop ** Tags added: mantic ubuntu-meta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in One Hundred Papercuts: New Status in gsettings-desktop-schemas package in Ubuntu: In Progress Status in subiquity package in Ubuntu: Won't Fix Status in gsettings-desktop-schemas package in Debian: New Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 1956109] Re: printer-driver-ptouch is included with multiple metapackages for the minimal install
** Description changed: - A label printer driver is a recommended dependency of many desktop, - core, and minimal ubuntu and spin metapackages. It is also installed - with the minimal Ubuntu ISO option. Should this hardware be included - with the minimal install and should it be in multiple, overlapping - metapackages? If so, why? + A label printer driver is a recommended dependency in many metapackages. + It is also installed with the minimal Ubuntu ISO option. ** Tags removed: kinetic ubuntu-22.04 ** Tags added: mantic packaging ubuntu-meta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1956109 Title: printer-driver-ptouch is included with multiple metapackages for the minimal install Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: New Bug description: A label printer driver is a recommended dependency in many metapackages. It is also installed with the minimal Ubuntu ISO option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1956109/+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 1956110] Re: upower requires libimobiledevice6 as a dependency
** Tags removed: kinetic ubuntu-22.04 ** Tags added: mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1956110 Title: upower requires libimobiledevice6 as a dependency Status in libimobiledevice package in Ubuntu: New Status in upower package in Ubuntu: New Bug description: An iPhone library is required to have power management required by Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1956110/+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 2034539] [NEW] Create the usbmux user in the preinst script
Public bug reported: [placeholder] ** Affects: usbmuxd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/2034539 Title: Create the usbmux user in the preinst script Status in usbmuxd package in Ubuntu: New Bug description: [placeholder] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/2034539/+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 2018330] Re: routel script gives shift errors
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iproute2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/2018330 Title: routel script gives shift errors Status in iproute2 package in Ubuntu: Confirmed Bug description: The routel(8) shell script is meant to format the output of ip(8) commands for human viewing, but the script is not robust enough. Running 22.04.2 LTS jammy jellyfish, freshly installed on an AWS EC2 instance and then "apt upgrade"d. (It's headless and remote, so it can't submit bug reports. I generated an apport file, but have no other Ubuntu system that could re-parse it to submit the report. But it's here if it would be useful.) The iproute2 package is: iproute2: Installed: 5.15.0-1ubuntu2 Candidate: 5.15.0-1ubuntu2 Version table: *** 5.15.0-1ubuntu2 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Here's the raw output of ip(8): $ ip route list table 0 default via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.64.2 via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.64.231 via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.65.30 via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.67.0/24 dev eth0 proto kernel scope link src 10.37.67.187 metric 100 10.37.67.1 dev eth0 proto dhcp scope link src 10.37.67.187 metric 100 local 10.37.67.187 dev eth0 table local proto kernel scope host src 10.37.67.187 broadcast 10.37.67.255 dev eth0 table local proto kernel scope link src 10.37.67.187 local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 ::1 dev lo proto kernel metric 256 pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium local ::1 dev lo table local proto kernel metric 0 pref medium local fe80::458:96ff:fe61:6829 dev eth0 table local proto kernel metric 0 pref medium multicast ff00::/8 dev eth0 table local proto kernel metric 256 pref medium Running routel, however, yields this: $ routel targetgateway sourceprotoscopedev tbl default 10.37.67.110.37.67.187 dhcpeth0 10.37.64.2 10.37.67.110.37.67.187 dhcpeth0 10.37.64.231 10.37.67.110.37.67.187 dhcpeth0 10.37.65.30 10.37.67.110.37.67.187 dhcpeth0 10.37.67.0/ 2410.37.67.187 kernel link eth0 10.37.67.1 10.37.67.187 dhcp link eth0 10.37.67.187 local10.37.67.187 kernel host eth0 local 10.37.67.255 broadcast10.37.67.187 kernel link eth0 local 127.0.0.0/ 8local 127.0.0.1 kernel host lo local 127.0.0.1 local 127.0.0.1 kernel host lo local 127.255.255.255 broadcast 127.0.0.1 kernel link lo local /usr/bin/routel: 48: shift: ::1 kernel lo fe80::/ 64 kerneleth0 ::1 local kernel lo local fe80::458:96ff:fe61:6829 local kernel eth0 local can't shift that many Splitting stdout and stderr for readability: $ routel 2> /tmp/err targetgateway sourceprotoscopedev tbl default 10.37.67.110.37.67.187 dhcpeth0 10.37.64.2 10.37.67.110.37.67.187 dhcpeth0 10.37.64.231 10.37.67.110.37.67.187 dhcpeth0 10.37.65.30 10.37.67.110.37.67.187 dhcpeth0 10.37.67.0/ 2410.37.67.187 kernel link eth0 10.37.67.1 10.37.67.187 dhcp link eth0 10.37.67.187 local10.37.67.187 kernel host eth0 local 10.37.67.255 broadcast10.37.67.187 kernel link eth0 local 127.0.0.0/ 8local 127.0.0.1 kernel host lo local 127.0.0.1 local 127.0.0.1 kernel host lo local 127.255.255.255 broadcast 127.0.0.1 kernel link lo local ::1 kernel lo fe80::/ 64
[Touch-packages] [Bug 2028935] Re: Merge rsyslog 8.2306.0-2
This bug was fixed in the package rsyslog - 8.2306.0-2ubuntu2
---
rsyslog (8.2306.0-2ubuntu2) mantic; urgency=medium
* Amend list of expected messages d/rsyslog.logcheck.ignore.server
to fix armhf autopkgtest (LP: #2028935)
rsyslog (8.2306.0-2ubuntu1) mantic; urgency=medium
* Merge with Debian unstable (LP: #2028935)
* New change:
- d/test/logcheck: fix failures caused by apparmor and timing
* Remaining changes:
- d/00rsyslog.conf, d/rsyslog.postinst, d/rsyslog.install: Install
tmpfiles.d snippet to ensure that the syslog group can write into
/var/log/.
- debian/50-default.conf: set of default rules for syslog
+ debian/50-default.conf: separated default rules
+ d/rsyslog.install: install default rules
+ d/rsyslog.postrm: clear default rules on purge
+ d/rsyslog.postrm: remove conf file in postrm on purge. manage with ucf
+ d/rsyslog.postinst: Adapt script to use ucf for Ubuntu's config files
+ debian/control: Add Depends for ucf
- debian/rsyslog.conf:
+ enable $RepeatedMsgReduction to avoid bloating the syslog file.
+ enable $KLogPermitNonKernelFacility for non-kernel klog messages
+ Run as syslog:syslog, set $FileOwner to syslog
+ Remove rules moved to 50-default.conf
- Add AppArmor profile, enabled by default, with support for
AppArmor configuration snippets:
+ d/rsyslog.install: install apparmor rule
+ d/rsyslog.postinst: remove disabling of apparmor on upgrades if
we are upgrading from a version older than $now.
+ d/rules: use dh_apparmor to install profile before rsyslog is started
+ d/control: suggests apparmor (>= 2.3), Build-Depends on
dh-apparmor
+ d/rsyslog.dirs: install /etc/apparmor.d/rsyslog.d
+ d/usr.sbin.rsyslogd apparmor profile for rsyslogd
+ d/{apparmor/rsyslog-mysql,rsyslog-mysql.install}: add apparmor
profile for mysql plugin
+ d/{apparmor/rsyslog-pgsql,rsyslog-pgsql.install}: add apparmor
profile for postgresql plugin
+ d/{apparmor/rsyslog-gnutls.apparmor,rsyslog-gnutls.install}: add
apparmor profile for the gnutls plugin
+ d/{apparmor/rsyslog-openssl.apparmor,rsyslog-gnutls.install}: add
apparmor profile for the openssl plugin
+ New script to reload apparmor profile:
- d/rsyslog.service: reload apparmor profile in ExecStartPre and
set StandardError to journal so we can see errors from the
script
- d/rsyslog.install: install reload-apparmor-profile
- d/reload-apparmor-profile: script to reload the
rsyslogd apparmor profile
+ d/NEWS: add info about apparmor changes in the Ubuntu packaging
+ d/rsyslog.docs, d/README.apparmor: explains how the dynamic
component of the rsyslog apparmor profile is applied
+ d/README.apparmor.rsyslog.d, d/rsyslog.install: install a specific
README file in the apparmor include directory for rsyslog
- d/rules: Fix LDFLAGS to avoid segfault on receipt of first message
- Drop [mm|pm]normalize modules, depending on liblognorm from universe.
+ d/rules: drop --enable-mmnormalize & --enable-pmnormalize
+ d/rsyslog.install: remove mmnormalize
- run as user syslog
+ d/rsyslog.postinst: fix ownership of /var/spool/rsyslog.
+ d/rsyslog.postinst: Create syslog user and add it to adm group
+ d/rsyslog.postinst: Adapt privileges for /var/log
+ debian/control: Add Depends for adduser
- d/dmesg.service, d/rsyslog.install: provide /var/log/dmesg.log as non
log-rotated log for boot-time kernel messages.
- debian/clean: Delete some files left over by the test suite
- Add DEP8 tests (LP #1906333):
+ d/t/utils: common function(s)
+ d/t/control, d/t/simple-mysql: DEP8 test using rsyslog with a
MySQL server
+ d/t/control, d/t/simple-pgsql: DEP8 test using rsyslog with a
PostgreSQL server
+ d/t/apparmor-include-mechanism: DEP8 test for the rsyslog.d
include mechanism used by the rsyslog apparmor profile
rsyslog (8.2306.0-2) unstable; urgency=medium
[ Richard Lewis ]
* Update logcheck rules for latest debian defaults.
New patterns cope with both
- The high precision timestamps which appear in syslog (rsyslog default
since bookworm).
- The inclusion of a pid after 'rsyslogd' which is logged in the journal
(checked by logcheck since bookworm). The first two 'kernel' messages
are not generated any more but systemd generates a message about a
socket which is now captured.
(Closes: #1038163)
* Add autopkgtests (for logcheck rules).
A simple test that checks that rsyslog's logcheck rules work.
* Add debian/salsa-ci.yml
-- Heinrich Schuchardt Mon, 04 Sep
2023 15:33:45 +0200
** Changed in: rsyslog (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you
[Touch-packages] [Bug 1882466] Re: mythtv frontend crash when calling glClear in iris driver
Great, let's mark it as fixed, then. ** Changed in: mesa (Ubuntu) Status: Incomplete => Fix Released -- 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/1882466 Title: mythtv frontend crash when calling glClear in iris driver Status in mesa package in Ubuntu: Fix Released Bug description: on startup, mythfrontend crashes repeatedly when calling glClear - the following traceback: Core was generated by `/usr/bin/mythfrontend.real'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so [Current thread is 1 (Thread 0x7f9551e59940 (LWP 4164))] (gdb) bt #0 0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #1 0x7f9495ca2ebf in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x7f9495e65de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x7f9495c7ce5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f9495c7da95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f94952bc774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x7f955f79e713 in QOpenGLFunctions::glClear (this=0x555cb36e8160, mask=16384) at /usr/include/x86_64-linux-gnu/qt5/QtGui/qopenglfunctions.h:628 #7 0x7f955f798090 in MythRenderOpenGL::ClearFramebuffer ( this=0x555cb36e8150) at opengl/mythrenderopengl.cpp:801 #8 0x7f955f78a3f2 in MythOpenGLPainter::Begin (this=0x555cb398dac0, Parent=0x555cb399d1d0) at opengl/mythpainteropengl.cpp:136 I can work around this problem with this: export MESA_LOADER_DRIVER_OVERRIDE=i965 (then running mythfrontend works fine) sorry for the lack of debug symbols in iris_dri.so if there is a .deb around with a debug version i can generate the traceback again not sure if the problem belongs to iris_dri.so or to mythfrontend but I put it here due to the workaround. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 20.0.4-2ubuntu1 Candidate: 20.0.4-2ubuntu1 Version table: *** 20.0.4-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1882466/+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
