[Touch-packages] [Bug 2046026] Re: Performance problem with openssh-client
Is this now correct? ** Package changed: openssh (Ubuntu) => raspbian ** Changed in: raspbian Status: Invalid => New -- 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/2046026 Title: Performance problem with openssh-client Status in Raspbian: New Bug description: I have noticed a massive loss of performance in the openssh-client package. It has no impact on a raspberry pi 4 because it has enough CPU power, but on a pi zeroW it took about 10 seconds until the command prompt is shown to enter the password (or autologin) while CPU load is 100%. It can be reproduced very simple: On a Pi ZeroW open a terminal and connect to a ssh server. It has worked before, but then "Raspian-2" version was replaced with "-2+deb12u1" which has this problem. Working: OpenSSH_9.2p1 Raspbian-2, OpenSSL 3.0.11 19 Sep 2023 Problem: OpenSSH_9.2p1 -2+deb12u1, OpenSSL 3.0.11 19 Sep 2023 As you can see, the version number is the same. But the description is different. It looks like something like hardware acceleration is missing. If i replace /usr/bin/ssh with the "old" one it works perfect. Login prompt is shown in about 2 seconds. But with the new version it took about 10 seconds until the prompt is shown. Please let me know if you need any further information. To manage notifications about this bug go to: https://bugs.launchpad.net/raspbian/+bug/2046026/+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 2015562] Re: [SRU] Segfault in dnsmasq when using certain static domain entries + DoH (bugfix possibly exists upstream)
Hello Gordon, or anyone else affected, Accepted dnsmasq into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dnsmasq/2.86-1.1ubuntu0.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. ** Changed in: dnsmasq (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2015562 Title: [SRU] Segfault in dnsmasq when using certain static domain entries + DoH (bugfix possibly exists upstream) Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Fix Committed Bug description: [ Impact ] Some users may face an unpleasant segmentation fault if they combine configurations options like server=/domain/# with server|address=/domain/ since the domain matching functionality was rewritten in version 2.86. The special server address ’#’ means "use the standard servers". The SEGV occurs due to the struct server datastructure associated with it is passed to forward_query() call without been properly reserved and filled due to resolvconf servers didn't belong to the priority list. Without resolving this, dnsmasq stops running due to the SEGV and (non-experienced) users might not notice it. [ Test Plan ] #0.Prepare a VM or Container. i.e: # lxc launch ubuntu-daily:jammy Jdnsmasq #1. Install dnsmasq # apt update && apt upgrade -y # apt install -y dnsmasq #2. Disable systemd-resolved service and enabling resolution through dnsmasq, configuring DNS servers through it. # systemctl disable --now systemd-resolved.service # rm -f /etc/resolv.conf # cat > /etc/resolv.conf << __EOF__ nameserver 127.0.0.1 __EOF__ # echo "server=8.8.8.8" >> /etc/dnsmasq.conf (or edit the file to add it if you prefer) # (Optional) echo "log-queries" >> /etc/dnsmasq.conf # (optional) echo "log-debug" >> /etc/dnsmasq.conf # systemctl start dnsmasq.service 3. Copy netflix-nov6.conf into /etc/dnsmasq.d/ # cat > /etc/dnsmasq.d/netflix-nov6.conf << __EOF__ # Null response on these domains server=/netflix.com/# address=/netflix.com/:: server=/netflix.net/# address=/netflix.net/:: server=/nflxext.com/# address=/nflxext.com/:: server=/example.com/# address=/example.com/:: __EOF__ #4. Restart/reload dnsmasq # systemctl restart dnsmasq #5. Verify that dnsmasq resolves domains correctly: root@Jdnsmasq:~# dig +short -tA ubuntu.com @127.0.0.1 185.125.190.21 185.125.190.20 185.125.190.29 root@Jdnsmasq:~# dig +short -t ubuntu.com @127.0.0.1 2620:2d:4000:1::28 2620:2d:4000:1::26 2620:2d:4000:1::27 #6. Perform a type65 / HTTPS recordtype query for netflix.com towards the dnsmasq server twice: root@Jdnsmasq:~# dig A netflix.com @127.0.0.1 ; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> A netflix.com @127.0.0.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 48730 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; EDE: 23 (Network Error) ;; QUESTION SECTION: ;netflix.com. IN A ;; Query time: 23 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP) ;; WHEN: Wed Nov 15 16:46:19 UTC 2023 ;; MSG SIZE rcvd: 46 root@Jdnsmasq-checking:~# dig A netflix.com @127.0.0.1 ;; communications error to 127.0.0.1#53: timed out ;; communications error to 127.0.0.1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused #7. Check logs to verify segfault: # journalctl -u dnsmasq Apr 27 11:22:52 Jdnsmasq systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Apr 27 11:22:53 Jdnsmasq dnsmasq[111585]:
[Touch-packages] [Bug 2039142] Re: openssl v3.0.2 is not work with dynamic engine libengine-gost-openssl1.1
[Expired for openssl (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssl (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2039142 Title: openssl v3.0.2 is not work with dynamic engine libengine-gost- openssl1.1 Status in openssl package in Ubuntu: Expired Bug description: Hello We use from a source code the gost engine for a check certificates chains. But openssl the version 3.0.2 is not correct load dynamic engines. openssl return error "40D7F65B7F7F:error:1280006A:DSO support routines:dlfcn_bind_func:could not bind to the requested symbol name:../crypto/dso/dso_dlfcn.c:188:symname(EVP_PKEY_base_id): /usr/lib/x86_64-linux-gnu/engines-3/gost.so: undefined symbol: EVP_PKEY_base_id". We checked openssl the version 3.0.1, and 3.0.3, and 3.1.3 with the same engine. It work. In the openssl it fixed, but in the version >=3.0.3. Thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1.10 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 09:44:36 2023 InstallationDate: Installed on 2023-01-13 (271 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2039142/+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 2045705] Re: FTBFS with default Java 21
>What is the recommended source/target version that should nowadays be
used?
At the moment we can use 8 as the default.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2045705
Title:
FTBFS with default Java 21
Status in Apport:
Triaged
Status in apport package in Ubuntu:
Triaged
Bug description:
Dear Maintainers,
The package apport ftbfs with default Java 21.
The relevant part of the build log:
---
running build_java_subdir
warning: [options] bootstrap class path not set in conjunction with -source 7
error: Source option 7 is no longer supported. Use 8 or later.
error: Target option 7 is no longer supported. Use 8 or later.
Traceback (most recent call last):
File "/<>/setup.py", line 119, in
DistUtilsExtra.auto.setup(
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 125, in
setup
setuptools.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line
131, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/<>/setuptools_apport/java.py", line 35, in run
subprocess.check_call(javac + glob.glob("com/ubuntu/apport/*.java"))
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['javac', '-source', '7', '-target',
'7', 'com/ubuntu/apport/ApportUncaughtExceptionHandler.java']' returned
non-zero exit status 2.
E: pybuild pybuild:395: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p "3.12 3.11"
returned exit code 13
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2023-12-04T07:37:06Z
---
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2045705/+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 2043393] Re: Report.get_logind_session fails to determine session on cgroup2 systems
Remove skipping crashes that happened during logout: https://github.com/canonical/apport/pull/278 ** Changed in: apport Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043393 Title: Report.get_logind_session fails to determine session on cgroup2 systems Status in Apport: In Progress Status in apport package in Ubuntu: New Bug description: Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu 18.04 only cgroup version 1). Report.get_logind_session will fail to determine the logind session and always return None if only cgroup2 is used. get_logind_session searches for cgroup lines with "name=systemd:" and then extracts the session from "/session-". This worked in Ubuntu 16.04 but started failing in 18.04. Content of /proc/self/cgroup when printed from a terminal inside a Ubuntu desktop session: Ubuntu 16.04 (xenial) - ``` 12:cpuset:/ 11:perf_event:/ 10:pids:/user.slice/user-1000.slice 9:blkio:/ 8:hugetlb:/ 7:net_cls,net_prio:/ 6:cpu,cpuacct:/ 5:devices:/user.slice 4:freezer:/ 3:rdma:/ 2:memory:/ 1:name=systemd:/user.slice/user-1000.slice/session-c1.scope ``` Ubuntu 18.04 (bionic) - ``` 12:freezer:/ 11:net_cls,net_prio:/ 10:memory:/ 9:rdma:/ 8:cpu,cpuacct:/ 7:devices:/user.slice 6:perf_event:/ 5:cpuset:/ 4:pids:/user.slice/user-1000.slice/user@1000.service 3:hugetlb:/ 2:blkio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service 0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service ``` Ubuntu 20.04 (focal) - ``` 13:memory:/user.slice/user-1000.slice/user@1000.service 12:perf_event:/ 11:misc:/ 10:pids:/user.slice/user-1000.slice/user@1000.service 9:hugetlb:/ 8:cpuset:/ 7:blkio:/ 6:devices:/user.slice 5:cpu,cpuacct:/ 4:freezer:/ 3:rdma:/ 2:net_cls,net_prio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope 0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope ``` Ubuntu 22.04 (jammy) - ``` 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope ``` To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2043393/+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 2043393] Re: Report.get_logind_session fails to determine session on cgroup2 systems
** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Changed in: apport Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043393 Title: Report.get_logind_session fails to determine session on cgroup2 systems Status in Apport: New Status in apport package in Ubuntu: New Bug description: Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu 18.04 only cgroup version 1). Report.get_logind_session will fail to determine the logind session and always return None if only cgroup2 is used. get_logind_session searches for cgroup lines with "name=systemd:" and then extracts the session from "/session-". This worked in Ubuntu 16.04 but started failing in 18.04. Content of /proc/self/cgroup when printed from a terminal inside a Ubuntu desktop session: Ubuntu 16.04 (xenial) - ``` 12:cpuset:/ 11:perf_event:/ 10:pids:/user.slice/user-1000.slice 9:blkio:/ 8:hugetlb:/ 7:net_cls,net_prio:/ 6:cpu,cpuacct:/ 5:devices:/user.slice 4:freezer:/ 3:rdma:/ 2:memory:/ 1:name=systemd:/user.slice/user-1000.slice/session-c1.scope ``` Ubuntu 18.04 (bionic) - ``` 12:freezer:/ 11:net_cls,net_prio:/ 10:memory:/ 9:rdma:/ 8:cpu,cpuacct:/ 7:devices:/user.slice 6:perf_event:/ 5:cpuset:/ 4:pids:/user.slice/user-1000.slice/user@1000.service 3:hugetlb:/ 2:blkio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service 0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service ``` Ubuntu 20.04 (focal) - ``` 13:memory:/user.slice/user-1000.slice/user@1000.service 12:perf_event:/ 11:misc:/ 10:pids:/user.slice/user-1000.slice/user@1000.service 9:hugetlb:/ 8:cpuset:/ 7:blkio:/ 6:devices:/user.slice 5:cpu,cpuacct:/ 4:freezer:/ 3:rdma:/ 2:net_cls,net_prio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope 0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope ``` Ubuntu 22.04 (jammy) - ``` 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope ``` To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2043393/+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 1850804] Re: Tab completion warnings with ubuntu-bug when using alias for ls
** Changed in: apport Status: In Progress => Fix Committed ** Changed in: apport Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1850804 Title: Tab completion warnings with ubuntu-bug when using alias for ls Status in Apport: Fix Committed Status in apport package in Ubuntu: Fix Released Bug description: When running ubuntu-bug on the command line, and tab completing the package name, the following warnings are printed: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory This happens when following alias is set: alias ls='ls -N --color=yes --time-style=long-iso' ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 31 10:54:43 2019 InstallationDate: Installed on 2017-08-16 (805 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1850804/+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 2043393] Re: Report.get_logind_session fails to determine session on cgroup2 systems
** Changed in: apport Milestone: None => 2.28.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043393 Title: Report.get_logind_session fails to determine session on cgroup2 systems Status in Apport: New Status in apport package in Ubuntu: New Bug description: Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu 18.04 only cgroup version 1). Report.get_logind_session will fail to determine the logind session and always return None if only cgroup2 is used. get_logind_session searches for cgroup lines with "name=systemd:" and then extracts the session from "/session-". This worked in Ubuntu 16.04 but started failing in 18.04. Content of /proc/self/cgroup when printed from a terminal inside a Ubuntu desktop session: Ubuntu 16.04 (xenial) - ``` 12:cpuset:/ 11:perf_event:/ 10:pids:/user.slice/user-1000.slice 9:blkio:/ 8:hugetlb:/ 7:net_cls,net_prio:/ 6:cpu,cpuacct:/ 5:devices:/user.slice 4:freezer:/ 3:rdma:/ 2:memory:/ 1:name=systemd:/user.slice/user-1000.slice/session-c1.scope ``` Ubuntu 18.04 (bionic) - ``` 12:freezer:/ 11:net_cls,net_prio:/ 10:memory:/ 9:rdma:/ 8:cpu,cpuacct:/ 7:devices:/user.slice 6:perf_event:/ 5:cpuset:/ 4:pids:/user.slice/user-1000.slice/user@1000.service 3:hugetlb:/ 2:blkio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service 0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service ``` Ubuntu 20.04 (focal) - ``` 13:memory:/user.slice/user-1000.slice/user@1000.service 12:perf_event:/ 11:misc:/ 10:pids:/user.slice/user-1000.slice/user@1000.service 9:hugetlb:/ 8:cpuset:/ 7:blkio:/ 6:devices:/user.slice 5:cpu,cpuacct:/ 4:freezer:/ 3:rdma:/ 2:net_cls,net_prio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope 0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope ``` Ubuntu 22.04 (jammy) - ``` 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope ``` To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2043393/+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 2043393] Re: Report.get_logind_session fails to determine session on cgroup2 systems
I checked the bug reports against apport between 2018 and now, but I found none complaining about this regression. If no one objects (and provides a way to determine the current session and the session of a process), I will remove that code. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043393 Title: Report.get_logind_session fails to determine session on cgroup2 systems Status in Apport: New Status in apport package in Ubuntu: New Bug description: Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu 18.04 only cgroup version 1). Report.get_logind_session will fail to determine the logind session and always return None if only cgroup2 is used. get_logind_session searches for cgroup lines with "name=systemd:" and then extracts the session from "/session-". This worked in Ubuntu 16.04 but started failing in 18.04. Content of /proc/self/cgroup when printed from a terminal inside a Ubuntu desktop session: Ubuntu 16.04 (xenial) - ``` 12:cpuset:/ 11:perf_event:/ 10:pids:/user.slice/user-1000.slice 9:blkio:/ 8:hugetlb:/ 7:net_cls,net_prio:/ 6:cpu,cpuacct:/ 5:devices:/user.slice 4:freezer:/ 3:rdma:/ 2:memory:/ 1:name=systemd:/user.slice/user-1000.slice/session-c1.scope ``` Ubuntu 18.04 (bionic) - ``` 12:freezer:/ 11:net_cls,net_prio:/ 10:memory:/ 9:rdma:/ 8:cpu,cpuacct:/ 7:devices:/user.slice 6:perf_event:/ 5:cpuset:/ 4:pids:/user.slice/user-1000.slice/user@1000.service 3:hugetlb:/ 2:blkio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service 0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service ``` Ubuntu 20.04 (focal) - ``` 13:memory:/user.slice/user-1000.slice/user@1000.service 12:perf_event:/ 11:misc:/ 10:pids:/user.slice/user-1000.slice/user@1000.service 9:hugetlb:/ 8:cpuset:/ 7:blkio:/ 6:devices:/user.slice 5:cpu,cpuacct:/ 4:freezer:/ 3:rdma:/ 2:net_cls,net_prio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope 0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope ``` Ubuntu 22.04 (jammy) - ``` 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope ``` To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2043393/+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 1786475] Re: Checkbox texts are displayed in reverse order
*** This bug is a duplicate of bug 1967965 *** https://bugs.launchpad.net/bugs/1967965 ** This bug has been marked a duplicate of bug 1967965 apport-kde: "Other problem" and "Display" options are swapped -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1786475 Title: Checkbox texts are displayed in reverse order Status in apport package in Ubuntu: New Bug description: Start 'ubuntu-bug' without arguments... a pop-up appears where the text at the top is "Other problem" -- while in fact that is the checkbox at the bottom: the whole list is reversed! (the checkboxes are unrelated to the text that is printed next to it). If you select something and a new checkbox list comes up then that has the same problem. This makes it extremely hard for people to report bugs I'd think so? Unless they are able to spot this problem of course :/. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Aug 10 15:04:11 2018 InstallationDate: Installed on 2016-01-11 (941 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-08-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1786475/+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 1955178] Re: Deprecation warning from apport/report.py
*** This bug is a duplicate of bug 1947425 *** https://bugs.launchpad.net/bugs/1947425 ** This bug has been marked a duplicate of bug 1947425 Use of deprecated 'imp' module -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1955178 Title: Deprecation warning from apport/report.py Status in apport package in Ubuntu: New Bug description: /usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import fnmatch, glob, traceback, errno, sys, atexit, locale, imp, stat - I have a custom sys.excepthook installed in a private python3-based application. The above text was prepended to my exception message. Just FYI. $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.21 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 17 12:28:27 2021 InstallationDate: Installed on 2020-12-30 (351 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1955178/+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 1908011] Re: Apport crashes during handling package-hooks and re compile
Re-assinging the bug to thunderbird which ships /usr/share/apport/package-hooks/source_thunderbird.py ** Package changed: apport (Ubuntu) => thunderbird (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1908011 Title: Apport crashes during handling package-hooks and re compile Status in thunderbird package in Ubuntu: New Bug description: Below console output should be self-explaining, don't hesitate to ask for any further info nusch@xps13:/tmp$ ubuntu-bug thunderbird ERROR: hook /usr/share/apport/package-hooks/source_thunderbird.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 218, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_thunderbird.py", line 1386, in add_info if (profile.current or profile.default) and profile.addon_compat_check_disabled: File "/usr/share/apport/package-hooks/source_thunderbird.py", line 1227, in addon_compat_check_disabled is_nightly = re.sub(r'^[^\.]+\.[0-9]+([a-z0-9]*).*', r'\1', self.last_version) == 'a1' File "/usr/lib/python3.6/re.py", line 191, in sub return _compile(pattern, flags).sub(repl, string, count) TypeError: expected string or bytes-like object ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.20 Uname: Linux 5.10.0-051000rc6-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashReports: 644:0:118:316:2020-12-09 17:54:46.572232715 +0100:2020-11-25 03:58:44.990978419 +0100:/var/crash/kexec_cmd CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 02:27:16 2020 InstallationDate: Installed on 2015-05-08 (2046 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-08-26 (840 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1908011/+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 1958758] Re: Had a crash coming up when changing localization and loggin out came but window to click to send was lost upon log out, but it didnt saved anywhere?
The crashes are stored in /var/crash/. Once the crash is stored there, the apport window will be opened. So it should not be able to loose the crash at that point. ** Changed in: apport (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1958758 Title: Had a crash coming up when changing localization and loggin out came but window to click to send was lost upon log out, but it didnt saved anywhere? Status in apport package in Ubuntu: Invalid Bug description: Had a crash coming up when changing localization and loggin out came but window to click to send was lost upon log out, but it didnt saved anywhere? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-96.109~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-96-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CrashReports: 640:1000:117:441156:2022-01-22 22:28:45.490321414 +0200:2022-01-22 22:28:44.250318740 +0200:/var/crash/_bin_bash.1000.crash 640:1000:117:855333:2022-01-22 23:17:15.713448587 +0200:2022-01-22 23:17:13.649435177 +0200:/var/crash/_usr_bin_baloo_file.1000.crash 640:1000:117:24676134:2022-01-23 01:25:53.143536000 +0200:2022-01-23 01:24:31.863199843 +0200:/var/crash/_usr_bin_plasma-discover.1000.crash 640:1000:117:3187653:2022-01-23 01:37:08.210734961 +0200:2022-01-23 01:37:01.874702866 +0200:/var/crash/_usr_bin_spectacle.1000.crash 640:1000:117:4405134:2022-01-22 22:01:01.008237056 +0200:2022-01-22 22:00:57.536189532 +0200:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash CurrentDesktop: KDE Date: Sun Jan 23 06:02:42 2022 InstallationDate: Installed on 2022-01-15 (7 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1958758/+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 1959866] Re: lubuntu jammy - unable to submit bug via `ubuntu-bug calamares`
Can you retest with apport 2.20.11-0ubuntu82.5? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1959866 Title: lubuntu jammy - unable to submit bug via `ubuntu-bug calamares` Status in apport package in Ubuntu: Incomplete Bug description: Lubuntu jammy QA-test install on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) but it failed; calamares issue... No prob; file bug. I had issues filing bug, thus this additional report. ** BACKGROUND on the install & other report calamares bug filed as https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865 was filed online; then apport-collect run successfully on box. That link is now added to this report here as `apport-collect` was run during the same boot or live session as issue occurred. As noted in comment #7 (of this report) and the now provided link; a end-users filing of an install issue had me attempt a 'strange' (stupid?) install; a QA-testcase we call "install using existing partition"; https://discourse.lubuntu.me/t/testing-checklist- understanding-the-testcases/2743 where you just re-use existing partitions without format.. EXCEPT I was attempting it here with an encrypted partition... no mount or anything; just selecting in calamares)... it was this install type that no doubt led to this error. ** EXPECTED OUTCOME `ubuntu-bug calamares` and file bug report via firefox.. ** ACTUAL OUTCOME Alas `ubuntu-bug` won't work with this error --- The problem cannot be reported: Your /tmp partition has less than 32.33792 MB of free space available, which leads to problems using applications and installing updates. Please free some space. Press any key to continue... --- Full terminal session follows --- lubuntu@lubuntu:~$ ubuntu-bug calamares *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** The contents of the files attached to this report will help developers diagnose your bug more quickly. It may be possible that there is sensitive information in these files. You will be able to review these attachments before they are sent. Do you want to include these files? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y *** Problem in calamares The problem cannot be reported: Your /tmp partition has less than 32.33792 MB of free space available, which leads to problems using applications and installing updates. Please free some space. Press any key to continue... No pending crash reports. Try --help for more information. -- Note: apport-collect has NOW been run on same box; same daily ISO, but it's a later reboot/session --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: LXQt DistroRelease: Ubuntu 22.04 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) Package: apport 2.20.11-0ubuntu76 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1959866/+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 1995507] Re: List number of crashes in motd on servers
** Changed in: apport (Ubuntu) Importance: Undecided => Wishlist ** Changed in: apport (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1995507 Title: List number of crashes in motd on servers Status in apport package in Ubuntu: Triaged Bug description: To make users more aware of existing crashes that should/could be reported, please mention the number of crashes in the motd (if there are any). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1995507/+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 1995611] Re: Apport closes itself when "examine locally" or "show details"
I cannot reproduce the crash on Ubuntu 23.10 with apport 2.27.0-0ubuntu5 any more. ** Changed in: apport (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1995611 Title: Apport closes itself when "examine locally" or "show details" Status in apport package in Ubuntu: Invalid Bug description: On GNOME, run: ``` apport-bug _usr_share_apport_apport-gtk.1000.crash ``` then click on "show details" or "example locally" (install apport- retrace for it). The GTK UI will close without printing anything on stdout/stderr. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1995611/+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 2028970] Re: Apport Crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. Can you share /var/crash/_usr_share_apport_apport- gtk.0.crash? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2028970 Title: Apport Crash Status in apport package in Ubuntu: Incomplete Bug description: Powerglt crashed, but on report bug, apport-gtk crashed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport-gtk 2.20.11-0ubuntu82.5 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: GNOME Date: Fri Jul 28 11:41:11 2023 InstallationDate: Installed on 2022-09-19 (312 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2028970/+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 2028972] Re: Crash prompt dialog says that netplan script encountered an error
Do you have an apport crash file in /var/crash/ that you could
report/share?
** Changed in: apport (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2028972
Title:
Crash prompt dialog says that netplan script encountered an error
Status in apport package in Ubuntu:
Incomplete
Status in netplan.io package in Ubuntu:
Incomplete
Bug description:
I think this is on the ethernet NIC of this machine, which it is
having a problem connecting static... But generates and applies
without error.
I just replaced the motherboard from a Supermicro H8SGL-F with an AMD
Opteron 6386 SE to a MSI MPG Z790 Edge Wifi with Intel i9-13900K and
migrated the system to it: Legacy to UEFI, and LVM2 to ZFS.
This does have KVM and OpenVSwitch...
Output of Netplan Generate and Apply is:
mafoelffen@msi-ubuntu:~$ sudo netplan --debug generate
[sudo] password for mafoelffen:
DEBUG:command generate: running ['/lib/netplan/generate']
** (generate:37983): DEBUG: 11:58:12.511: starting new processing pass
** (generate:37983): DEBUG: 11:58:12.511: starting new processing pass
** (generate:37983): DEBUG: 11:58:12.511: enp5s0: adding new route
** (generate:37983): DEBUG: 11:58:12.511: We have some netdefs, pass them
through a final round of validation
** (generate:37983): DEBUG: 11:58:12.511: enp5s0: setting default backend to 1
** (generate:37983): DEBUG: 11:58:12.511: Configuration is valid
** (generate:37983): DEBUG: 11:58:12.511: Generating output files..
** (generate:37983): DEBUG: 11:58:12.511: openvswitch: definition enp5s0 is
not for us (backend 1)
** (generate:37983): DEBUG: 11:58:12.511: NetworkManager: definition enp5s0
is not for us (backend 1)
mafoelffen@msi-ubuntu:~$ sudo netplan --debug apply
** (generate:39541): DEBUG: 11:59:58.834: starting new processing pass
** (generate:39541): DEBUG: 11:59:58.834: starting new processing pass
** (generate:39541): DEBUG: 11:59:58.834: enp5s0: adding new route
** (generate:39541): DEBUG: 11:59:58.834: We have some netdefs, pass them
through a final round of validation
** (generate:39541): DEBUG: 11:59:58.834: enp5s0: setting default backend to 1
** (generate:39541): DEBUG: 11:59:58.834: Configuration is valid
** (generate:39541): DEBUG: 11:59:58.834: Generating output files..
** (generate:39541): DEBUG: 11:59:58.834: openvswitch: definition enp5s0 is
not for us (backend 1)
** (generate:39541): DEBUG: 11:59:58.834: NetworkManager: definition enp5s0
is not for us (backend 1)
DEBUG:netplan generated networkd configuration changed, reloading networkd
** (process:39539): DEBUG: 11:59:59.479: starting new processing pass
** (process:39539): DEBUG: 11:59:59.479: starting new processing pass
** (process:39539): DEBUG: 11:59:59.479: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.479: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.479: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.479: Configuration is valid
DEBUG:Merged config:
b''
DEBUG:no netplan generated NM configuration exists
** (process:39539): DEBUG: 11:59:59.490: starting new processing pass
** (process:39539): DEBUG: 11:59:59.491: starting new processing pass
** (process:39539): DEBUG: 11:59:59.491: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.491: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.491: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.491: Configuration is valid
DEBUG:Merged config:
b''
DEBUG:Link changes: {}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp5s0
DEBUG:netplan triggering .link rules for wlo1
DEBUG:netplan triggering .link rules for virbr2
DEBUG:netplan triggering .link rules for virbr1
DEBUG:netplan triggering .link rules for virbr0
DEBUG:netplan triggering .link rules for virbr3
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.604: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.604: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.604: Configuration is valid
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.604: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG:
[Touch-packages] [Bug 1517030] Re: ubuntu-bug (apport-kde) crashes every time I submit a problem report
The code change in comment #7 refers to MainUserInterface.ui_update_view. I fail to see how that change fixes a problem. Can you reproduce the failure with a recent Ubuntu version? ** Changed in: apport (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1517030 Title: ubuntu-bug (apport-kde) crashes every time I submit a problem report Status in apport package in Ubuntu: Incomplete Bug description: Every time I run the "ubuntu-bug" program, I get a crash report about it. 1. I run (say) "ubuntu-bug muon-updater" 2. Apport window appears, "Send problem report to developers?" with info about the bug. 3. Click Send. 4. "Uploading problem information" dialog appears and disappears. 5. Launchpad website appears. I start filing in details. 6. Sometime soon, Plasma reports a crash in its system tray. A dialog appears. See my screenshot. 7. I click the "Continue" button to submit a crash bug report. The dialog disappears, but nothing else happens that I can see. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport-kde 2.19.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 17 07:51:26 2015 InstallationDate: Installed on 2013-08-31 (807 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to wily on 2015-11-08 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1517030/+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 2045705] Re: FTBFS with default Java 21
** Changed in: apport (Ubuntu)
Status: New => Triaged
** Changed in: apport (Ubuntu)
Importance: Undecided => High
** Changed in: apport
Importance: Undecided => High
** Changed in: apport
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2045705
Title:
FTBFS with default Java 21
Status in Apport:
Triaged
Status in apport package in Ubuntu:
Triaged
Bug description:
Dear Maintainers,
The package apport ftbfs with default Java 21.
The relevant part of the build log:
---
running build_java_subdir
warning: [options] bootstrap class path not set in conjunction with -source 7
error: Source option 7 is no longer supported. Use 8 or later.
error: Target option 7 is no longer supported. Use 8 or later.
Traceback (most recent call last):
File "/<>/setup.py", line 119, in
DistUtilsExtra.auto.setup(
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 125, in
setup
setuptools.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line
131, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/<>/setuptools_apport/java.py", line 35, in run
subprocess.check_call(javac + glob.glob("com/ubuntu/apport/*.java"))
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['javac', '-source', '7', '-target',
'7', 'com/ubuntu/apport/ApportUncaughtExceptionHandler.java']' returned
non-zero exit status 2.
E: pybuild pybuild:395: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p "3.12 3.11"
returned exit code 13
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2023-12-04T07:37:06Z
---
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2045705/+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 2046179] Re: package linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2046179 Title: package linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: got fail massage at end up big update & just tried to auto send report here. not sure what needs to be included ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 11 12:37:24 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-02-16 (1027 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2046179/+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 2046189] [NEW] Xorg freezes on external displays when in Gnome Shell on Nvidia graphics
Public bug reported:
When using external displays, they randomly freeze, but the internal
display works just fine. Windows remain interactive, but frozen, on
external displays, and the cursor disappears.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Dec 11 15:14:50 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if
00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] TigerLake-H GT1 [UHD
Graphics] [1462:1305]
NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] GA106M [GeForce RTX 3060
Mobile / Max-Q] [1462:1305]
InstallationDate: Installed on 2022-06-28 (531 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=70390c05-b447-4e39-b596-a9f9eb4ac62b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2021
dmi.bios.release: 1.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: E17K3IMS.11B
dmi.board.asset.tag: Default string
dmi.board.name: MS-17K3
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17K3IMS.11B:bd09/15/2021:br1.27:svnMicro-StarInternationalCo.,Ltd.:pnGE76Raider11UE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17K3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17K3.1:
dmi.product.family: GE
dmi.product.name: GE76 Raider 11UE
dmi.product.sku: 17K3.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug false-gpu-hang freeze mantic ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2046189
Title:
Xorg freezes on external displays when in Gnome Shell on Nvidia
graphics
Status in xorg package in Ubuntu:
New
Bug description:
When using external displays, they randomly freeze, but the internal
display works just fine. Windows remain interactive, but frozen, on
external displays, and the cursor disappears.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Dec 11 15:14:50 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] TigerLake-H GT1 [UHD
Graphics] [1462:1305]
NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] GA106M [GeForce RTX
3060 Mobile / Max-Q] [1462:1305]
InstallationDate: Installed on 2022-06-28 (531 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']}
[Touch-packages] [Bug 2046026] Re: Performance problem with openssh-client
Yes, i think i pressed the wrong button sorry. I not often reporting bugs. Can you reproduce this bug? -- 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/2046026 Title: Performance problem with openssh-client Status in openssh package in Ubuntu: Invalid Bug description: I have noticed a massive loss of performance in the openssh-client package. It has no impact on a raspberry pi 4 because it has enough CPU power, but on a pi zeroW it took about 10 seconds until the command prompt is shown to enter the password (or autologin) while CPU load is 100%. It can be reproduced very simple: On a Pi ZeroW open a terminal and connect to a ssh server. It has worked before, but then "Raspian-2" version was replaced with "-2+deb12u1" which has this problem. Working: OpenSSH_9.2p1 Raspbian-2, OpenSSL 3.0.11 19 Sep 2023 Problem: OpenSSH_9.2p1 -2+deb12u1, OpenSSL 3.0.11 19 Sep 2023 As you can see, the version number is the same. But the description is different. It looks like something like hardware acceleration is missing. If i replace /usr/bin/ssh with the "old" one it works perfect. Login prompt is shown in about 2 seconds. But with the new version it took about 10 seconds until the prompt is shown. Please let me know if you need any further information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2046026/+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 2046026] Re: Performance problem with openssh-client
Working: OpenSSH_9.2p1 Raspbian-2, OpenSSL 3.0.11 19 Sep 2023 Problem: OpenSSH_9.2p1 -2+deb12u1, OpenSSL 3.0.11 19 Sep 2023 Neither of these are Ubuntu packages. ** Changed in: openssh (Ubuntu) Status: New => Invalid -- 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/2046026 Title: Performance problem with openssh-client Status in openssh package in Ubuntu: Invalid Bug description: I have noticed a massive loss of performance in the openssh-client package. It has no impact on a raspberry pi 4 because it has enough CPU power, but on a pi zeroW it took about 10 seconds until the command prompt is shown to enter the password (or autologin) while CPU load is 100%. It can be reproduced very simple: On a Pi ZeroW open a terminal and connect to a ssh server. It has worked before, but then "Raspian-2" version was replaced with "-2+deb12u1" which has this problem. Working: OpenSSH_9.2p1 Raspbian-2, OpenSSL 3.0.11 19 Sep 2023 Problem: OpenSSH_9.2p1 -2+deb12u1, OpenSSL 3.0.11 19 Sep 2023 As you can see, the version number is the same. But the description is different. It looks like something like hardware acceleration is missing. If i replace /usr/bin/ssh with the "old" one it works perfect. Login prompt is shown in about 2 seconds. But with the new version it took about 10 seconds until the prompt is shown. Please let me know if you need any further information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2046026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
> Is only asking kernel to scan the device; to then generate "kernel udev" > events; for then udev to wakeup and process/emit "udev udev" events; and > create the required device nodes. > It's not udev that creates nodes like /dev/loop1p1 though is it? That's devtmpfs surely. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2046026] Re: Performance problem with openssh-client
** Project changed: raspbian => openssh (Ubuntu) -- 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/2046026 Title: Performance problem with openssh-client Status in openssh package in Ubuntu: New Bug description: I have noticed a massive loss of performance in the openssh-client package. It has no impact on a raspberry pi 4 because it has enough CPU power, but on a pi zeroW it took about 10 seconds until the command prompt is shown to enter the password (or autologin) while CPU load is 100%. It can be reproduced very simple: On a Pi ZeroW open a terminal and connect to a ssh server. It has worked before, but then "Raspian-2" version was replaced with "-2+deb12u1" which has this problem. Working: OpenSSH_9.2p1 Raspbian-2, OpenSSL 3.0.11 19 Sep 2023 Problem: OpenSSH_9.2p1 -2+deb12u1, OpenSSL 3.0.11 19 Sep 2023 As you can see, the version number is the same. But the description is different. It looks like something like hardware acceleration is missing. If i replace /usr/bin/ssh with the "old" one it works perfect. Login prompt is shown in about 2 seconds. But with the new version it took about 10 seconds until the prompt is shown. Please let me know if you need any further information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2046026/+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 2046179] [NEW] package linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: got fail massage at end up big update & just tried to auto send report here. not sure what needs to be included ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 11 12:37:24 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-02-16 (1027 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2046179 Title: package linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: got fail massage at end up big update & just tried to auto send report here. not sure what needs to be included ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 11 12:37:24 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-02-16 (1027 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2046179/+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 2046026] [NEW] Performance problem with openssh-client
You have been subscribed to a public bug: I have noticed a massive loss of performance in the openssh-client package. It has no impact on a raspberry pi 4 because it has enough CPU power, but on a pi zeroW it took about 10 seconds until the command prompt is shown to enter the password (or autologin) while CPU load is 100%. It can be reproduced very simple: On a Pi ZeroW open a terminal and connect to a ssh server. It has worked before, but then "Raspian-2" version was replaced with "-2+deb12u1" which has this problem. Working: OpenSSH_9.2p1 Raspbian-2, OpenSSL 3.0.11 19 Sep 2023 Problem: OpenSSH_9.2p1 -2+deb12u1, OpenSSL 3.0.11 19 Sep 2023 As you can see, the version number is the same. But the description is different. It looks like something like hardware acceleration is missing. If i replace /usr/bin/ssh with the "old" one it works perfect. Login prompt is shown in about 2 seconds. But with the new version it took about 10 seconds until the prompt is shown. Please let me know if you need any further information. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- Performance problem with openssh-client https://bugs.launchpad.net/bugs/2046026 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh 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 2046166] Re: mesa 23.3 zink errors
** Tags removed: block-proposed ** Tags added: block-proposed-noble update-excuse -- 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/2046166 Title: mesa 23.3 zink errors Status in gtk4 package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Bug description: mesa 23.3 is emitting ZINK errors. Some initial issues were fixed which had caused autopkgtest failures for mutter and gtk4. There is still a gtk4 build test failure. My theory is that the extra ZINK stderr output is confusing the gtk:tools / validate test which is not expecting the extra errors. https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1 I am setting the block-proposed tag since I don't think we want mesa to migrate out of noble-proposed while it is causing gtk4 to fail to build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2046166/+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 2046166] [NEW] mesa 23.3 zink errors
Public bug reported: mesa 23.3 is emitting ZINK errors. Some initial issues were fixed which had caused autopkgtest failures for mutter and gtk4. There is still a gtk4 build test failure. My theory is that the extra ZINK stderr output is confusing the gtk:tools / validate test which is not expecting the extra errors. https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1 I am setting the block-proposed tag since I don't think we want mesa to migrate out of noble-proposed while it is causing gtk4 to fail to build. ** Affects: gtk4 (Ubuntu) Importance: High Status: Triaged ** Affects: mesa (Ubuntu) Importance: High Status: Triaged ** Tags: block-proposed ftbfs noble ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Description changed: mesa 23.3 is emitting ZINK errors. Some initial issues were fixed which had caused autopkgtest failures for mutter and gtk4. There is still a gtk4 build test failure. My theory is that the extra - ZINK stderr is confusing the gtk:tools / validate test which is not - expecting the extra errors. + ZINK stderr output is confusing the gtk:tools / validate test which is + not expecting the extra errors. https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1 I am setting the block-proposed tag since I don't think we want mesa to migrate out of noble-proposed while it is causing gtk4 to fail to build. ** Changed in: gtk4 (Ubuntu) Importance: Undecided => High ** Changed in: gtk4 (Ubuntu) Status: New => Triaged -- 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/2046166 Title: mesa 23.3 zink errors Status in gtk4 package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Bug description: mesa 23.3 is emitting ZINK errors. Some initial issues were fixed which had caused autopkgtest failures for mutter and gtk4. There is still a gtk4 build test failure. My theory is that the extra ZINK stderr output is confusing the gtk:tools / validate test which is not expecting the extra errors. https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1 I am setting the block-proposed tag since I don't think we want mesa to migrate out of noble-proposed while it is causing gtk4 to fail to build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2046166/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
Hello, Dave! Huge thanks for your attention to this bug! >The major thing that I think needs correction is that this patch is built on top of ubuntu/noble-devel by importing the upstream 5.0.3, but what Stéphane suggested in comment 14 was to take the Debian upstream (currently 5.0.3-2) and build on top of that. Ah, yes. My bad. I guess that I can easily fix that. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Confirmed Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
Thanks very much for the updated debdiff. There's a lot of changes here to look at and unfortunately I've run out of time looking through it all during my patch-pilot shift, but here's what I've got so far: The major thing that I think needs correction is that this patch is built on top of ubuntu/noble-devel by importing the upstream 5.0.3, but what Stéphane suggested in comment 14 was to take the Debian upstream (currently 5.0.3-2) and build on top of that. In this case, the commits in the repo would be based on debian/sid rather than ubuntu/noble-devel. This would ensure we incorporate the changes Debian has placed on top of lxc, as well as our own (and means in future we can follow the git- ubuntu merge process for this package). The proposed changes also include package renames (which will be necessary if we're basing off the upstream Debian version). As far as I can tell they look sane but I haven't dug deep into this bit yet (it's something I always need to read the policy guides and manuals for!). The requested autopkgtest to ensure LXC_DEVEL==0 is present, and looks good. I have to dash to an appointment now, but I'll try and add some more notes later this evening. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Confirmed Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
If you have a bunch of unmanaged interfaces, then you should use a drop- in configuration to pass the --any flag to systemd-networkd-wait-online: cat > /etc/systemd/system/systemd-networkd-wait-online.service.d/any.conf << EOF [Service] ExecStart= ExecStart=/lib/systemd/systemd-networkd-wait-online --any EOF This makes it so that systemd-networkd-wait-online will return success once at least one interface becomes configured. -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated
This bug was fixed in the package lomiri-download-manager - 0.1.2-2ubuntu1 --- lomiri-download-manager (0.1.2-2ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2045635). Remaining changes: - debian/*.symbols: + Remove; upstream is C++ and does not aggressively manage their exported symbols, so these are unhepfully compiler-version-, architecture-, and compiler-option-dependent. The debhelper-compat 13 default of -VUpstream-Version is sufficient. - debian/rules: - debian/control: + Drop pkgkde_symbolshelper; no longer used to (try to) manage the symbols. * Replace deprecated calls to GetConnectionAppArmorSecurityContext by calls to GetConnectionCredentials (LP: #1489489). -- Olivier Gayot Tue, 05 Dec 2023 10:20:56 +0100 ** Changed in: lomiri-download-manager (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1489489 Title: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated Status in Ubuntu Online Accounts API: Confirmed Status in snapd: Confirmed Status in apparmor package in Ubuntu: Fix Released Status in biometryd package in Ubuntu: New Status in content-hub package in Ubuntu: Confirmed Status in dbus package in Ubuntu: Triaged Status in deepin-notifications package in Ubuntu: New Status in lomiri-download-manager package in Ubuntu: Fix Released Status in mediascanner2 package in Ubuntu: Fix Released Status in signon-apparmor-extension package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Bug description: When upstream D-Bus merged the AppArmor mediation patches, they did not like the GetConnectionAppArmorSecurityContext() bus method. Instead, they decided to expose a peer's AppArmor context using the org.freedesktop.DBus.GetConnectionCredentials() bus method. All users of the GetConnectionAppArmorSecurityContext() method should switch to the GetConnectionCredentials() method as soon as possible so that Ubuntu can drop the patch that implements GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is released. In order to switch to the new method, you'll need to depend on libapparmor 2.10 or newer. I'll be adding example code that illustrates how to switch from GetConnectionAppArmorSecurityContext() to GetConnectionCredentials(). content-hub, media-hub, mediascanner2, signon-apparmor-extension, ubuntu-download-manager, and ubuntu-system-settings-online-accounts all need to transition to the new method of obtaining the AppArmor label. The apparmor package should be updated to drop the libapparmor- mention-dbus-method-in-getcon-man.patch patch and the dbus package should be updated to drop the aa-get-connection-apparmor-security- context.patch patch. To manage notifications about this bug go to: https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+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 2009071] Re: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all
I have a Razor Blade 16 (2023). I ran the script linked in issue #4055 (https://pastebin.com/45ksYAXX) but still do not hear any sound from the speakers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2009071 Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: New install of Ubuntu 22.04 has no audio. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1793 F pulseaudio /dev/snd/controlC1: mblack 1793 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Thu Mar 2 13:21:20 2023 InstallationDate: Installed on 2023-03-02 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1793 F pulseaudio /dev/snd/controlC1: mblack 1793 F pulseaudio mblack 8091 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Razer dmi.bios.version: 1.07 dmi.board.name: SO690 dmi.board.vendor: Razer dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnRazer:bvr1.07:bd01/27/2023:br1.7:efr1.3:svnRazer:pnBlade16-RZ09-0483:pvr9.04:rvnRazer:rnSO690:rvr4:cvnRazer:ct10:cvr:skuRZ09-0483SEJ3: dmi.product.family: 1A583006 Razer Blade dmi.product.name: Blade 16 - RZ09-0483 dmi.product.sku: RZ09-0483SEJ3 dmi.product.version: 9.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2009071/+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 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
** Description changed:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
- version: 2
- tunnels:
- wg0:
- renderer: NetworkManager
- addresses:
- - "10.0.0.2/24"
- mode: "wireguard"
- port: 51820
- keys:
- private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
- peers:
- - keys:
- public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
- allowed-ips:
- - "10.0.0.1/32"
- networkmanager:
- uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
- name: "con-wg0"
- passthrough:
- ipv6.addr-gen-mode: "default"
- ipv6.method: "disabled"
- ipv6.ip6-privacy: "-1"
- proxy._: ""
-
+ version: 2
+ tunnels:
+ wg0:
+ renderer: NetworkManager
+ addresses:
+ - "10.0.0.2/24"
+ mode: "wireguard"
+ port: 51820
+ keys:
+ private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
+ peers:
+ - keys:
+ public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
+ allowed-ips:
+ - "10.0.0.1/32"
+ networkmanager:
+ uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
+ name: "con-wg0"
+ passthrough:
+ ipv6.addr-gen-mode: "default"
+ ipv6.method: "disabled"
+ ipv6.ip6-privacy: "-1"
+ proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
-
- Now the UI modifies the "allowed-ips" setting to ["10.0.0.1", "2001::1"].
Notably the addresses do *not* have a netmask, neither in the original config
nor that update. Unfortunately that update cannot be done on the CLI:
+ Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
+ "2001::1"]. Notably the addresses do *not* have a netmask, neither in
+ the original config nor that update. Unfortunately that update cannot be
+ done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
-
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
+ But this generates a wrong "/32" default netmask in the netplan config
+ for the IPv6 address:
- But this generates a wrong "/32" default netmask in the netplan config for
the IPv6 address:
-
- allowed-ips:
- - "10.0.0.1/32"
- - "2001::1/32"
+ allowed-ips:
+ - "10.0.0.1/32"
+ - "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is not
added on this call. The netplan backend should do that (not second-
guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour
[Touch-packages] [Bug 2046158] [NEW] Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
Public bug reported:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
ipv6.addr-gen-mode: "default"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
Now the UI modifies the "allowed-ips" setting to ["10.0.0.1", "2001::1"].
Notably the addresses do *not* have a netmask, neither in the original config
nor that update. Unfortunately that update cannot be done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
But this generates a wrong "/32" default netmask in the netplan config for the
IPv6 address:
allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is not
added on this call. The netplan backend should do that (not second-
guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch it
together, but I hope your unit tests make this easier somehow.
This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.
DistroRelease: Ubuntu 23.04
Package: network-manager 1.44.2-1ubuntu1.2
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: mantic regression-release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask for
IPv6 addresses
Status in network-manager package in Ubuntu:
New
Bug description:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only
connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public:
[Touch-packages] [Bug 2045577] Re: Demote isc-dhcp-server to universe
For some reason, this got back in main. I believe there is no easy/public way to track how/why it ended back in main? Can we demote it again? ** Changed in: isc-dhcp (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2045577 Title: Demote isc-dhcp-server to universe Status in isc-dhcp package in Ubuntu: Triaged Bug description: Following up on the isc-kea promotion (LP: #2002861) as the new supported DHCP server, it is now time to demote isc-dhcp-server. All the packages that are in. While we are not ready to demote all isc-dhcp packages (there are still packages in main that reverse depend/recommend isc-dhcp-client), we are ready to demote isc-dhcp-server. $ reverse-depends isc-dhcp-server Reverse-Recommends == * fai-server Reverse-Depends === * fai-quickstart * isc-dhcp-server-ldap [amd64 arm64 armhf ppc64el s390x] Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -b isc-dhcp-server Reverse-Testsuite-Triggers == * chrony * dracut As shown there are no reverse dependencies for isc-dhcp-server in main. There are Reverse-Testsuite-Triggers in main, but these should not be considered for demotion matters here. The seeds at https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/tree/?h=noble contain 2 entries for isc-dhcp- server: $ grep -r isc-dhcp-server * supported-maas: * isc-dhcp-server supported-misc-servers: * isc-dhcp-server I will proceed with removing the supported-misc-servers entry. Once this is removed from supported-maas, the package will no longer be seeded (we should then get a component mismatch) and can be safely demoted to universe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2045577/+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 2045033] Re: Merge rsyslog 8.2310.0-2 from Debian
Merge request https://github.com/rsyslog/rsyslog/pull/5290 was merged upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2045033 Title: Merge rsyslog 8.2310.0-2 from Debian Status in rsyslog package in Ubuntu: New Bug description: Debian has released rsyslog 8.2310.0-4. Merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2045033/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
I don't have a good explanation, but in the past I've "fixed" such races by adding a `sync "$loop_device"` before using any of the newly created partitons. Maybe it's worth trying. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
my expectation is that udev should be running (somewhere, not sure if it needs to be both the host and the lxd guest) and that it should process the device using locks https://systemd.io/BLOCK_DEVICE_LOCKING/. After that is done, the device should be safe to operate on, in a consistent manner. After all, -P, --partscan Force the kernel to scan the partition table on a newly created loop device. Note that the partition table parsing depends on sector sizes. The default is sector size is 512 bytes, otherwise you need to use the option --sector-size together with --partscan. Is only asking kernel to scan the device; to then generate "kernel udev" events; for then udev to wakeup and process/emit "udev udev" events; and create the required device nodes. We have always been fixing and supporting running udev inside the lxd containers, because of such things (in contexts of priviledged containers, but outside of lp-buildd) to make all of this work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Looks like this is a reported regression in the security pocket. ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Confirmed Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Reopening because a PIN of is not reported to work (and even if it did, that would still be a regression in a stable release). ** Changed in: bluez (Ubuntu) Status: Incomplete => Confirmed ** Changed in: bluez (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Confirmed Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2045250] Comment bridged from LTC Bugzilla
--- Comment From holger.deng...@ibm.com 2023-12-11 02:24 EDT---
Even if the problem can be reproduced easier on 32-bit architectures, the
architecture doesn't matter at all. If you do a syscall in userspace programs,
you have to check the returned value for errors. Period.
In my opinion, the fix for the problem is trivial (just do not call
strftime() with a NULL pointer), so the reproduction of a failure and a
test of the fix can be skipped here. It is more important, that the fix
is pushed into the field as soon as possible.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2045250
Title:
pam_lastlog doesn't handle localtime_r related errors properly
Status in pam package in Ubuntu:
New
Status in pam package in Fedora:
Fix Released
Bug description:
The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to
noble) are affected by
https://bugzilla.redhat.com/show_bug.cgi?id=2012871
Customers report a command going through PAM crashing for a given user.
A potential follow on issue can be that no ssh remote connections to an
affected server are possible anymore, esp. painful with headless systems (was
reported on a different distro).
This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
with tm = localtime_r(...) that can be NULL and needs to be handled.
There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
314- ll_time = last_login.ll_time;
315: if ((tm = localtime_r (_time, _buf)) != NULL) {
316- strftime (the_time, sizeof (the_time),
317- /* TRANSLATORS: "strftime options for date of last
login" */
--
574-
575- lf_time = utuser.ut_tv.tv_sec;
576: tm = localtime_r (_time, _buf);
577- strftime (the_time, sizeof (the_time),
578- /* TRANSLATORS: "strftime options for date of last login" */
Case 1 (line 315) is properly handled, but not case 2 (line 576).
The second case got fixed by:
https://github.com/linux-pam/linux-pam/commit/40c271164dbcebfc5304d0537a42fb42e6b6803c
This fix should be included in Ubuntu (and Debian).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2045250/+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
