[Touch-packages] [Bug 1959488] Re: Error loading key ".../id_ed25519.pub": error in libcrypto
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- 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/1959488 Title: Error loading key ".../id_ed25519.pub": error in libcrypto Status in openssh package in Ubuntu: Expired Bug description: I can't add my ED25519 ssh-key to my ssh-agent. I am getting this error message: user@pc:~$ ssh-add ~/.ssh/id_ed25519.pub Error loading key "/home/user/.ssh/id_ed25519.pub": error in libcrypto I have setup key agent for KDE like this: user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-agent.sh #!/bin/bash [ -n "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -s)" user@pc:~$ cat ~/.config/plasma-workspace/env/ssh-askpass.sh #!/bin/bash [ -n "$SSH\_ASKPASS" ] || export SSH\_ASKPASS=/usr/bin/ksshaskpass user@pcc:~$ cat ~/.config/plasma-workspace/shutdown/ssh-agent-shutdown.sh #!/bin/bash [ -z "$SSH\_AGENT\_PID" ] || eval "$(ssh-agent -k)" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-client 1:8.7p1-4 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jan 29 16:43:55 2022 InstallationDate: Installed on 2022-01-21 (7 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.7p1 Ubuntu-4, OpenSSL 3.0.1 14 Dec 2021 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1959488/+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 1967565] Re: upower takes long time to detect laptop AC charger plugged in
Thank you for your suggestion. I have reported the issue upstream here: https://gitlab.freedesktop.org/upower/upower/-/issues/179 ** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #179 https://gitlab.freedesktop.org/upower/upower/-/issues/179 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1967565 Title: upower takes long time to detect laptop AC charger plugged in Status in upower package in Ubuntu: New Bug description: upower takes a really long time (around 1-2 minutes) to detect when an AC charger is plugged-in. 'upower -d' shows battery state as discharging after AC charger is plugged-in. 'systemctl restart upower.service' would update the status immediately as charging. Otherwise, it takes 1-2 minutes before upower updates the status. Laptop Model: Acer Aspire E15 E5-573G-56JN Laptop battery and AC charger is not faulty as the charging/discharging status gets correctly detected when using Windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 1 23:07:12 2022 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1967565/+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 1871538] Autopkgtest regression report (systemd/248.3-1ubuntu8.5)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.5) for impish have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.54.3+21.10.1ubuntu0.2 (s390x, ppc64el, arm64, amd64) casper/1.465 (amd64) tpm2-abrmd/unknown (ppc64el) corosync-qdevice/unknown (ppc64el) nftables/unknown (ppc64el) udisks2/2.9.4-1 (arm64) diaspora-installer/0.7.15.0+debian1 (arm64, s390x) systemd/248.3-1ubuntu8.5 (armhf) swupdate/2020.11-2 (s390x) munin/2.0.57-1ubuntu1 (arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that
[Touch-packages] [Bug 1955997] Autopkgtest regression report (systemd/248.3-1ubuntu8.5)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.5) for impish
have finished running.
The following regressions have been reported in tests triggered by the package:
snapd/2.54.3+21.10.1ubuntu0.2 (s390x, ppc64el, arm64, amd64)
casper/1.465 (amd64)
tpm2-abrmd/unknown (ppc64el)
corosync-qdevice/unknown (ppc64el)
nftables/unknown (ppc64el)
udisks2/2.9.4-1 (arm64)
diaspora-installer/0.7.15.0+debian1 (arm64, s390x)
systemd/248.3-1ubuntu8.5 (armhf)
swupdate/2020.11-2 (s390x)
munin/2.0.57-1ubuntu1 (arm64, amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/impish/update_excuses.html#systemd
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1955997
Title:
The airplane hotkey has no function on a HP platform
Status in OEM Priority Project:
Fix Committed
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Impish:
Fix Committed
Status in systemd source package in Jammy:
Fix Released
Bug description:
[Impact]
The airplane hokey doesn't work on HP new generation machines.
[Test Plan]
Press airplane hokey.
Before the patch, nothing happens.
After the patch, the rfkill works as expected.
In some old HP platforms (contains Intel-HID and HPQ6001 in same
machine), the user will aware the airplane mode toggled very quickly
e.g. turn-on and turn-off immediately (or works good without problem,
depends on how DM handles multiple rfkill events).
In this case, you could check:
1. sudo evtest
# You probably could see
# ...
# /dev/input/event8: Intel HID events
# ...
# /dev/input/event11: Wireless hotkeys
# or "HP Wireless hotkeys" depends on your kernel version
2. try to listen these events when pressing airplane key, you will
probably see these two events will send the keycode out.
3. check the components own this event
$ sudo udevadm info -a /dev/input/event11
# ...
# ATTRS{phys}=="hpq6001/input0"
$ sudo udevadm info -a /dev/input/event8
# ...
#DRIVERS=="intel-hid"
4. check your hwdb is affect.
$ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
# If you didn't see anything then it means your intel-hid is unmask.
5. You could report a bug to your DM for dealing with two rfkill events (same
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as
workaround (but it will be overwritten in next upgrade) by adding:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
```
to /lib/udev/hwdb.d/60-keyboard.hwdb
then
$ systemd-hwdb update
$ udevadm trigger
[Where problems could occur]
In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will
not work but HP confirmed the new HP generation won't contain the HPQ6001 and
also each DM still need to deal with multi-rfkill events because upstream
changes[2].
---
In the last year, HP mentions HP machines need to use hp-wireless
(HPQ6001) as the rfkill source[1].
However, HP confirms the HPQ6001 has been retired in the platforms
since 2022.
In the platforms after 2022, there are two sources of rkfill events
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
Therefore, the upstream already accept the patch[2] to unmask intel-hid and
mention this big change in the NEWS.
This change makes the pre-2022 HP platforms meet the regression since they
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing
function key.
Thus, there is a patch[3] to make sure the GNOME could deal with this case
smoothly.
However, the systemd change will still cause other DEs meet the regression
(xfce, KDE, lxde, etc..).
Backport systemd change to make HP 2022 platforms work is not the best choice
on stable version (focal in this case).
We still need a solution to make airplane key works on 2022 HP platforms
(intel-hid and atkbd only).
The potential solution from my mind that is to maintain a whitelist to unmask
intel-hid in ubuntu-patch in focal, something like:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
KEYBOARD_KEY_8=wlan # Use hp-wireless instead
```
after "KEYBOARD_KEY_8=unkown".
[1] https://bugs.launchpad.net/bugs/1883846
[2] https://github.com/systemd/systemd/pull/20219
[3]
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda
To manage notifications about this bug go to:
[Touch-packages] [Bug 1962038] Autopkgtest regression report (systemd/248.3-1ubuntu8.5)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.5) for impish have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.54.3+21.10.1ubuntu0.2 (s390x, ppc64el, arm64, amd64) casper/1.465 (amd64) tpm2-abrmd/unknown (ppc64el) corosync-qdevice/unknown (ppc64el) nftables/unknown (ppc64el) udisks2/2.9.4-1 (arm64) diaspora-installer/0.7.15.0+debian1 (arm64, s390x) systemd/248.3-1ubuntu8.5 (armhf) swupdate/2020.11-2 (s390x) munin/2.0.57-1ubuntu1 (arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962038 Title: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf Status in procps package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in procps source package in Impish: Won't Fix Status in systemd source package in Impish: Fix Committed Status in procps source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] I've just learned that systemd is setting kernel.sysrq to 16 in /usr/lib/sysctl.d/50-default.conf. This is inconsistent with /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176 by default. systemd should drop its setting to defer to the file that we have been carrying in procps for a very long time. Therefore, users can only sync their storage but not do any other actions using the magic sysrq key. [Test Plan] $ sysctl kernel.sysrq => This should show "kernel.sysrq = 176" as set by /etc/sysctl.d/10-magic-sysrq.conf $ sysctl net.ipv4.conf.all.rp_filter => This should show "net.ipv4.conf.all.rp_filter=2" as set by /etc/sysctl.d/10-network-security.conf [Where problems could occur] * This patch changes systemd's sysctl configuration in /lib/sysctl.d/*.conf * If something is broken it could fail to apply any of systemd's sysctl configuration, but Ubuntu's defaults from /etc/sysctl.d/*.conf would still be in place. [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1962038/+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 1967576] Autopkgtest regression report (systemd/248.3-1ubuntu8.5)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.5) for impish have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.54.3+21.10.1ubuntu0.2 (s390x, ppc64el, arm64, amd64) casper/1.465 (amd64) tpm2-abrmd/unknown (ppc64el) corosync-qdevice/unknown (ppc64el) nftables/unknown (ppc64el) udisks2/2.9.4-1 (arm64) diaspora-installer/0.7.15.0+debian1 (arm64, s390x) systemd/248.3-1ubuntu8.5 (armhf) swupdate/2020.11-2 (s390x) munin/2.0.57-1ubuntu1 (arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1967576 Title: systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount units Status in systemd package in Ubuntu: New Status in systemd source package in Impish: Fix Committed Bug description: This build log provides an example of the problem: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/ppc64el/s/systemd/20220331_190433_fdbbe@/log.gz. During setup for tests-in-lxd, an attempt is made to purge snapd, but this fails: [ ... ] Purging configuration files for snapd (2.54.3+21.10.1ubuntu0.2) ... Stopping snap.lxd.activate.service Stopping unit snap.lxd.activate.service Waiting until unit snap.lxd.activate.service is stopped [attempt 1] snap.lxd.activate.service is stopped. Removing snap.lxd.activate.service Stopping snap.lxd.daemon.service Stopping unit snap.lxd.daemon.service Waiting until unit snap.lxd.daemon.service is stopped [attempt 1] snap.lxd.daemon.service is stopped. Removing snap.lxd.daemon.service Stopping snap.lxd.user-daemon.service Stopping unit snap.lxd.user-daemon.service Waiting until unit snap.lxd.user-daemon.service is stopped [attempt 1] snap.lxd.user-daemon.service is stopped. Removing snap.lxd.user-daemon.service Stopping snap-core20-1378.mount Stopping unit snap-core20-1378.mount Waiting until unit snap-core20-1378.mount is stopped [attempt 1] snap-core20-1378.mount is stopped. Removing snap core20 and revision 1378 Removing snap-core20-1378.mount Stopping snap-lxd-22672.mount Stopping unit snap-lxd-22672.mount Waiting until unit snap-lxd-22672.mount is stopped [attempt 1] snap-lxd-22672.mount is stopped. Removing snap lxd and revision 22672 rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/meminfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/stat': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/uptime': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/diskstats': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/swaps': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/loadavg': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/slabinfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpu0': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpuidle': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/uevent': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/svm': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/hotplug': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/offline': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/present': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/power': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/dscr_default': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/probe': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/smt': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/vulnerabilities': Operation not permitted rm: cannot remove
[Touch-packages] [Bug 1967521] Re: Test binaries in libsndfile-dev package
Ok, thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1967521 Title: Test binaries in libsndfile-dev package Status in libsndfile package in Ubuntu: New Bug description: There are programs from the libsndfile test suite in dev package. Should they be there? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1967521/+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 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
Ubuntu 22.04. I still have this problem intel-media-va-driver 22.3.0 tigerlake laptop $ apt-cache show intel-media-va-driver Package: intel-media-va-driver Architecture: amd64 Version: 22.3.0+dfsg1-1 tim@ochre:~$ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit tim@ochre:~$ -- 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/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Status in intel-media-driver package in Ubuntu: Fix Released Status in intel-media-driver-non-free package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Bug description: I noticed that it upgraded mesa to 22.x and now video acceleration is not working due to: ❯ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit ~/Desktop ❯ inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Device-2: Generalplus GENERAL WEBCAM type: USB driver: snd-usb-audio,uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2) v: 4.6 Mesa 22.0.0 I tried rebuilding the i965-va-driver, and it's still the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mesa-vdpau-drivers 22.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 10:37:41 2022 DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-10-05 (172 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago) dmi.bios.date: 07/08/2021 dmi.bios.release: 23.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: Default string dmi.board.name: Pro WS W480-ACE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
[Touch-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
** Changed in: webkit Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Unknown Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+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 1966418]
(In reply to Marian Rainer-Harbach from comment #7) > This issue occurs on my machine as well, which has an AMD GPU. So it does > not seem to be directly related to the graphics driver in use. Beware: if you're not certain the issue is caused by the same mesa 21.3 -> 22.0 upgrade, you might have a different underlying issue. Anyway, I'm going to close this as MOVED since the issue is being tracked by mesa now and it seems unlikely that WebKit developers will be able to help more. We can reopen if the mesa issue gets closed. -- 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/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Unknown Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+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 1966418]
This issue occurs on my machine as well, which has an AMD GPU. So it does not seem to be directly related to the graphics driver in use. -- 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/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Unknown Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+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 1965673] Re: Object 0x... of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management
Sounds like https://github.com/ibus/ibus/pull/2394 might fix the issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1965673 Title: Object 0x... of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management Status in ibus: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch @ 20/03/2022 Journal logs spam a lot of lines like these: mrt 20 13:36:38 R00TB00K gnome-shell[3452]: Object 0x7f896cf7cad0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mrt 20 13:36:38 R00TB00K gnome-shell[3452]: Object 0x557a992efd20 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management Probably regression bug upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5147 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:34:37 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1965673/+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 1850667] Re: Switch to "unified" cgroup hierarchy (cgroupv2)
** Changed in: lxc Importance: Undecided => Unknown -- 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/1850667 Title: Switch to "unified" cgroup hierarchy (cgroupv2) Status in lxc: Fix Released Status in lxd: Fix Released Status in docker.io package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in lxc package in Debian: Fix Released Status in systemd package in Debian: Fix Released Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1850667/+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 1955997] Autopkgtest regression report (systemd/248.3-1ubuntu8.4)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.4) for impish
have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/248.3-1ubuntu8.4 (arm64, ppc64el)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/impish/update_excuses.html#systemd
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1955997
Title:
The airplane hotkey has no function on a HP platform
Status in OEM Priority Project:
Fix Committed
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Impish:
Fix Committed
Status in systemd source package in Jammy:
Fix Released
Bug description:
[Impact]
The airplane hokey doesn't work on HP new generation machines.
[Test Plan]
Press airplane hokey.
Before the patch, nothing happens.
After the patch, the rfkill works as expected.
In some old HP platforms (contains Intel-HID and HPQ6001 in same
machine), the user will aware the airplane mode toggled very quickly
e.g. turn-on and turn-off immediately (or works good without problem,
depends on how DM handles multiple rfkill events).
In this case, you could check:
1. sudo evtest
# You probably could see
# ...
# /dev/input/event8: Intel HID events
# ...
# /dev/input/event11: Wireless hotkeys
# or "HP Wireless hotkeys" depends on your kernel version
2. try to listen these events when pressing airplane key, you will
probably see these two events will send the keycode out.
3. check the components own this event
$ sudo udevadm info -a /dev/input/event11
# ...
# ATTRS{phys}=="hpq6001/input0"
$ sudo udevadm info -a /dev/input/event8
# ...
#DRIVERS=="intel-hid"
4. check your hwdb is affect.
$ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
# If you didn't see anything then it means your intel-hid is unmask.
5. You could report a bug to your DM for dealing with two rfkill events (same
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as
workaround (but it will be overwritten in next upgrade) by adding:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
```
to /lib/udev/hwdb.d/60-keyboard.hwdb
then
$ systemd-hwdb update
$ udevadm trigger
[Where problems could occur]
In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will
not work but HP confirmed the new HP generation won't contain the HPQ6001 and
also each DM still need to deal with multi-rfkill events because upstream
changes[2].
---
In the last year, HP mentions HP machines need to use hp-wireless
(HPQ6001) as the rfkill source[1].
However, HP confirms the HPQ6001 has been retired in the platforms
since 2022.
In the platforms after 2022, there are two sources of rkfill events
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
Therefore, the upstream already accept the patch[2] to unmask intel-hid and
mention this big change in the NEWS.
This change makes the pre-2022 HP platforms meet the regression since they
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing
function key.
Thus, there is a patch[3] to make sure the GNOME could deal with this case
smoothly.
However, the systemd change will still cause other DEs meet the regression
(xfce, KDE, lxde, etc..).
Backport systemd change to make HP 2022 platforms work is not the best choice
on stable version (focal in this case).
We still need a solution to make airplane key works on 2022 HP platforms
(intel-hid and atkbd only).
The potential solution from my mind that is to maintain a whitelist to unmask
intel-hid in ubuntu-patch in focal, something like:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
KEYBOARD_KEY_8=wlan # Use hp-wireless instead
```
after "KEYBOARD_KEY_8=unkown".
[1] https://bugs.launchpad.net/bugs/1883846
[2] https://github.com/systemd/systemd/pull/20219
[3]
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+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 1871538] Autopkgtest regression report (systemd/248.3-1ubuntu8.4)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.4) for impish have finished running. The following regressions have been reported in tests triggered by the package: systemd/248.3-1ubuntu8.4 (arm64, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully
[Touch-packages] [Bug 1962038] Autopkgtest regression report (systemd/248.3-1ubuntu8.4)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.4) for impish have finished running. The following regressions have been reported in tests triggered by the package: systemd/248.3-1ubuntu8.4 (arm64, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962038 Title: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf Status in procps package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in procps source package in Impish: Won't Fix Status in systemd source package in Impish: Fix Committed Status in procps source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] I've just learned that systemd is setting kernel.sysrq to 16 in /usr/lib/sysctl.d/50-default.conf. This is inconsistent with /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176 by default. systemd should drop its setting to defer to the file that we have been carrying in procps for a very long time. Therefore, users can only sync their storage but not do any other actions using the magic sysrq key. [Test Plan] $ sysctl kernel.sysrq => This should show "kernel.sysrq = 176" as set by /etc/sysctl.d/10-magic-sysrq.conf $ sysctl net.ipv4.conf.all.rp_filter => This should show "net.ipv4.conf.all.rp_filter=2" as set by /etc/sysctl.d/10-network-security.conf [Where problems could occur] * This patch changes systemd's sysctl configuration in /lib/sysctl.d/*.conf * If something is broken it could fail to apply any of systemd's sysctl configuration, but Ubuntu's defaults from /etc/sysctl.d/*.conf would still be in place. [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1962038/+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 1871538] Please test proposed package
Hello Christian, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one.
[Touch-packages] [Bug 1962038] Re: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf
Hello Steve, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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. ** Tags removed: verification-done-impish ** Tags added: verification-needed-impish -- 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/1962038 Title: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf Status in procps package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in procps source package in Impish: Won't Fix Status in systemd source package in Impish: Fix Committed Status in procps source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] I've just learned that systemd is setting kernel.sysrq to 16 in /usr/lib/sysctl.d/50-default.conf. This is inconsistent with /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176 by default. systemd should drop its setting to defer to the file that we have been carrying in procps for a very long time. Therefore, users can only sync their storage but not do any other actions using the magic sysrq key. [Test Plan] $ sysctl kernel.sysrq => This should show "kernel.sysrq = 176" as set by /etc/sysctl.d/10-magic-sysrq.conf $ sysctl net.ipv4.conf.all.rp_filter => This should show "net.ipv4.conf.all.rp_filter=2" as set by /etc/sysctl.d/10-network-security.conf [Where problems could occur] * This patch changes systemd's sysctl configuration in /lib/sysctl.d/*.conf * If something is broken it could fail to apply any of systemd's sysctl configuration, but Ubuntu's defaults from /etc/sysctl.d/*.conf would still be in place. [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1962038/+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 1955997] Re: The airplane hotkey has no function on a HP platform
Hello jeremyszu, or anyone else affected,
Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. 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.
** Tags removed: verification-done verification-done-impish
** Tags added: verification-needed verification-needed-impish
--
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/1955997
Title:
The airplane hotkey has no function on a HP platform
Status in OEM Priority Project:
Fix Committed
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Impish:
Fix Committed
Status in systemd source package in Jammy:
Fix Released
Bug description:
[Impact]
The airplane hokey doesn't work on HP new generation machines.
[Test Plan]
Press airplane hokey.
Before the patch, nothing happens.
After the patch, the rfkill works as expected.
In some old HP platforms (contains Intel-HID and HPQ6001 in same
machine), the user will aware the airplane mode toggled very quickly
e.g. turn-on and turn-off immediately (or works good without problem,
depends on how DM handles multiple rfkill events).
In this case, you could check:
1. sudo evtest
# You probably could see
# ...
# /dev/input/event8: Intel HID events
# ...
# /dev/input/event11: Wireless hotkeys
# or "HP Wireless hotkeys" depends on your kernel version
2. try to listen these events when pressing airplane key, you will
probably see these two events will send the keycode out.
3. check the components own this event
$ sudo udevadm info -a /dev/input/event11
# ...
# ATTRS{phys}=="hpq6001/input0"
$ sudo udevadm info -a /dev/input/event8
# ...
#DRIVERS=="intel-hid"
4. check your hwdb is affect.
$ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
# If you didn't see anything then it means your intel-hid is unmask.
5. You could report a bug to your DM for dealing with two rfkill events (same
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as
workaround (but it will be overwritten in next upgrade) by adding:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
```
to /lib/udev/hwdb.d/60-keyboard.hwdb
then
$ systemd-hwdb update
$ udevadm trigger
[Where problems could occur]
In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will
not work but HP confirmed the new HP generation won't contain the HPQ6001 and
also each DM still need to deal with multi-rfkill events because upstream
changes[2].
---
In the last year, HP mentions HP machines need to use hp-wireless
(HPQ6001) as the rfkill source[1].
However, HP confirms the HPQ6001 has been retired in the platforms
since 2022.
In the platforms after 2022, there are two sources of rkfill events
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
Therefore, the upstream already accept the patch[2] to unmask intel-hid and
mention this big change in the NEWS.
This change makes the pre-2022 HP platforms meet the regression since they
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing
function key.
Thus, there is a patch[3] to make sure the GNOME could deal with this case
smoothly.
However, the systemd change will still cause other DEs meet the regression
(xfce, KDE, lxde, etc..).
Backport systemd change to make HP 2022 platforms work is not the best choice
on stable version (focal in this case).
We still need a solution to make airplane key works on 2022 HP platforms
(intel-hid and atkbd only).
The potential solution from my mind that is to maintain a whitelist to unmask
intel-hid in ubuntu-patch in focal, something like:
```
evdev:name:Intel
[Touch-packages] [Bug 1967576] Re: systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount units
Hello Nick, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- 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/1967576 Title: systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount units Status in systemd package in Ubuntu: New Status in systemd source package in Impish: Fix Committed Bug description: This build log provides an example of the problem: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/ppc64el/s/systemd/20220331_190433_fdbbe@/log.gz. During setup for tests-in-lxd, an attempt is made to purge snapd, but this fails: [ ... ] Purging configuration files for snapd (2.54.3+21.10.1ubuntu0.2) ... Stopping snap.lxd.activate.service Stopping unit snap.lxd.activate.service Waiting until unit snap.lxd.activate.service is stopped [attempt 1] snap.lxd.activate.service is stopped. Removing snap.lxd.activate.service Stopping snap.lxd.daemon.service Stopping unit snap.lxd.daemon.service Waiting until unit snap.lxd.daemon.service is stopped [attempt 1] snap.lxd.daemon.service is stopped. Removing snap.lxd.daemon.service Stopping snap.lxd.user-daemon.service Stopping unit snap.lxd.user-daemon.service Waiting until unit snap.lxd.user-daemon.service is stopped [attempt 1] snap.lxd.user-daemon.service is stopped. Removing snap.lxd.user-daemon.service Stopping snap-core20-1378.mount Stopping unit snap-core20-1378.mount Waiting until unit snap-core20-1378.mount is stopped [attempt 1] snap-core20-1378.mount is stopped. Removing snap core20 and revision 1378 Removing snap-core20-1378.mount Stopping snap-lxd-22672.mount Stopping unit snap-lxd-22672.mount Waiting until unit snap-lxd-22672.mount is stopped [attempt 1] snap-lxd-22672.mount is stopped. Removing snap lxd and revision 22672 rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/meminfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/stat': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/uptime': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/diskstats': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/swaps': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/loadavg': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/slabinfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpu0': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpuidle': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/uevent': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/svm': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/hotplug': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/offline': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/present': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/power': Operation not permitted rm: cannot remove
[Touch-packages] [Bug 1946388] Re: Journalctl -f --file some.journal causes coredump
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal- proposed have been resolved. The regressions appear to have been related to recent autopkgtest infrastructure issues, and retrying the tests resolved the issues. -- 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/1946388 Title: Journalctl -f --file some.journal causes coredump Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] journalctl -f --file FILE results in segfault [test case] $ journalctl -f --file $FILENAME [regression potential] journalctl segfault or failure to properly operate [scope] needed in focal fixed upstream in 2b6df46d21a at v246, so fixed already in h and later [original description] Focal latest systemd 245. Journalctl -f --file path/to/file.journal. Will allways causes journalctl crash... The same doesnt happen on centos8 systemd 239... I couldnt test on any more systems atm. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1946388/+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 1955997] Re: The airplane hotkey has no function on a HP platform
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal-
proposed have been resolved. The regressions appear to have been related
to recent autopkgtest infrastructure issues, and retrying the tests
resolved the issues.
--
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/1955997
Title:
The airplane hotkey has no function on a HP platform
Status in OEM Priority Project:
Fix Committed
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Impish:
Fix Committed
Status in systemd source package in Jammy:
Fix Released
Bug description:
[Impact]
The airplane hokey doesn't work on HP new generation machines.
[Test Plan]
Press airplane hokey.
Before the patch, nothing happens.
After the patch, the rfkill works as expected.
In some old HP platforms (contains Intel-HID and HPQ6001 in same
machine), the user will aware the airplane mode toggled very quickly
e.g. turn-on and turn-off immediately (or works good without problem,
depends on how DM handles multiple rfkill events).
In this case, you could check:
1. sudo evtest
# You probably could see
# ...
# /dev/input/event8: Intel HID events
# ...
# /dev/input/event11: Wireless hotkeys
# or "HP Wireless hotkeys" depends on your kernel version
2. try to listen these events when pressing airplane key, you will
probably see these two events will send the keycode out.
3. check the components own this event
$ sudo udevadm info -a /dev/input/event11
# ...
# ATTRS{phys}=="hpq6001/input0"
$ sudo udevadm info -a /dev/input/event8
# ...
#DRIVERS=="intel-hid"
4. check your hwdb is affect.
$ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
# If you didn't see anything then it means your intel-hid is unmask.
5. You could report a bug to your DM for dealing with two rfkill events (same
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as
workaround (but it will be overwritten in next upgrade) by adding:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
```
to /lib/udev/hwdb.d/60-keyboard.hwdb
then
$ systemd-hwdb update
$ udevadm trigger
[Where problems could occur]
In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will
not work but HP confirmed the new HP generation won't contain the HPQ6001 and
also each DM still need to deal with multi-rfkill events because upstream
changes[2].
---
In the last year, HP mentions HP machines need to use hp-wireless
(HPQ6001) as the rfkill source[1].
However, HP confirms the HPQ6001 has been retired in the platforms
since 2022.
In the platforms after 2022, there are two sources of rkfill events
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
Therefore, the upstream already accept the patch[2] to unmask intel-hid and
mention this big change in the NEWS.
This change makes the pre-2022 HP platforms meet the regression since they
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing
function key.
Thus, there is a patch[3] to make sure the GNOME could deal with this case
smoothly.
However, the systemd change will still cause other DEs meet the regression
(xfce, KDE, lxde, etc..).
Backport systemd change to make HP 2022 platforms work is not the best choice
on stable version (focal in this case).
We still need a solution to make airplane key works on 2022 HP platforms
(intel-hid and atkbd only).
The potential solution from my mind that is to maintain a whitelist to unmask
intel-hid in ubuntu-patch in focal, something like:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
KEYBOARD_KEY_8=wlan # Use hp-wireless instead
```
after "KEYBOARD_KEY_8=unkown".
[1] https://bugs.launchpad.net/bugs/1883846
[2] https://github.com/systemd/systemd/pull/20219
[3]
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+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 1958284] Re: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal-
proposed have been resolved. The regressions appear to have been related
to recent autopkgtest infrastructure issues, and retrying the tests
resolved the issues.
--
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/1958284
Title:
shutdown hangs at "Waiting for process: ..." for 90s, ignoring
DefaultTimeoutStopSec
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Bug description:
[Impact]
The systemd shutdown sequence does not honor systemd-system.conf
settings when waiting for remaining processes. This means that, for
example, if a systemd service specifies KillMode=process and a process
remaining from that service does not properly handle SIGTERM, then the
remaining process will not be killed until after the compiled-in
default value of DefaultTimeoutStopSec (90s), even if the user has
changed the setting of DefaultTimeoutStopSec. In such cases, this
impacts users by significantly increasing the time required for
shutdown/reboot.
[Test Plan]
* Create a new script, /usr/local/bin/loop-ignore-sigterm:
```
#!/bin/bash
loop_forever() {
while true; do sleep 1; done
}
(
trap 'echo Ignoring SIGTERM...' SIGTERM
loop_forever
)
loop_forever
```
This script will spawn a subshell which will loop forever and ignore
SIGTERM. This will force systemd to wait for the subprocess at
reboot/shutdown, and eventually send SIGKILL after TimeoutStopSec
(DefaultTimeoutStopSec in this case).
* Make the script executable:
$ chmod +x /usr/local/bin/loop-ignore-sigterm
* Create a systemd service for this script. Add the following to
/etc/systemd/system/loop-ignore-sigterm.service:
```
[Service]
KillMode=process
ExecStart=/usr/local/bin/loop-ignore-sigterm
```
* Start the service:
$ systemctl start loop-ignore-sigterm.service
* Edit /etc/systemd/system.conf, and uncomment the
'DefaultTimeoutStopSec=90s' line. Modify 90s to something much shorter,
e.g. 20s.
* Re-exec the daemon so this new default takes effect:
$ systemctl daemon-reexec
* Reboot, and monitor the logs. Observe that systemd-shutdown will wait
for the loop-ignore-sigterm process for 90s, instead of the 20s
configured earlier.
[Where problems could occur]
The patch moves the reset_arguments() call to the end of main, which
means reset_arguments() is no longer called before daemon re-execution
(if that branch is taken). If anything in that code path relied on
reset_arguments() being called before re-executing, those assumptions
could be broken. Any such problems would potentially be seen during
daemon re-execution, e.g. when calling systemctl daemon-reexec.
[ Original Description ]
With systemd v245 as shipped with 20.04, the shutdown sequence does
not use the value of `DefaultTimeoutStopSec` to wait for remaining
processes, it instead uses the compiled in default of 90s.
This is most visible with services that use `KillMode=process`
(docker, k8s, k3s, etc...), especially if the remaining processes do
not handle `SIGTERM` or choose to ignore it.
For example:
```
[ OK ] Finished Reboot.
[ OK ] Reached target Reboot.
[ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim,
containerd-shim, containerd-shim, fluent-bit
--- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower
value ---
```
The bug has been fixed upstream here:
https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22
Marc was kind enough to package the patch for 20.04 so I could test it
(https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing-
archive-extra) and with that package, I can confirm that it indeed
fixes the issue.
Here's a few github issues I stumbled upon while trying to debug this,
along with a short writeup of the workaround I ended up using:
- https://github.com/moby/moby/issues/41831
- https://github.com/k3s-io/k3s/issues/2400
- https://github.com/systemd/systemd/issues/16991
- https://raby.sh/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html
Of course, it would be much better if all the processes would properly
handle `SIGTERM`, but having a way to enforce a maximum wait time at
shutdown is a decent workaround.
Given that the patch is relatively simple, would it be possible to add
it the package for 20.04?
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958284/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal- proposed have been resolved. The regressions appear to have been related to recent autopkgtest infrastructure issues, and retrying the tests resolved the issues. -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]:
[Touch-packages] [Bug 1967576] Re: systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount units
** Patch added: "systemd-lp-1967576.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1967576/+attachment/5575869/+files/systemd-lp-1967576.debdiff -- 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/1967576 Title: systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount units Status in systemd package in Ubuntu: New Bug description: This build log provides an example of the problem: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/ppc64el/s/systemd/20220331_190433_fdbbe@/log.gz. During setup for tests-in-lxd, an attempt is made to purge snapd, but this fails: [ ... ] Purging configuration files for snapd (2.54.3+21.10.1ubuntu0.2) ... Stopping snap.lxd.activate.service Stopping unit snap.lxd.activate.service Waiting until unit snap.lxd.activate.service is stopped [attempt 1] snap.lxd.activate.service is stopped. Removing snap.lxd.activate.service Stopping snap.lxd.daemon.service Stopping unit snap.lxd.daemon.service Waiting until unit snap.lxd.daemon.service is stopped [attempt 1] snap.lxd.daemon.service is stopped. Removing snap.lxd.daemon.service Stopping snap.lxd.user-daemon.service Stopping unit snap.lxd.user-daemon.service Waiting until unit snap.lxd.user-daemon.service is stopped [attempt 1] snap.lxd.user-daemon.service is stopped. Removing snap.lxd.user-daemon.service Stopping snap-core20-1378.mount Stopping unit snap-core20-1378.mount Waiting until unit snap-core20-1378.mount is stopped [attempt 1] snap-core20-1378.mount is stopped. Removing snap core20 and revision 1378 Removing snap-core20-1378.mount Stopping snap-lxd-22672.mount Stopping unit snap-lxd-22672.mount Waiting until unit snap-lxd-22672.mount is stopped [attempt 1] snap-lxd-22672.mount is stopped. Removing snap lxd and revision 22672 rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/meminfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/stat': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/uptime': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/diskstats': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/swaps': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/loadavg': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/slabinfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpu0': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpuidle': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/uevent': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/svm': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/hotplug': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/offline': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/present': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/power': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/dscr_default': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/probe': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/smt': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/vulnerabilities': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpufreq': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/isolated': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/kernel_max': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/modalias': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/cgroup': Input/output error dpkg: error processing package snapd (--purge): installed snapd package post-removal script subprocess returned error exit status 1 [ ... ] This appears to result in some snap .mount units being left over in /etc/systemd/system. These leftover mount units will now always fail because snapd
[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
I sponsored this, thanks! ** Tags removed: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: Triaged Status in dbus source package in Jammy: Triaged Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1966800] Re: systemd locks up due to incorrect handling of time zone changes
** Tags added: rls-jj-incoming -- 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/1966800 Title: systemd locks up due to incorrect handling of time zone changes Status in systemd package in Ubuntu: Confirmed Status in systemd package in Fedora: Unknown Bug description: Recently on systems in Ireland, systemd became unresponsive due the change from GMT to Irish Standard Time. This is due to Ireland being unique in having their standard time during the summer, unlike most regions. Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1941335 Fixed by: https://github.com/systemd/systemd-stable/commit/a8b66ca9af811148b67ee952ab32748f88b8bba3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966800/+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 1967576] [NEW] systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount units
Public bug reported: This build log provides an example of the problem: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/ppc64el/s/systemd/20220331_190433_fdbbe@/log.gz. During setup for tests-in-lxd, an attempt is made to purge snapd, but this fails: [ ... ] Purging configuration files for snapd (2.54.3+21.10.1ubuntu0.2) ... Stopping snap.lxd.activate.service Stopping unit snap.lxd.activate.service Waiting until unit snap.lxd.activate.service is stopped [attempt 1] snap.lxd.activate.service is stopped. Removing snap.lxd.activate.service Stopping snap.lxd.daemon.service Stopping unit snap.lxd.daemon.service Waiting until unit snap.lxd.daemon.service is stopped [attempt 1] snap.lxd.daemon.service is stopped. Removing snap.lxd.daemon.service Stopping snap.lxd.user-daemon.service Stopping unit snap.lxd.user-daemon.service Waiting until unit snap.lxd.user-daemon.service is stopped [attempt 1] snap.lxd.user-daemon.service is stopped. Removing snap.lxd.user-daemon.service Stopping snap-core20-1378.mount Stopping unit snap-core20-1378.mount Waiting until unit snap-core20-1378.mount is stopped [attempt 1] snap-core20-1378.mount is stopped. Removing snap core20 and revision 1378 Removing snap-core20-1378.mount Stopping snap-lxd-22672.mount Stopping unit snap-lxd-22672.mount Waiting until unit snap-lxd-22672.mount is stopped [attempt 1] snap-lxd-22672.mount is stopped. Removing snap lxd and revision 22672 rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/meminfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/stat': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/uptime': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/diskstats': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/swaps': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/loadavg': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/slabinfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpu0': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpuidle': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/uevent': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/svm': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/hotplug': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/offline': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/present': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/power': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/dscr_default': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/probe': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/smt': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/vulnerabilities': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpufreq': Operation not permitted rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/isolated': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/kernel_max': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/modalias': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/cgroup': Input/output error dpkg: error processing package snapd (--purge): installed snapd package post-removal script subprocess returned error exit status 1 [ ... ] This appears to result in some snap .mount units being left over in /etc/systemd/system. These leftover mount units will now always fail because snapd etc. is no longer installed. Thus, the 'test_no_failed' test, which checks for any failed units after boot, will fail: [ ... ] == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.s5bwuE/build.2Vb/real-tree/debian/tests/boot-and-services", line 69, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['snap-lxd-22672.mount loaded failed fai[119 chars]180'] !=
[Touch-packages] [Bug 1764044] Re: ssh-add asks about passphrases for keys already unlocked in the keychain
A bit more info because this bug came up again for me. It was mentioned that this was working OK in Trusty, so I assume that openssh 6.6 was being used there, and that when the upgrade to openssh 7.x happened this issue started happening. I agree that the tool itself could be more helpful in its output, but this deprecation has been documented in the release notes: https://wiki.ubuntu.com/XenialXerus/ReleaseNotes/#OpenSSH_7.2p2 I looked at upstream's bugzilla and could not find any bugs requesting a more verbose output from the tool. I still believe this bug should be dealt with by upstream, and we can follow their lead. Keeping as Low priority (and I consider that the priority will only get lower, given that people will forcefully start migrating away from DSA). BTW, I confirmed that this issue still applies to Jammy. ** Changed in: openssh (Ubuntu) Status: New => Triaged ** Changed in: openssh (Ubuntu) Importance: Low => Wishlist -- 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/1764044 Title: ssh-add asks about passphrases for keys already unlocked in the keychain Status in openssh package in Ubuntu: Triaged Bug description: In the below example, on the second invocation of ssh-add I should not be prompted to enter the passphrase again after I successfully entered it on the first instance. This used to work fine in trusty i386 setup. $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Starting ssh-agent... Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Found existing ssh-agent: 25744 Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) gnome-keyring is running: $ ps -ax|grep key 2067 ?SLl0:05 /usr/bin/gnome-keyring-daemon --start --components ssh 2078 ?Ssl0:01 /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service --use-gtk 6987 ?S 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh 17832 pts/2S+ 0:00 grep --color=auto key ssh-agent is running: $ ps aux | grep ssh-agent leggewie 1928 0.0 0.0 15548 340 ?Ss 02:38 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env LD_PRELOAD=libgtk3-nocsd.so.0 /usr/lib/gnome-session/run-systemd-session unity-session.target leggewie 6987 0.0 0.0 11304 1484 ?S02:50 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh leggewie 9952 0.0 0.0 11304 320 ?Ss 04:11 0:00 ssh-agent bash leggewie 17850 0.0 0.0 14492 1160 pts/2S+ 06:06 0:00 grep --color=auto ssh-agent $ env|grep SSH SSH_AUTH_SOCK=/tmp/ssh-W6fuGBztRRds/agent.6992 SSH_AGENT_PID=9952 SSH_AGENT_LAUNCHER=gnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764044/+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 1967521] Re: Test binaries in libsndfile-dev package
it was added on purpose in Debian it seems to be able to use it for autopkgtest https://salsa.debian.org/multimedia-team/libsndfile/-/commit/ce47c46e but it might make sense to have them split in another binary, you should report that to Debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1967521 Title: Test binaries in libsndfile-dev package Status in libsndfile package in Ubuntu: New Bug description: There are programs from the libsndfile test suite in dev package. Should they be there? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1967521/+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 1966613] Re: Navigating with arrow keys broken for RTL text
** Changed in: pango1.0 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1966613 Title: Navigating with arrow keys broken for RTL text Status in Pango: Unknown Status in pango1.0 package in Ubuntu: Fix Committed Bug description: RTL text renders fine, and navigating within a line with the arrow keys works as expected. However, using the left and right arrow keys to move to the next or previous lines is broken. To reproduce: 1. Open gnome-text-editor and paste the following into its window: זוהי השורה הראשונה זוהי השורה השנייה זוהי השורה השלישית make sure it is aligned to the right, as it should. 2. place the caret in the middle of the 2nd line. 3. With the arrows, move the caret to the left of the line (its end). 4. Press the left arrow key one more time. Expected results: 1. The caret moves to the right hand side of the next line. Actual results: 1. The caret moves to the left hand side of the previous line. The same issue exists in reverse: if you move the caret with the arrow keys to the right of the line (its beginning) and press the right arrow key one more time, it will move to the right hand side of the next line instead of the left hand side of the previous line, as it should. This make navigation in RTL files highly uncomfortable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-text-editor 42.0-2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 03:09:24 2022 InstallationDate: Installed on 2022-01-31 (55 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1966613/+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 1967565] Re: upower takes long time to detect laptop AC charger plugged in
Thank you for your bug report, could you report the issue upstream on https://gitlab.freedesktop.org/upower/upower/-/issues ? ** Changed in: upower (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1967565 Title: upower takes long time to detect laptop AC charger plugged in Status in upower package in Ubuntu: New Bug description: upower takes a really long time (around 1-2 minutes) to detect when an AC charger is plugged-in. 'upower -d' shows battery state as discharging after AC charger is plugged-in. 'systemctl restart upower.service' would update the status immediately as charging. Otherwise, it takes 1-2 minutes before upower updates the status. Laptop Model: Acer Aspire E15 E5-573G-56JN Laptop battery and AC charger is not faulty as the charging/discharging status gets correctly detected when using Windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 1 23:07:12 2022 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1967565/+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 1965964] Re: an error has occurred while searching for drivers
*** This bug is a duplicate of bug 1964880 ***
https://bugs.launchpad.net/bugs/1964880
** This bug has been marked a duplicate of bug 1964880
software-properties-gtk crashed with AttributeError in
packages_for_modalias(): 'Cache' object has no attribute 'packages'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1965964
Title:
an error has occurred while searching for drivers
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
when going to additional drivers it says an error has occurred while
searching for drivers. I am using Ubuntu 22.04.
software-properties-gtk:
Installed: 0.99.19
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py:49:
PyGIWarning: Handy was imported without specifying a version first. Use
gi.require_version('Handy', '1') before import to ensure that the right version
gets loaded.
from gi.repository import GObject, Gdk, Gtk, Gio, GLib, Handy
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1380, in detect_drivers
self.devices = detect.system_device_drivers(self.apt_cache)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 752, in
system_device_drivers
for pkg, pkginfo in system_driver_packages(apt_cache, sys_path,
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 448, in
system_driver_packages
for p in packages_for_modalias(apt_cache, alias):
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 200, in
packages_for_modalias
apt_cache_hash = hash(package.get_fullname() for package in
apt_cache.packages)
AttributeError: 'Cache' object has no attribute 'packages'
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: software-properties-gtk 0.99.19
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 22 15:57:06 2022
InstallationDate: Installed on 2022-03-22 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965964/+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 1965857] Re: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
*** This bug is a duplicate of bug 1964880 *** https://bugs.launchpad.net/bugs/1964880 ** This bug has been marked a duplicate of bug 1964880 software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965857 Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' Status in software-properties package in Ubuntu: New Bug description: live patch not active ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 22 10:22:47 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-04-25 (695 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=6 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=6'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: Upgraded to jammy on 2022-02-12 (37 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965857/+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 1965180] Re: apt-add-repository requires --login for private repos, breaking automated workflows
** Changed in: software-properties (Ubuntu Jammy)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: software-properties (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1965180
Title:
apt-add-repository requires --login for private repos, breaking
automated workflows
Status in software-properties package in Ubuntu:
In Progress
Status in software-properties source package in Jammy:
In Progress
Bug description:
On Focal, in an automated environment (such as a launchpad builder), a
used can do the following workflow:
curl
"https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
ppa.launchpad.net/${REPO}/ubuntu focal main"
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64
Packages [3288 B]
Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main
Translation-en [1892 B]
However, on Jammy, I get the following:
curl "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
ppa.launchpad.net/${REPO}/ubuntu jammy main"
Repository: 'deb https://private-ppa.launchpad.net/$REPO/ubuntu jammy main'
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 105,
in lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line
592, in __call__
response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
429, in _request
raise error
lazr.restfulclient.errors.NotFound: HTTP Error 404: Not Found
Response headers:
---
-content-encoding: gzip
content-length: 91
content-type: text/plain;charset=utf-8
date: Wed, 16 Mar 2022 19:54:16 GMT
server: gunicorn/19.8.1
status: 404
vary: Accept-Encoding
x-powered-by: Zope (www.zope.org), Python (www.python.org)
x-request-id: ec4bd7ff-f333-4543-ba91-3b7b063fab0e
x-vcs-revision: 81acd06336f3c4be8f28a2213f7a64912593402d
---
Response body:
---
b"Object: ,
name: '$REPO'"
---
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 352, in main
self.prompt_user_shortcut(shortcut)
File "/usr/bin/apt-add-repository", line 140, in prompt_user_shortcut
if shortcut.description:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 117,
in description
return self.lpppa.description
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 109,
in lpppa
raise ShortcutException(msg)
softwareproperties.shortcuthandler.ShortcutException: ERROR: ppa
'$REPO/proposed' not found (use --login if private)
Impish similarly breaks. Digging through changelogs, I see various
entries in Impish forward, starting with version 0.99.0 where a
refactor was done.
using `--login` is not possible in an automated setup (such as a
builder) as it starts an OAuth dance, which requires human
interaction. this will break existing automation utilizing apt-add-
repository for users when migrating to Jammy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965180/+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 1966127] Re: ubuntu-desktop-minimal pulls gnome-session which is in universe
** Changed in: ubuntu-meta (Ubuntu) Status: New => Invalid ** Changed in: gdm3 (Ubuntu) Status: New => In Progress ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1966127 Title: ubuntu-desktop-minimal pulls gnome-session which is in universe Status in gdm3 package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: Invalid Bug description: ubuntu-desktop-minimal is in main but installing it pulls gnome- session from universe. Here is how to reproduce it: 1) Create a Jammy VM: $ lxc launch images:ubuntu/jammy jammy-vm --vm 2) Enter the Jammy VM: $ lxc shell jammy-vm 3) Install ubuntu-desktop-minimal root@jammy-vm:~# apt-get update ... root@jammy-vm:~# apt-get install -V ubuntu-desktop-minimal ... Get:726 http://archive.ubuntu.com/ubuntu jammy/main amd64 libxfont2 amd64 1:2.0.5-1 [94.7 kB] Get:727 http://archive.ubuntu.com/ubuntu jammy/main amd64 xwayland amd64 2:22.1.0-1 [932 kB] Get:728 http://archive.ubuntu.com/ubuntu jammy/universe amd64 gnome-session all 42.0-1ubuntu1 [15.2 kB] Get:729 http://archive.ubuntu.com/ubuntu jammy/main amd64 yaru-theme-gnome-shell all 22.04.2 [66.4 kB] Get:730 http://archive.ubuntu.com/ubuntu jammy/main amd64 ubuntu-session all 42.0-1ubuntu1 [5,418 B] ... 4) Check the policy of packages: root@jammy-vm:~# apt-cache policy ubuntu-desktop-minimal gnome-session ubuntu-desktop-minimal: Installed: 1.478 Candidate: 1.478 Version table: *** 1.478 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Both should be from main. Additional information: root@jammy-vm:~# lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966127/+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 1966613] Re: Navigating with arrow keys broken for RTL text
** Also affects: gnome-text-editor via https://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/344 Importance: Unknown Status: Unknown ** Package changed: gnome-text-editor (Ubuntu) => pango1.0 (Ubuntu) ** Changed in: pango1.0 (Ubuntu) Status: New => Triaged ** Project changed: gnome-text-editor => pango ** Changed in: pango1.0 (Ubuntu) Status: Triaged => In Progress ** Changed in: pango1.0 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1966613 Title: Navigating with arrow keys broken for RTL text Status in Pango: Unknown Status in pango1.0 package in Ubuntu: In Progress Bug description: RTL text renders fine, and navigating within a line with the arrow keys works as expected. However, using the left and right arrow keys to move to the next or previous lines is broken. To reproduce: 1. Open gnome-text-editor and paste the following into its window: זוהי השורה הראשונה זוהי השורה השנייה זוהי השורה השלישית make sure it is aligned to the right, as it should. 2. place the caret in the middle of the 2nd line. 3. With the arrows, move the caret to the left of the line (its end). 4. Press the left arrow key one more time. Expected results: 1. The caret moves to the right hand side of the next line. Actual results: 1. The caret moves to the left hand side of the previous line. The same issue exists in reverse: if you move the caret with the arrow keys to the right of the line (its beginning) and press the right arrow key one more time, it will move to the right hand side of the next line instead of the left hand side of the previous line, as it should. This make navigation in RTL files highly uncomfortable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-text-editor 42.0-2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 03:09:24 2022 InstallationDate: Installed on 2022-01-31 (55 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1966613/+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 1967155] Re: Update gnome-online-accounts to 3.44
** Changed in: gnome-online-accounts (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1967155 Title: Update gnome-online-accounts to 3.44 Status in gnome-online-accounts package in Ubuntu: Fix Committed Bug description: Minimal tracking bug if needed. https://gitlab.gnome.org/GNOME/gnome-online- accounts/-/blob/master/NEWS https://gitlab.gnome.org/GNOME/gnome-online- accounts/-/compare/3.43.1...master?from_project_id=1666 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1967155/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
Attaching debdiff which I believe should prevent the service from being stopped on upgrade. Test packages are currently building in ppa:waveform/dbus (https://launchpad.net/~waveform/+archive/ubuntu/dbus) but I've already built locally and verified that the offending portion of the preinst maintscript is gone. Ultimately this is down to a mis-understanding of debhelper's start/restart options (which are unfortunately named, and in my opinion insufficiently documented -- something I'll try and post a patch for upstream): In Ubuntu (several releases back) we'd altered the dh_installsystemd options for dbus (in d/rules) to "--no-start" intending the service to be activated solely via dbus.socket. Unfortunately, just specifying "-- no-start" tells debhelper you don't want the service started, but it still implies that you wish the service to be *restarted* (if it's running) during upgrade. You must *additionally* specify "--no-stop-on- upgrade" (formerly known as "--no-restart-on-upgrade", and not to be confused with "--no-restart-after-upgrade") if you do not want it restarted. Debian have also (more recently) adjusted their dh_installsystemd options for dbus (for different reasons), so this will also need patching upstream (I'll try and open a bug for this and associate it with this one as it's all the same options affected at the end of the day). ** Patch added: "1-1962036.debdiff" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+attachment/5575780/+files/1-1962036.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: Triaged Status in dbus source package in Jammy: Triaged Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
Some additional info:
"dh_installsystemd --no-start" on its own is *not* equivalent to "--no-
start --restart-after-upgrade" as one might imagine ("--restart-after-
upgrade" is *usually* the dh_installsystemd default). Instead "--no-
start" adjusts the restart default to "--no-restart-after-upgrade" (I'm
now *fairly* convinced this is actually a bug). Unfortunately "--no-
restart-after-upgrade" cannot work with "--no-start" because, whilst the
preinst script will always stop the service, the postinst script won't
attempt to start it again because "--no-start" is specified.
Even if dh_installsystemd did try to be more intelligent, I'm not
convinced this combination can ever work in all circumstances: the
postinst maintscript cannot know whether the service was running prior
to the preinst script stopping it because the idempotency requirement
for maintscripts implies that postinst is not necessarily running
immediately after preinst.
In other words, "--no-start --no-restart-after-upgrade" (or "--no-start"
on its own which is equivalent) is a broken combination which does not
(and probably cannot, at least with the current design) work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1962036
Title:
dbus was stopped during today's jammy update, breaking desktop
Status in dbus package in Ubuntu:
Triaged
Status in dbus source package in Jammy:
Triaged
Bug description:
Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
Had to hard reset.
Today's jammy upgrade stopped dbus at 19:46:27
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
Bus...
This should not happen. I don't know which package caused this, but
presumably dbus should not be stoppable in the first place.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: dbus 1.12.20-2ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Feb 23 20:03:41 2022
InstallationDate: Installed on 2018-03-14 (1442 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1966613] [NEW] Navigating with arrow keys broken for RTL text
You have been subscribed to a public bug: RTL text renders fine, and navigating within a line with the arrow keys works as expected. However, using the left and right arrow keys to move to the next or previous lines is broken. To reproduce: 1. Open gnome-text-editor and paste the following into its window: זוהי השורה הראשונה זוהי השורה השנייה זוהי השורה השלישית make sure it is aligned to the right, as it should. 2. place the caret in the middle of the 2nd line. 3. With the arrows, move the caret to the left of the line (its end). 4. Press the left arrow key one more time. Expected results: 1. The caret moves to the right hand side of the next line. Actual results: 1. The caret moves to the left hand side of the previous line. The same issue exists in reverse: if you move the caret with the arrow keys to the right of the line (its beginning) and press the right arrow key one more time, it will move to the right hand side of the next line instead of the left hand side of the previous line, as it should. This make navigation in RTL files highly uncomfortable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-text-editor 42.0-2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 03:09:24 2022 InstallationDate: Installed on 2022-01-31 (55 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-text-editor Importance: Unknown Status: Unknown ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: Triaged ** Tags: amd64 apport-bug jammy rtl -- Navigating with arrow keys broken for RTL text https://bugs.launchpad.net/bugs/1966613 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 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 1967565] [NEW] upower takes long time to detect laptop AC charger plugged in
Public bug reported: upower takes a really long time (around 1-2 minutes) to detect when an AC charger is plugged-in. 'upower -d' shows battery state as discharging after AC charger is plugged-in. 'systemctl restart upower.service' would update the status immediately as charging. Otherwise, it takes 1-2 minutes before upower updates the status. Laptop Model: Acer Aspire E15 E5-573G-56JN Laptop battery and AC charger is not faulty as the charging/discharging status gets correctly detected when using Windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 1 23:07:12 2022 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal upower ** Attachment added: "upower_incorrect_discharging.txt" https://bugs.launchpad.net/bugs/1967565/+attachment/5575774/+files/upower_incorrect_discharging.txt ** Description changed: - upower takes a really long time (around 1-2 minutes) to detect when an AC charger is plugged-in. + upower takes a really long time (around 1-2 minutes) to detect when an AC charger is plugged-in. 'upower -d' shows battery state as discharging after AC charger is plugged-in. 'systemctl restart upower.service' would update the status immediately as charging. Otherwise, it takes 1-2 minutes before upower updates the status. - Distro: Ubuntu 20.04.4 Laptop Model: Acer Aspire E15 E5-573G-56JN Laptop battery and AC charger is not faulty as the charging/discharging status gets correctly detected when using Windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 1 23:07:12 2022 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: - LANG=en_IN - LANGUAGE=en_IN:en - PATH=(custom, no user) + LANG=en_IN + LANGUAGE=en_IN:en + PATH=(custom, no user) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1967565 Title: upower takes long time to detect laptop AC charger plugged in Status in upower package in Ubuntu: New Bug description: upower takes a really long time (around 1-2 minutes) to detect when an AC charger is plugged-in. 'upower -d' shows battery state as discharging after AC charger is plugged-in. 'systemctl restart upower.service' would update the status immediately as charging. Otherwise, it takes 1-2 minutes before upower updates the status. Laptop Model: Acer Aspire E15 E5-573G-56JN Laptop battery and AC charger is not faulty as the charging/discharging status gets correctly detected when using Windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 1 23:07:12 2022 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1967565/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
** Changed in: dbus (Ubuntu Jammy) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: Triaged Status in dbus source package in Jammy: Triaged Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1967535] Re: [81BG, Realtek ALC236, Mic, Internal] Recording problem
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1967535 Title: [81BG, Realtek ALC236, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: HI, im kinda new to linux-ubuntu im using it for like 6 month. my issue is that by default my integrated laptop microphone not working. in order to make it work i have to use pulseaudio software and everytime i boot my laptop i have to do pulseaudio --kill and pulseaudio --start in order to make the microphone working. and thats really frustrating, and the really really weird part of the issue is that now while i was trying to report this issue i pressed alt + f2 and then typed ubuntu-bug and then a windows got opened and it asked me to record my voice and then when i recorded my voice, the app played my voice back and i could hear my voice clearly i didnt even started pulseaudio. so i was shocked ! i thought it got fixed for a moment but no it seems like it only worked for the ubuntu-bug report app p.s : sorry for my messy english its not my native language ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sasha 1967 F pulseaudio /dev/snd/pcmC0D0c: sasha 1967 F...m pulseaudio /dev/snd/pcmC0D0p: sasha 1967 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 18:57:31 2022 InstallationDate: Installed on 2021-09-13 (200 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: None of the above Title: [81BG, Realtek ALC236, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN23WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvr6JCN23WW:bd01/23/2018:br1.23:efr1.23:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:skuLENOVO_MT_81BG_BU_idea_FM_ideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 81BG dmi.product.sku: LENOVO_MT_81BG_BU_idea_FM_ideapad 320-15IKB dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1967535/+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 1967535] [NEW] [81BG, Realtek ALC236, Mic, Internal] Recording problem
You have been subscribed to a public bug: HI, im kinda new to linux-ubuntu im using it for like 6 month. my issue is that by default my integrated laptop microphone not working. in order to make it work i have to use pulseaudio software and everytime i boot my laptop i have to do pulseaudio --kill and pulseaudio --start in order to make the microphone working. and thats really frustrating, and the really really weird part of the issue is that now while i was trying to report this issue i pressed alt + f2 and then typed ubuntu-bug and then a windows got opened and it asked me to record my voice and then when i recorded my voice, the app played my voice back and i could hear my voice clearly i didnt even started pulseaudio. so i was shocked ! i thought it got fixed for a moment but no it seems like it only worked for the ubuntu-bug report app p.s : sorry for my messy english its not my native language ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sasha 1967 F pulseaudio /dev/snd/pcmC0D0c: sasha 1967 F...m pulseaudio /dev/snd/pcmC0D0p: sasha 1967 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 18:57:31 2022 InstallationDate: Installed on 2021-09-13 (200 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: None of the above Title: [81BG, Realtek ALC236, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN23WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvr6JCN23WW:bd01/23/2018:br1.23:efr1.23:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:skuLENOVO_MT_81BG_BU_idea_FM_ideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 81BG dmi.product.sku: LENOVO_MT_81BG_BU_idea_FM_ideapad 320-15IKB dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- [81BG, Realtek ALC236, Mic, Internal] Recording problem https://bugs.launchpad.net/bugs/1967535 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 1966179] Re: The airplane hotkey does not work on lots of HP platforms
HP finally confirmed the dmistring for the G9 platforms we currently have. https://drive.google.com/file/d/12HxmGeHcGDRqyay_DLf3WR7M3-T8bv0V/view?usp=sharing -- 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/1966179 Title: The airplane hotkey does not work on lots of HP platforms Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: New Bug description: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. [Where problems could occur] If we don't have whitelist in focal and impish, then the airplane key won't work on new HP platforms. Please refer to Bug #1955997 as well. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966179/+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 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft
** Changed in: iptables (Ubuntu Impish)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1949603
Title:
iptables-save -c shows incorrect counters with iptables-nft
Status in iptables package in Ubuntu:
Fix Released
Status in iptables source package in Impish:
In Progress
Status in iptables source package in Jammy:
Fix Released
Bug description:
[Impact]
Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
is always failing. Initially I thought it was a kernel issue, but
debugging further I found that the reason is that with Impish we're
using iptables-nft by default instead of iptables-legacy.
This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
source directory) is creating a bunch of network namespaces and
checking the iptables counters for the defined policies, in particular
this is the interesting part:
check_ipt_policy_count()
{
ns=$1
ip netns exec $ns iptables-save -c |grep policy | ( read c rest
ip netns exec $ns iptables -Z
if [ x"$c" = x'[0:0]' ]; then
exit 0
elif [ x"$c" = x ]; then
echo "ERROR: No counters"
ret=1
exit 111
else
exit 1
fi
)
}
If I use iptables-nft the counters are never [0:0] as they should be,
so the test is failing. With iptables-legacy they are [0:0] and the
test is passing.
[Test case]
tools/testing/selftests/net/xfrm_policy.sh from the Linux kernel
source code.
[Fix]
Apply iptables upstream commit:
5f1fcace ("iptables-nft: fix -Z option")
In this way also with iptables-nft the counters are reported
correctly.
[Regression potential]
We may require other upstream commits now that the -Z option is
working properly with iptables-nft.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1949603/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1967521] Re: Test binaries in libsndfile-dev package
** Changed in: libsndfile (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1967521 Title: Test binaries in libsndfile-dev package Status in libsndfile package in Ubuntu: New Bug description: There are programs from the libsndfile test suite in dev package. Should they be there? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1967521/+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 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
Appreciate your help, Christian. I'm trying to find a way to reproduce this issue without vSphere, will post it here once get it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1864310] Re: "Ubuntu Archive Automatic Signing Key (2018) " string is not translatable
I think this is more or less a name and names often aren't translated. That string is not from software-properties itself, but perhaps software-properties could use its own string for this label. ** Changed in: software-properties (Ubuntu) Importance: Undecided => Wishlist ** Changed in: software-properties (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1864310 Title: "Ubuntu Archive Automatic Signing Key (2018) " string is not translatable Status in software-properties package in Ubuntu: Triaged Bug description: The "Ubuntu Archive Automatic Signing Key (2018) " string does not seem to be translatable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1864310/+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 1966381] Re: applications crash that never crashed under Ubuntu-20.04
> I think you have a problem there too. oh I'm certainly not claiming a 1g default swap is appropriate, that does seem far, far too small to me and will likely cause widespread issues beyond just this, I was only saying that tweaking the systemd- oomd swap % full setting would IMHO not be likely to fix this very well - and as you point out increasing the swap size to a more reasonable size almost certainly will help (and might be why upstream hadn't noticed this before), regardless of the systemd-oomd swap % used default setting, because it would be far less likely to fill swap up to the oomd swap % full default. > Maybe running with such a starved swapspace triggers systemd-oom to do weird things? >From my quick read of the code, it doesn't seem to be doing anything weird at all, I think it's doing exactly what it's programmed to do. I just don't think the code is correct. -- 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/1966381 Title: applications crash that never crashed under Ubuntu-20.04 Status in systemd package in Ubuntu: New Status in systemd source package in Jammy: New Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+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 1967521] [NEW] Test binaries in libsndfile-dev package
Public bug reported: There are programs from the libsndfile test suite in dev package. Should they be there? ** Affects: libsndfile (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1967521 Title: Test binaries in libsndfile-dev package Status in libsndfile package in Ubuntu: New Bug description: There are programs from the libsndfile test suite in dev package. Should they be there? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1967521/+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 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
This bug was fixed in the package ubuntu-release-upgrader - 1:22.04.8 --- ubuntu-release-upgrader (1:22.04.8) jammy; urgency=medium [ Brian Murray ] * Update the firefox deb2snap entry so that it includes Ubuntu Studio. * Modify the ubuntu-release-upgrader apport package hook to also gather recent messages in journalctl and a list of crashes in /var/crash as one of those may have negatively affected the upgrade process. [ Christian Ehrhardt ] * d/91-release-upgrade: try to use the less expensive /etc/lsb-release to check if we are in a devel release (LP: #1893716) -- Brian Murray Thu, 31 Mar 2022 14:23:13 -0700 ** Changed in: ubuntu-release-upgrader (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 pam in Ubuntu. https://bugs.launchpad.net/bugs/1893716 Title: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions Status in landscape-client package in Ubuntu: In Progress Status in pam package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in update-motd package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: In Progress Bug description: My client has 200+ devices automatically uploading information via sftp and scp to a server every few minutes. After a recent update, I noticed the load on their server spiking through the roof. Upon investigation, I discovered a horde of landscape-sysinfo and /usr/bin/lsb_release processes running that correlated with login session notifications in /var/log/syslog and the load spikes. It appears that even in non-interactive sessions where this information will never be seen, the configuration options below in /etc/pam.d/sshd cause these items to be launched (in fact, probably everything in /etc/update-motd.d). This only started on the system in question after a recent set of system updates were installed. The content of /etc/update-motd.d/* really, really, really shouldn't be executed if the session in question is not interactive, as it provides no value at all. Unfortunately, to disable it for these non- interactive sessions, we also have to disable it for the interactive ones as well where it has some value (though not enough to make spiking the load on this server through the roof an acceptable tradeoff). # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. #sessionoptional pam_motd.so motd=/run/motd.dynamic #sessionoptional pam_motd.so noupdate Also, looking at the script 00-header in /etc/update-motd.d/, /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release does include the necessary information: [ -r /etc/lsb-release ] && . /etc/lsb-release if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then # Fall back to using the very slow lsb_release utility DISTRIB_DESCRIPTION=$(lsb_release -s -d) fi # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1893716/+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 1385415] Re: make libapparmor thread-safe after fork
** Changed in: apparmor Assignee: (unassigned) => Arthit Kosachunhanun (richshops) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1385415 Title: make libapparmor thread-safe after fork Status in AppArmor: New Status in apparmor package in Ubuntu: Triaged Bug description: This tracks the work related to moving AppArmor to systemd in support of bug 1379542. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1385415/+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 1379536] Re: Coarse-grained kernel keyring mediation
** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Arthit Kosachunhanun (richshops) ** Changed in: apparmor (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1379536 Title: Coarse-grained kernel keyring mediation Status in AppArmor: In Progress Status in apparmor package in Ubuntu: Confirmed Bug description: Tracking bug to support coarse-grained kernel keyring mediation. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1379536/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs
** Changed in: cloud-init (Ubuntu) Status: Incomplete => Confirmed ** Changed in: cloud-init Assignee: (unassigned) => Arthit Kosachunhanun (richshops) ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Arthit Kosachunhanun (richshops) ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Arthit Kosachunhanun (richshops) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Arthit Kosachunhanun (richshops) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1701297 Title: NTP reload failure (unable to read library) on overlayfs Status in cloud-init: Won't Fix Status in apparmor package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: After update [1] of cloud-init in Ubuntu (which landed in xenial- updates on 2017-06-27), it is causing NTP reload failures. https://launchpad.net/ubuntu/+source/cloud- init/0.7.9-153-g16a7302f-0ubuntu1~16.04.1 In MAAS scenarios, this is causing the machine to fail to deploy. Related bugs: * bug 1645644: cloud-init ntp not using expected servers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1967499] [NEW] package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: x ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 1 12:45:23 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-21 (465 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1967499 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: x ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 1 12:45:23 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-21 (465 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 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/1967499/+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 1959211] Re: Please merge dbus 1.12.20-3 from Debian unstable
** Description changed: + NOTE: Resetting to new; do NOT merge (the current state of the merge + would also produce LP: #1962036 -- will update this merge once that is + fixed) + Please merge dbus 1.12.20-3 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. ** Changed in: dbus (Ubuntu) Status: Confirmed => New ** Description changed: NOTE: Resetting to new; do NOT merge (the current state of the merge would also produce LP: #1962036 -- will update this merge once that is fixed) + + = Original Description = + Please merge dbus 1.12.20-3 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1959211 Title: Please merge dbus 1.12.20-3 from Debian unstable Status in dbus package in Ubuntu: New Bug description: NOTE: Resetting to new; do NOT merge (the current state of the merge would also produce LP: #1962036 -- will update this merge once that is fixed) = Original Description = Please merge dbus 1.12.20-3 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1967030] Re: [NUC11PAHi7, Realtek ALC256, Mic, Internal] Behringer 1202USB mixer's default usb audio driver clicks
20.04 After upgrading to 5.13.0-39-generic, the same effect is observed. Bus 002 Device 004: ID 08bb:2902 Texas Instruments PCM2902 Audio Codec fix cat ~/.config/pulse/daemon.conf default-sample-rate = 48000 alternate-sample-rate = 48000 avoid-resampling = no -- 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/1967030 Title: [NUC11PAHi7, Realtek ALC256, Mic, Internal] Behringer 1202USB mixer's default usb audio driver clicks Status in alsa-driver package in Ubuntu: New Bug description: maybe pulseaudio, maybe alsa, i don't know. I have a stock kubuntu 21.10 (except for 2 files where i used a "too old" fix that didn't work) Any audio going to my Behringer 1202USB mixer has clicks about 2 per second. That mixer is crackly on startup and shutdown but is new. Could be something to do with powersaving? This is a fresh install of kubuntu on my ibm nuc11i7. I've tried Fedora kde and no repeated clicking. Windows doesn't click. But Fedora kde is junk - can't even connect to github :( Other devices going thru the mixer don't click. Just the usb audio. Other audio devices on kubuntu like hdmi or bluetooth audio work fine. This is maddening :) click click click click... others have the issue too. See... https://www.reddit.com/r/linuxaudio/comments/tko0i6/sudden_issue_with_audio_interface_clicking_at/i2ntx7s/?context=3 please help me :) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sh 988 F pulseaudio /dev/snd/controlC2: sh 988 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Mar 29 18:54:40 2022 InstallationDate: Installed on 2022-03-27 (2 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioLog: Symptom_Type: Volume slider, or mixer problems Title: [NUC11PAHi7, Realtek ALC256, Mic, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2020 dmi.bios.release: 0.35 dmi.bios.vendor: Intel Corp. dmi.bios.version: PATGL357.0035.2020.1113.1353 dmi.board.name: NUC11PABi7 dmi.board.vendor: Intel Corporation dmi.board.version: K90104-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.1 dmi.modalias: dmi:bvnIntelCorp.:bvrPATGL357.0035.2020.1113.1353:bd11/13/2020:br0.35:efr3.1:svnIntel(R)ClientSystems:pnNUC11PAHi7:pvrM15513-302:rvnIntelCorporation:rnNUC11PABi7:rvrK90104-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC11PAHi7000: dmi.product.family: PA dmi.product.name: NUC11PAHi7 dmi.product.sku: RNUC11PAHi7000 dmi.product.version: M15513-302 dmi.sys.vendor: Intel(R) Client Systems modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-03-27T14:12:12.368562 mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-27T16:41:56.751936 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1967030/+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 1230031] Re: dbus-daemon consumes 100% cpu without reason
lowering the importance, there aren't been other reports about that and low activity here over the recent years, unsure if that's still an issue but it's not a critical one for Ubuntu if it impacts a low number of users ** Changed in: dbus (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1230031 Title: dbus-daemon consumes 100% cpu without reason Status in dbus package in Ubuntu: Confirmed Bug description: Just login in to session, and dbus-daemon consumes 100% of cpu. Before, I did a login and logout. This problem appears randomly, not all the time. 9107 sergio20 0 30376 1660 1356 R 100,1 0,0 11:35.08 dbus-daemon 11692 root 20 0 433m 54m 37m S 1,0 1,4 0:05.46 Xorg 12279 sergio20 0 1506m 78m 30m S 0,7 2,1 0:05.40 compiz 12417 sergio20 0 553m 20m 11m S 0,7 0,6 0:00.93 gnome-terminal 13757 sergio20 0 853m 160m 40m S 0,7 4,2 0:06.83 firefox See sensors, dbus-daemon is heating up my laptop: Adapter: Virtual device temp1:+68.0°C (crit = +98.0°C) coretemp-isa- Adapter: ISA adapter Physical id 0: +69.0°C (high = +84.0°C, crit = +100.0°C) Core 0: +49.0°C (high = +84.0°C, crit = +100.0°C) Core 1: +51.0°C (high = +84.0°C, crit = +100.0°C) Core 2: +69.0°C (high = +84.0°C, crit = +100.0°C) Core 3: +55.0°C (high = +84.0°C, crit = +100.0°C) asus-isa- Adapter: ISA adapter temp1: +6280.0°C pkg-temp-0-virtual-0 Adapter: Virtual device temp1:+68.0°C --- Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 Linux sergio-X751JB 3.11.0-8-generic #15-Ubuntu SMP Fri Sep 20 04:11:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux dbus: Installed: 1.6.12-0ubuntu5 Candidate: 1.6.12-0ubuntu5 Version table: *** 1.6.12-0ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: dbus 1.6.12-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Wed Sep 25 04:31:14 2013 InstallationDate: Installed on 2013-09-20 (4 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130920) MarkForUpload: True SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1230031/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
The issue seems to be due to the dbus package
$ cat /var/lib/dpkg/info/dbus.preinst
...
# Automatically added by dh_installsystemd/13.6ubuntu1
if [ -z "${DPKG_ROOT:-}" ] && [ "$1" = upgrade ] && [ -d /run/systemd/system ]
; then
deb-systemd-invoke stop 'dbus.service' 'dbus.socket' >/dev/null || true
fi
# End automatically added section
shouldn't have that been resolved by
https://launchpad.net/ubuntu/+source/dbus/1.12.20-2ubuntu3 ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1962036
Title:
dbus was stopped during today's jammy update, breaking desktop
Status in dbus package in Ubuntu:
Triaged
Status in dbus source package in Jammy:
Triaged
Bug description:
Impact: logind stopped, so desktop stopped, ssh stopped, got no getty.
Had to hard reset.
Today's jammy upgrade stopped dbus at 19:46:27
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message
Bus...
This should not happen. I don't know which package caused this, but
presumably dbus should not be stoppable in the first place.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: dbus 1.12.20-2ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Feb 23 20:03:41 2022
InstallationDate: Installed on 2018-03-14 (1442 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
Testing impish to jammy upgrades the graphical session closes just after having the dbus packages updated, same with xubuntu. The different segfaults in graphical components are probably side effects of dbus or xorg going away under their feet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: Triaged Status in dbus source package in Jammy: Triaged Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
** Tags added: fr-2162 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: Triaged Status in dbus source package in Jammy: Triaged Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
** Changed in: dbus (Ubuntu) Importance: Undecided => Critical ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: Triaged Status in dbus source package in Jammy: Triaged Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
** Changed in: dbus (Ubuntu) Milestone: None => ubuntu-22.04 ** Changed in: dbus (Ubuntu) Status: Confirmed => Triaged ** Also affects: dbus (Ubuntu Jammy) Importance: Critical Status: Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: Triaged Status in dbus source package in Jammy: Triaged Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+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
