[Touch-packages] [Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange
Wt, thanks for confirming Niklas. Athos, would you mind prepping an MP for this, et al? TIA, good sir! \o/ -- 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/1938144 Title: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Status in openssh source package in Focal: Triaged Status in openssh source package in Hirsute: Triaged Bug description: I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and server) with the option "GSSAPIKeyExchange=yes", and this causes the connection to fail. The server has GSSAPI (Kerberos authentication) enabled, but is is only used for non-root users (root uses SSH keys). Client command: ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex root@server -v -p -o GSSAPIKeyExchange=yes Client log: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020 debug1: Reading configuration data /home/user/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: Connecting to compute-test [130.75.80.46] port . debug1: Connection established. debug1: identity file /home/rother/.ssh/id_rsa type 0 debug1: identity file /home/rother/.ssh/id_rsa-cert type -1 debug1: identity file /home/rother/.ssh/id_dsa type -1 debug1: identity file /home/rother/.ssh/id_dsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa type -1 debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519 type -1 debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_xmss type -1 debug1: identity file /home/rother/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400 debug1: Authenticating to server: as 'root' debug1: Offering GSSAPI proposal: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q== debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g== debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: Doing group exchange debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Received GSSAPI_COMPLETE debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Rekey has happened - updating saved versions debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent debug1: Will attempt key: /home/user/.ssh/id_dsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/user/.ssh/id_ed25519 debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk debug1: Will attempt key: /home/user/.ssh/id_xmss debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Delegating credentials debug1: Delegating credentials debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: gssapi-keyex Connection closed by 1.2.3.4 port Server log: debug1: sshd version OpenSSH_8.2, OpenSSL 1.1.1f 31 Mar 2020 debug1: private host key #0: ssh-rsa SHA256:REDACTED debug1: pri
[Touch-packages] [Bug 1943704] Re: lxc fails autopkgtests on (pure) cgroups v2 enabled system
From a side-channel discussion:
all the fully unprivileged tests need to be disabled on
cgroup v2. You can't run fully unprivileged containers on pure cgroup2
layouts. The delegation model doesn't allow it. Not without systemd
making a fully empty delegated cgroup hierarchy available.
I think I'd prefer if those tests could figure out they're
running on a cgroup2 systemd system and then do the systemd-run wrapper
around lxc-start (or whatever it is) as that's realistically what users
of unpriv LXC would do. Something along those lines: `systemd-run
--unit=myshell --user --scope -p "Delegate=yes" lxc-start`
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1943704
Title:
lxc fails autopkgtests on (pure) cgroups v2 enabled system
Status in lxc package in Ubuntu:
New
Bug description:
lxc fails 4 autopkgtests if ran on a cgroups v2 enabled systemd
(248.3-1ubuntu7) using a pure unified hierarchy (in favor of the
hybrid hierarchy used before).
https://autopkgtest.ubuntu.com/packages/lxc
FAIL: lxc-tests: lxc-test-apparmor-mount (0s)
FAIL: lxc-tests: lxc-test-autostart (360s)
FAIL: lxc-tests: lxc-test-no-new-privs (361s)
FAIL: lxc-tests: lxc-test-unpriv (0s)
I needed to skip the "lxc-test-exit-code" test to avoid my local autopkgtest
to hang but that seems to be working on the Ubuntu infrastructure, so its
probably related to my local environment:
diff --git a/debian/tests/exercise b/debian/tests/exercise
index 4a22f33..70231ee 100755
--- a/debian/tests/exercise
+++ b/debian/tests/exercise
@@ -88,6 +88,10 @@ for testbin in lxc-test-*; do
echo "${testbin}" | grep -qv "\.in$" || continue
STRING="lxc-tests: $testbin"
+# Skip some tests because for testing
+[ "$testbin" = "lxc-test-exit-code" ] && \
+ignore "$STRING" && continue
+
# Some tests can't be run standalone
[ "$testbin" = "lxc-test-may-control" ] && continue
Reproducer (while being connected to the Canonical VPN, or setup another
squid proxy):
$ autopkgtest-buildvm-ubuntu-cloud -v -r impish
$ autopkgtest lxc -s -U --apt-pocket=proposed=src:systemd --env
"http_proxy=http://squid.internal:3128"; --env
"https_proxy=http://squid.internal:3128"; --env
"no_proxy=127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,launchpad.net,10.24.0.0/24"
-- qemu autopkgtest-impish-amd64.img
I used "../lxc_4.0.10-0ubuntu4+wip0_amd64.changes" instead of the
"lxc" SRCPKG name, to use a custom package, skipping the additional
"lxc-test-exit-code" test.
Interestingly, the same set of tests fails if I run the test using the
old (non cgroups v2) systemd (248.3-1ubuntu3), i.e. by leaving out the
"--apt-pocket=proposed=src:systemd" parameter. Although, they fail in
a slightly different way (see attached lxc-vs-old-systemd.log).
Running a baseline test using the old systemd passed on the Ubuntu
infrastructure. – I cannot really explain this infra-baseline vs
local-autopkgtest difference... But it doesn't matter too much either,
as we need to fix the situation for the new (cgroupv2) enabled
systemd.
Logs (full logs attached):
FAIL: lxc-tests: lxc-test-apparmor-mount (0s)
---
/usr/sbin/deluser: The user `lxcunpriv' does not exist.
./lxc-test-apparmor-mount: 152: cannot create
/sys/fs/cgroup/-.mount/lxctest/tasks: Permission denied
lxc-destroy: tmp.6hX6BylHCU: tools/lxc_destroy.c: main: 242 Container is not
defined
umount: /sys/kernel/security/apparmor/features/mount: not mounted.
sed: can't read /run/lxc/nics: No such file or directory
---
=> "./lxc-test-apparmor-mount: 152: cannot create
/sys/fs/cgroup/-.mount/lxctest/tasks: Permission denied" seems to be
relevant/related to unified cgroup hierarchy here.
=> fails in a different way with old (non cgroup v2) systemd, locally
FAIL: lxc-tests: lxc-test-autostart (21s)
---
Setting up the GPG keyring
Downloading the image index
ERROR: Failed to download
http://images.linuxcontainers.org//meta/1.0/index-system
lxc-create: lxc-test-auto: lxccontainer.c: create_run_template: 1621 Failed
to create container from template
lxc-create: lxc-test-auto: tools/lxc_create.c: main: 319 Failed to create
container lxc-test-auto
FAIL
---
=> fails in the same way with old (non cgroup v2) systemd, locally.
FAIL: lxc-tests: lxc-test-no-new-privs (22s)
---
+ DONE=0
+ trap cleanup EXIT SIGHUP SIGINT SIGTERM
+ '[' '!' -d /etc/lxc ']'
+ ARCH=i386
+ type dpkg
++ dpkg --print-architecture
+ ARCH=amd64
+ lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
Setting up the GPG keyring
Downloading the image index
ERROR: Failed to download
http://images.linuxcontainers.org//meta/1.0/index-system
lxc-create: c1: lxccontainer.c: create_run_template: 16
[Touch-packages] [Bug 1932579] Re: snap pt_BR locale shows warning every time
@iogui, every system I've tried works well with that workaround (4 installations with Ubuntu 20.04). Please reinstall language-pack-pt-base an try again. Yes, it is a binary file, a gettext .po compiled into a .mo. The sed is a quick workaround that works fine for me even with the binary. If you continue having problems, another way is retranslating with these commands: ``` sudo cp /usr/share/locale-langpack/pt/LC_MESSAGES/snappy.mo /usr/share/locale-langpack/pt/LC_MESSAGES/snappy.mo~ msgunfmt /usr/share/locale-langpack/pt/LC_MESSAGES/snappy.mo > /tmp/snappy.po sed -i 's/o directório de destino/O directório de destino/' /tmp/snappy.po # or edit with PoEditor sudo msgfmt /tmp/snappy.po -o /usr/share/locale-langpack/pt/LC_MESSAGES/snappy.mo ``` I can't find the origin of these translations to contribute to language-pack-pt-base. Do you know about these translations and how to contribute? I only find some git hooks in the sources manipulating translation contents, but don't understood clearly how it is done. Some help is welcome. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1932579 Title: snap pt_BR locale shows warning every time Status in language-pack-pt-base package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: The following warning appears every time I type a snap command, and thus breaks auto-completion. 2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's "" is lowercase in locale "pt_BR": "o directório de destino" The problem seems locale dependent, since "LANG=C snap" doesn't show this warning. I'm currently using Ubuntu 21.04, and this bug happens since I upgraded from 20.10. (I don't know if this is off-topic or where I can help, but "directório" is more pt_PT than pt_BR, which could be "pasta/diretório") echo $LANG output: pt_BR.UTF-8 lsb_release -rb output: Description: Ubuntu 21.04 Release: 21.04 apt-cache policy snapd output: snapd: Instalado: 2.49.2+21.04ubuntu1 Candidato: 2.49.2+21.04ubuntu1 Tabela de versão: *** 2.49.2+21.04ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status snap list output: ...[other packages]... snap-store 3.38.0-64-g23c4c77 547latest/stable canonical✓ - snapd 2.5112159 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1932579/+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 1865088] Re: setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1865088 Title: setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument" Status in console-setup package in Ubuntu: Confirmed Bug description: When I specify a large font file using the FONT variable in .console- setup, setupcon fails to load the font, reporting "putfont: KDFONTOP: Invalid argument". If I specify the same font by setting CODESET, FONTFACE, and FONTSIZE, the setupcon loads it fine. For instance, if I have the following files: bjh21@sole:~$ tail .console-setup.test* ==> .console-setup.test1 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" CODESET="Uni2" FONTFACE="Terminus" FONTSIZE="32x16" ==> .console-setup.test2 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus32x16.psf.gz ==> .console-setup.test3 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus16.psf.gz Running "setupcon test1" correctly loads Uni2-Terminus32x16, but "setupcon test2" does not, reporting "putfont: KDFONTOP: Invalid argument". "setupcon test3" works, demonstrating that not all uses of FONT are broken. I've attached the verbose output from "setupcon -v test2". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.9 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: i386 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Feb 27 20:40:08 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (3550 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1865088/+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 1932579] Re: snap pt_BR locale shows warning every time
The message should no longer be shown anymore in snapd as the PR referenced by Maciej has been merged and should be available on the edge channel of snapd in the few hours. Please give it a try if you like with: ``` snap install snapd --edge || snap refresh snapd --edge # test the snap command to make sure the message no longer appears snap refresh snapd --stable # to go back to tracking stable, as edge sometimes can have unstable changes on it ``` Thanks, Ian ** Changed in: snapd (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: snapd (Ubuntu) Importance: Undecided => Medium ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Milestone: None => 2.53 ** Changed in: snapd Status: New => Fix Committed ** Changed in: snapd Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-pt-base in Ubuntu. https://bugs.launchpad.net/bugs/1932579 Title: snap pt_BR locale shows warning every time Status in snapd: Fix Committed Status in language-pack-pt-base package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Fix Committed Bug description: The following warning appears every time I type a snap command, and thus breaks auto-completion. 2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's "" is lowercase in locale "pt_BR": "o directório de destino" The problem seems locale dependent, since "LANG=C snap" doesn't show this warning. I'm currently using Ubuntu 21.04, and this bug happens since I upgraded from 20.10. (I don't know if this is off-topic or where I can help, but "directório" is more pt_PT than pt_BR, which could be "pasta/diretório") echo $LANG output: pt_BR.UTF-8 lsb_release -rb output: Description: Ubuntu 21.04 Release: 21.04 apt-cache policy snapd output: snapd: Instalado: 2.49.2+21.04ubuntu1 Candidato: 2.49.2+21.04ubuntu1 Tabela de versão: *** 2.49.2+21.04ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status snap list output: ...[other packages]... snap-store 3.38.0-64-g23c4c77 547latest/stable canonical✓ - snapd 2.5112159 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1932579/+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 1943964] [NEW] local var="$@" doesn't behave like every other system
Public bug reported:
With Ubuntu (for many years), the following code in /bin/sh (i.e. dash):
f()
{
local v="$@"
echo "<$v>"
}
f "$@"
behaves differently to /bin/sh on Debian, macOS, FreeBSD, Solaris
(/usr/xpg4/bin/sh).
The behaviour of "$@" is very special. When there are no arguments, it
completely
disappears (i.e. even the surrounding quotes disappear so that there are no
words). When
there are arguments, it replicates those arguments perfectly (i.e. it
effectively produces
multiple quoted arguments if necessary).
The described behaviour applies when "$@" is used for local variable assignment
on Ubuntu,
which sounds consistent with other uses of "$@" and therefore correct, but it
doesn't
match the behaviour on any other system, and is therefore a problem for shell
portability.
On the other systems mentioned above, the behaviour of "$@" when used as the
value of a
variable assignment (local or not) is as though "$*" had been used (i.e. it
produces a
single argument containing all the words).
The difference is clear when the arguments contain multiple words. On Ubuntu,
only
the first word is assigned to v. Any subsequent words are treated as subsequent
variable
names. This goes unnoticed if the subsequent words are valid variable
identifiers.
But if the subsequent words are not valid identifiers, then dash emits a "bad
variable name"
error message.
Note that without the "local" keyword, "$@" does behave like "$*" (like
all the other systems).
You might think that this is correct behaviour, but it is contrary to non-local
variable
assignment, and contrary to all other systems, and is therefore unhelpful.
Please change
it to behave like dash on other systems, e.g. debian.
This behaviour has been witnessed on ubuntu-16.x and ubuntu-20.04.
** Affects: dash (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1943964
Title:
local var="$@" doesn't behave like every other system
Status in dash package in Ubuntu:
New
Bug description:
With Ubuntu (for many years), the following code in /bin/sh (i.e.
dash):
f()
{
local v="$@"
echo "<$v>"
}
f "$@"
behaves differently to /bin/sh on Debian, macOS, FreeBSD, Solaris
(/usr/xpg4/bin/sh).
The behaviour of "$@" is very special. When there are no arguments, it
completely
disappears (i.e. even the surrounding quotes disappear so that there are no
words). When
there are arguments, it replicates those arguments perfectly (i.e. it
effectively produces
multiple quoted arguments if necessary).
The described behaviour applies when "$@" is used for local variable
assignment on Ubuntu,
which sounds consistent with other uses of "$@" and therefore correct, but it
doesn't
match the behaviour on any other system, and is therefore a problem for shell
portability.
On the other systems mentioned above, the behaviour of "$@" when used as the
value of a
variable assignment (local or not) is as though "$*" had been used (i.e. it
produces a
single argument containing all the words).
The difference is clear when the arguments contain multiple words. On Ubuntu,
only
the first word is assigned to v. Any subsequent words are treated as
subsequent variable
names. This goes unnoticed if the subsequent words are valid variable
identifiers.
But if the subsequent words are not valid identifiers, then dash emits a "bad
variable name"
error message.
Note that without the "local" keyword, "$@" does behave like "$*"
(like all the other systems).
You might think that this is correct behaviour, but it is contrary to
non-local variable
assignment, and contrary to all other systems, and is therefore unhelpful.
Please change
it to behave like dash on other systems, e.g. debian.
This behaviour has been witnessed on ubuntu-16.x and ubuntu-20.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1943964/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- 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/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in ubuntu-meta source package in Impish: Confirmed Status in ubuntu-release-upgrader source package in Impish: Confirmed Bug description: Per Canonical's distribution agreement with Mozilla, we're making the snap¹ the default installation of firefox on desktop ISOs starting with Ubuntu 21.10. The snap is built and published for amd64, armhf and arm64. It is jointly maintained by Mozilla and the Ubuntu desktop team, and published by Mozilla. This requires updating the desktop-minimal seed, as well as ubuntu- release-upgrader. ¹ https://snapcraft.io/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- 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/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in ubuntu-meta source package in Impish: Confirmed Status in ubuntu-release-upgrader source package in Impish: Confirmed Bug description: Per Canonical's distribution agreement with Mozilla, we're making the snap¹ the default installation of firefox on desktop ISOs starting with Ubuntu 21.10. The snap is built and published for amd64, armhf and arm64. It is jointly maintained by Mozilla and the Ubuntu desktop team, and published by Mozilla. This requires updating the desktop-minimal seed, as well as ubuntu- release-upgrader. ¹ https://snapcraft.io/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1940504] Re: Support Alder Lake P graphics
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => Fix Committed
--
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/1940504
Title:
Support Alder Lake P graphics
Status in libdrm package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in mesa package in Ubuntu:
Fix Released
Status in libdrm source package in Focal:
Fix Committed
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in mesa source package in Focal:
Fix Committed
Bug description:
[SRU Justification:linux-firmware]
[Impact]
It shows the firmware is missing, and runtime power management has been
disabled:
i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.
[Fix]
Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").
[Test Case]
Verified on Intel ADL-M/ADL-P RVPs.
[Where problems could occur]
It's a new firmware for new GPU, not possible to introduce
regressions.
[Other Info]
Impish has this already. And while ADL-P/M support begins since v5.14,
only focal (for oem-5.14) is being nominated.
=
[SRU Justification:mesa,libdrm]
NOTE: this is for focal only, hirsute/impish do not and will not have
kernel support for this.
[Impact]
ADL-P machines need to use the native driver.
[Fix]
Backport support from upstream.
libdrm: a single patch from 2.4.107
mesa: three commits to add pci-id's and a workaround
kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports
[Test case]
Boot a machine and check that it's using the native driver and that the usual
workloads are fine.
[Where things could go wrong]
For older gpu's there's little to go wrong, since the commits are for ADL-P
only.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1943704] Re: lxc fails autopkgtests on (pure) cgroups v2 enabled system
Some more findings after testing with systemd-run:
FAIL: lxc-tests: lxc-test-autostart (360s)
FAIL: lxc-tests: lxc-test-no-new-privs (361s)
This two tests fail during the (local) autopkgtest run. But after logging into
the local autopkgtest VM via its debug shell (--shell-fail|-s parameter) and
executing them manually `sudo src/tests/lxc-test-autostart` / `sudo
src/tests/lxc-test-no-new-privs` they pass just fine.
(Well I needed to adopt from a "xenial" to a "focal" container for the
"no-new-privs" test as the xenial container will fail with some apt fetch
errors during `apt update`, maybe due to xenial EOL?)
So this is probably some intermittent networking failure or wrong/different
proxy environment settings. – But seems to be rather unrelated to cgroupsv2.
FAIL: lxc-tests: lxc-test-apparmor-mount (0s)
FAIL: lxc-tests: lxc-test-unpriv (0s)
The other two tests seem to need some more porting work to make them
compatible with cgroupsv2, as they are still making use of some
deprecated cgroupsv1 functionality, such as the `cgroup.clone_children`
or `tasks` files (see:
https://github.com/torvalds/linux/blob/master/Documentation/admin-
guide/cgroup-v2.rst#deprecated-v1-core-features).
So in order to unblock the systemd 248.3-1ubuntu7 release (in impish-proposed)
we could move forward with cbrauner's suggestion of skipping these tests.
Patch/Debdiff attached.
In the long run the tests should be fixed and made compatible with cgroupsv2,
though.
** Patch added: "lxc-1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1943704/+attachment/5525945/+files/lxc-1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1943704
Title:
lxc fails autopkgtests on (pure) cgroups v2 enabled system
Status in lxc package in Ubuntu:
New
Bug description:
lxc fails 4 autopkgtests if ran on a cgroups v2 enabled systemd
(248.3-1ubuntu7) using a pure unified hierarchy (in favor of the
hybrid hierarchy used before).
https://autopkgtest.ubuntu.com/packages/lxc
FAIL: lxc-tests: lxc-test-apparmor-mount (0s)
FAIL: lxc-tests: lxc-test-autostart (360s)
FAIL: lxc-tests: lxc-test-no-new-privs (361s)
FAIL: lxc-tests: lxc-test-unpriv (0s)
I needed to skip the "lxc-test-exit-code" test to avoid my local autopkgtest
to hang but that seems to be working on the Ubuntu infrastructure, so its
probably related to my local environment:
diff --git a/debian/tests/exercise b/debian/tests/exercise
index 4a22f33..70231ee 100755
--- a/debian/tests/exercise
+++ b/debian/tests/exercise
@@ -88,6 +88,10 @@ for testbin in lxc-test-*; do
echo "${testbin}" | grep -qv "\.in$" || continue
STRING="lxc-tests: $testbin"
+# Skip some tests because for testing
+[ "$testbin" = "lxc-test-exit-code" ] && \
+ignore "$STRING" && continue
+
# Some tests can't be run standalone
[ "$testbin" = "lxc-test-may-control" ] && continue
Reproducer (while being connected to the Canonical VPN, or setup another
squid proxy):
$ autopkgtest-buildvm-ubuntu-cloud -v -r impish
$ autopkgtest lxc -s -U --apt-pocket=proposed=src:systemd --env
"http_proxy=http://squid.internal:3128"; --env
"https_proxy=http://squid.internal:3128"; --env
"no_proxy=127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,launchpad.net,10.24.0.0/24"
-- qemu autopkgtest-impish-amd64.img
I used "../lxc_4.0.10-0ubuntu4+wip0_amd64.changes" instead of the
"lxc" SRCPKG name, to use a custom package, skipping the additional
"lxc-test-exit-code" test.
Interestingly, the same set of tests fails if I run the test using the
old (non cgroups v2) systemd (248.3-1ubuntu3), i.e. by leaving out the
"--apt-pocket=proposed=src:systemd" parameter. Although, they fail in
a slightly different way (see attached lxc-vs-old-systemd.log).
Running a baseline test using the old systemd passed on the Ubuntu
infrastructure. – I cannot really explain this infra-baseline vs
local-autopkgtest difference... But it doesn't matter too much either,
as we need to fix the situation for the new (cgroupv2) enabled
systemd.
Logs (full logs attached):
FAIL: lxc-tests: lxc-test-apparmor-mount (0s)
---
/usr/sbin/deluser: The user `lxcunpriv' does not exist.
./lxc-test-apparmor-mount: 152: cannot create
/sys/fs/cgroup/-.mount/lxctest/tasks: Permission denied
lxc-destroy: tmp.6hX6BylHCU: tools/lxc_destroy.c: main: 242 Container is not
defined
umount: /sys/kernel/security/apparmor/features/mount: not mounted.
sed: can't read /run/lxc/nics: No such file or directory
---
=> "./lxc-test-apparmor-mount: 152: cannot create
/sys/fs/cgroup/-.mount/lxctest/tasks: Permission denied" seems to be
relevant/related to unified cgroup hierarchy here.
=> fails in a different way with old (non cg
[Touch-packages] [Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0
It would be interesting to know if the issue is due to the differences in the toolchain used to build elfutils 0.183-6 and 0.183-8. The build logs show they were 10.2.1-23ubuntu2 and 11.2.0-1ubuntu2, respectively. If we built 2 copies of 0.183-8 in the same environment, but just varied the different gcc versions, would the problem follow the compiler? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1939413 Title: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Status in elfutils package in Ubuntu: New Status in mozc package in Ubuntu: Invalid Status in protobuf package in Ubuntu: Triaged Bug description: When trying to build package mozc for arm64 the following error popped up: lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux- gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Why does the library contain LTO information at all? Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1939413/+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 1943982] [NEW] Revert resolved-disable-event-sources-before-unreffing-them.patch
Public bug reported: [impact] The initial patch for LP: #1934221 was not sufficient to fix the root cause of the segfault, but rather moved it to a slightly different location in the code (still inside the on_query_timeout handler). [test case] this bug is only to revert the previous patch For verification we should keep systemd-resolved running for a while and observe that it does not crash, using the relevant configuration in addition to being able to resolve DNS queries as expected, e.g.: ``` root@ff-vm:~# cat /etc/systemd/resolved.conf [Resolve] DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net DNSSEC=yes DNSOverTLS=opportunistic MulticastDNS=no LLMNR=no Cache=yes DNSStubListener=yes Domains=~. root@ff-vm:~# dmesg | grep segfault root@ff-vm:~# dmesg | grep "systemd-resolve" root@ff-vm:~# resolvectl query google.com google.com: 2a00:1450:4001:809::200e -- link: enp5s0 172.217.18.110 -- link: enp5s0 -- Information acquired via protocol DNS in 177.4ms. -- Data is authenticated: no ``` [regression potential] Any regression could cause crashes in systemd-resolved, making it unresponsive to DNS network name requests to local applications. [other info] this only reverts the patch that was added for LP: #1934221, as this patch was detected to still produce (slightly different) segfaults in on_query_timeout (https://errors.ubuntu.com/problem/c4e5be3f1c7af9483993c7e6007b9325ab5b78cd), similar to the original segfaults in on_query_timeout (https://errors.ubuntu.com/problem/bb0ce4ff8e6ef86041cfb5647b792823a20b44f7) We want to revert the patch in Focal (systemd v245) for now, while we'll try to fix the root cause in Hirsute (systemd v247), adding more relevant patches that were added to systemd-stable v247 (but not systemd-stable v245): https://github.com/systemd/systemd-stable/commits/v247-stable/src/resolve/resolved-dns-query.c https://github.com/systemd/systemd-stable/commit/64317106aed94a6fb758ab6b08ba490873fc5227 https://github.com/systemd/systemd-stable/commit/91ba2eac4b6b463026b3a93e5a139923e8f2cfe4 https://github.com/systemd/systemd-stable/commit/ab9f7e1a51005f12d3bac83b86716d9d33048eb7 https://github.com/systemd/systemd-stable/commit/78a43c33c8847ebbc2d3cf530ebe304924c58b32 https://github.com/systemd/systemd-stable/commit/c8d7fab2286384b19ff6328cece107c4c02d7bb8 => Root-causing this issue will be done in the (re-opened) LP: #1934221 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1943982 Title: Revert resolved-disable-event-sources-before-unreffing-them.patch Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Bug description: [impact] The initial patch for LP: #1934221 was not sufficient to fix the root cause of the segfault, but rather moved it to a slightly different location in the code (still inside the on_query_timeout handler). [test case] this bug is only to revert the previous patch For verification we should keep systemd-resolved running for a while and observe that it does not crash, using the relevant configuration in addition to being able to resolve DNS queries as expected, e.g.: ``` root@ff-vm:~# cat /etc/systemd/resolved.conf [Resolve] DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net DNSSEC=yes DNSOverTLS=opportunistic MulticastDNS=no LLMNR=no Cache=yes DNSStubListener=yes Domains=~. root@ff-vm:~# dmesg | grep segfault root@ff-vm:~# dmesg | grep "systemd-resolve" root@ff-vm:~# resolvectl query google.com google.com: 2a00:1450:4001:809::200e -- link: enp5s0 172.217.18.110 -- link: enp5s0 -- Information acquired via protocol DNS in 177.4ms. -- Data is authenticated: no ``` [regression potential] Any regression could cause crashes in systemd-resolved, making it unresponsive to DNS network name requests to local applications. [other info] this only reverts the patch that was added for LP: #1934221, as this patch was detected to still produce (slightly different) segfaults in on_query_timeout (https://errors.ubuntu.com/problem/c4e5be3f1c7af9483993c7e6007b9325ab5b78cd), similar to the original segfaults in on_query_timeout (https://errors.ubuntu.com/problem/bb0ce4ff8e6ef86041cfb5647b792823a20b44f7) We want to revert the patch in Focal (systemd v245) for now, while we'll try to fix the root cause in Hirsute (systemd v247), adding more relevant patches that were added to systemd-stable v247 (but not systemd-stable v245): https://github.com/systemd/systemd-stable/commits/v247-sta
[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault
Unfortunately, this patch does not seem to be sufficient. It produces very similar segfaults in on_query_timeout (https://errors.ubuntu.com/problem/c4e5be3f1c7af9483993c7e6007b9325ab5b78cd) that the segfault we could observe before (https://errors.ubuntu.com/problem/bb0ce4ff8e6ef86041cfb5647b792823a20b44f7) We want to revert the patch in Focal (systemd v245) for now (LP: #1943982), while we'll try to fix the root cause in Hirsute (systemd v247), adding more relevant patches that were added to systemd-stable v247 (but not systemd-stable v245): https://github.com/systemd/systemd-stable/commits/v247-stable/src/resolve/resolved-dns-query.c https://github.com/systemd/systemd-stable/commit/64317106aed94a6fb758ab6b08ba490873fc5227 https://github.com/systemd/systemd-stable/commit/91ba2eac4b6b463026b3a93e5a139923e8f2cfe4 https://github.com/systemd/systemd-stable/commit/ab9f7e1a51005f12d3bac83b86716d9d33048eb7 https://github.com/systemd/systemd-stable/commit/78a43c33c8847ebbc2d3cf530ebe304924c58b32 https://github.com/systemd/systemd-stable/commit/c8d7fab2286384b19ff6328cece107c4c02d7bb8 It root-causing is successful, we might back-port those patches to Focal, too. ** Changed in: systemd (Ubuntu Focal) Status: Fix Released => Confirmed ** Changed in: systemd (Ubuntu Hirsute) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Confirmed Status in systemd source package in Hirsute: Confirmed Status in systemd source package in Impish: Fix Released Bug description: [Impact] * systemd-resolved stops replying to clients on the local LAN. * logging segfault crashes in dmesg: [836786.046514] systemd-resolve[872009]: segfault at 399 ip 0399 sp 7ffd7959a6d8 error 14 in systemd-resolved[556398695000+9000] [836786.046524] Code: Bad RIP value. [840887.303994] traps: systemd-resolve[877019] general protection fault ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4] [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4] [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8 * The upload backports the upstream fix (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute. [Test Plan] * Setup /etc/systemd/resolved.conf: [Resolve] DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net DNSSEC=yes DNSOverTLS=opportunistic MulticastDNS=no LLMNR=no Cache=yes DNSStubListener=yes Domains=~. * wait for ~24-48 hours and observe if any crash happens [Where problems could occur] * Any regression would likely cause crashes in systemd-resolved, making it unresponsive to DNS network name requests to local applications. [Other Info] * Reported upstream: https://github.com/systemd/systemd/issues/18427 * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832 === Original description === systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd/libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X399-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC.
[Touch-packages] [Bug 1943982] Re: Revert resolved-disable-event-sources-before-unreffing-them.patch
** Merge proposal linked: https://code.launchpad.net/~slyon/ubuntu/+source/systemd/+git/systemd/+merge/408816 -- 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/1943982 Title: Revert resolved-disable-event-sources-before-unreffing-them.patch Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Bug description: [impact] The initial patch for LP: #1934221 was not sufficient to fix the root cause of the segfault, but rather moved it to a slightly different location in the code (still inside the on_query_timeout handler). [test case] this bug is only to revert the previous patch For verification we should keep systemd-resolved running for a while and observe that it does not crash, using the relevant configuration in addition to being able to resolve DNS queries as expected, e.g.: ``` root@ff-vm:~# cat /etc/systemd/resolved.conf [Resolve] DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net DNSSEC=yes DNSOverTLS=opportunistic MulticastDNS=no LLMNR=no Cache=yes DNSStubListener=yes Domains=~. root@ff-vm:~# dmesg | grep segfault root@ff-vm:~# dmesg | grep "systemd-resolve" root@ff-vm:~# resolvectl query google.com google.com: 2a00:1450:4001:809::200e -- link: enp5s0 172.217.18.110 -- link: enp5s0 -- Information acquired via protocol DNS in 177.4ms. -- Data is authenticated: no ``` [regression potential] Any regression could cause crashes in systemd-resolved, making it unresponsive to DNS network name requests to local applications. [other info] this only reverts the patch that was added for LP: #1934221, as this patch was detected to still produce (slightly different) segfaults in on_query_timeout (https://errors.ubuntu.com/problem/c4e5be3f1c7af9483993c7e6007b9325ab5b78cd), similar to the original segfaults in on_query_timeout (https://errors.ubuntu.com/problem/bb0ce4ff8e6ef86041cfb5647b792823a20b44f7) We want to revert the patch in Focal (systemd v245) for now, while we'll try to fix the root cause in Hirsute (systemd v247), adding more relevant patches that were added to systemd-stable v247 (but not systemd-stable v245): https://github.com/systemd/systemd-stable/commits/v247-stable/src/resolve/resolved-dns-query.c https://github.com/systemd/systemd-stable/commit/64317106aed94a6fb758ab6b08ba490873fc5227 https://github.com/systemd/systemd-stable/commit/91ba2eac4b6b463026b3a93e5a139923e8f2cfe4 https://github.com/systemd/systemd-stable/commit/ab9f7e1a51005f12d3bac83b86716d9d33048eb7 https://github.com/systemd/systemd-stable/commit/78a43c33c8847ebbc2d3cf530ebe304924c58b32 https://github.com/systemd/systemd-stable/commit/c8d7fab2286384b19ff6328cece107c4c02d7bb8 => Root-causing this issue will be done in the (re-opened) LP: #1934221 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943982/+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 1943189] Re: "cannot refresh whilst network offline" bug
@Erich Does this need fixing in older releases as well? The description reads like it just affects impish, but I don't see why that would be the case. If so, can you provide the necessary info for an SRU as in https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1943189 Title: "cannot refresh whilst network offline" bug Status in packagekit package in Ubuntu: Fix Committed Status in packagekit source package in Impish: Fix Committed Bug description: In Ubuntu Impish, an issue has been noted in regards to refreshing packages in Plasma Discover for upgrade or installation. An error appears upon initialization of the Discover interface: "cannot refresh whilst network offline" This will happen regardless of if a system is online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. Unfortunately, the upstream PackageKit maintainers seem to be unwilling to apply this fix themselves, seeing it as not an issue per https://github.com/PackageKit/PackageKit/issues/336 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+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 1943984] [NEW] No archive files for static compilation are included in the -dev package
Public bug reported: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. ** Affects: graphite2 (Ubuntu) Importance: Undecided Status: New ** Patch added: "debdiff.patch" https://bugs.launchpad.net/bugs/1943984/+attachment/5525961/+files/debdiff.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+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 1943189] Re: "cannot refresh whilst network offline" bug
** Changed in: packagekit (Ubuntu Impish) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1943189 Title: "cannot refresh whilst network offline" bug Status in packagekit package in Ubuntu: Fix Committed Status in packagekit source package in Impish: Fix Committed Bug description: In Ubuntu Impish, an issue has been noted in regards to refreshing packages in Plasma Discover for upgrade or installation. An error appears upon initialization of the Discover interface: "cannot refresh whilst network offline" This will happen regardless of if a system is online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. Unfortunately, the upstream PackageKit maintainers seem to be unwilling to apply this fix themselves, seeing it as not an issue per https://github.com/PackageKit/PackageKit/issues/336 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+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 1943189] Re: "cannot refresh whilst network offline" bug
@Julian I can definitely convert this to an SRU. I haven't seen it in Hirsute or Focal, but it's a decent safety net for when things get stuck (gio or otherwise). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1943189 Title: "cannot refresh whilst network offline" bug Status in packagekit package in Ubuntu: Fix Committed Status in packagekit source package in Impish: Fix Committed Bug description: In Ubuntu Impish, an issue has been noted in regards to refreshing packages in Plasma Discover for upgrade or installation. An error appears upon initialization of the Discover interface: "cannot refresh whilst network offline" This will happen regardless of if a system is online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. Unfortunately, the upstream PackageKit maintainers seem to be unwilling to apply this fix themselves, seeing it as not an issue per https://github.com/PackageKit/PackageKit/issues/336 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+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 1943189] Re: "cannot refresh whilst network offline" bug
** Description changed: + Impact] + In Ubuntu Impish, an issue has been noted in regards to refreshing packages in Plasma Discover for upgrade or installation. An error appears upon initialization of the Discover interface: "cannot refresh whilst network offline" This will happen regardless of if a system is online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. - Unfortunately, the upstream PackageKit maintainers seem to be unwilling - to apply this fix themselves, seeing it as not an issue per - https://github.com/PackageKit/PackageKit/issues/336 + [Test Plan] + + * Install Kubuntu or Ubuntu Studio + + * While connected to network, Run Discover + + * Discover will complain about "cannot refresh whilst offline", which + is being communicated from PackageKit. All functionality in Discover is + hindered from this point forward. This is due to a hung packagekitd + process which sees the network offline, even though this is false. + + [Where problems could occur] + + * packagekitd's systemd service will time-out after 90 seconds if + systemd finds no network, which means any update notifications will not + automatically start until packagekitd is manually started. Luckily, + Discover and GNOME Software both attempt to start packagekitd for the + user when run. I'd consider this to be expected behavior for an offline + system. The fix is mostly to prevent the false-negative of the system + being offline when it's really not. + + [Other Info] + + * This fix has been accepted upstream by the PackageKit maintainers as a sane workaround for when gio misbehaves or otherwise. It's a decent safety net. https://github.com/PackageKit/PackageKit/pull/506 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) ** Also affects: packagekit (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: packagekit (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1943189 Title: "cannot refresh whilst network offline" bug Status in packagekit package in Ubuntu: Fix Committed Status in packagekit source package in Focal: New Status in packagekit source package in Hirsute: New Status in packagekit source package in Impish: Fix Committed Bug description: Impact] In Ubuntu Impish, an issue has been noted in regards to refreshing packages in Plasma Discover for upgrade or installation. An error appears upon initialization of the Discover interface: "cannot refresh whilst network offline" This will happen regardless of if a system is online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. [Test Plan] * Install Kubuntu or Ubuntu Studio * While connected to network, Run Discover * Discover will complain about "cannot refresh whilst offline", which is being communi
[Touch-packages] [Bug 1943704] Re: lxc fails autopkgtests on (pure) cgroups v2 enabled system
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1943704
Title:
lxc fails autopkgtests on (pure) cgroups v2 enabled system
Status in lxc package in Ubuntu:
New
Bug description:
lxc fails 4 autopkgtests if ran on a cgroups v2 enabled systemd
(248.3-1ubuntu7) using a pure unified hierarchy (in favor of the
hybrid hierarchy used before).
https://autopkgtest.ubuntu.com/packages/lxc
FAIL: lxc-tests: lxc-test-apparmor-mount (0s)
FAIL: lxc-tests: lxc-test-autostart (360s)
FAIL: lxc-tests: lxc-test-no-new-privs (361s)
FAIL: lxc-tests: lxc-test-unpriv (0s)
I needed to skip the "lxc-test-exit-code" test to avoid my local autopkgtest
to hang but that seems to be working on the Ubuntu infrastructure, so its
probably related to my local environment:
diff --git a/debian/tests/exercise b/debian/tests/exercise
index 4a22f33..70231ee 100755
--- a/debian/tests/exercise
+++ b/debian/tests/exercise
@@ -88,6 +88,10 @@ for testbin in lxc-test-*; do
echo "${testbin}" | grep -qv "\.in$" || continue
STRING="lxc-tests: $testbin"
+# Skip some tests because for testing
+[ "$testbin" = "lxc-test-exit-code" ] && \
+ignore "$STRING" && continue
+
# Some tests can't be run standalone
[ "$testbin" = "lxc-test-may-control" ] && continue
Reproducer (while being connected to the Canonical VPN, or setup another
squid proxy):
$ autopkgtest-buildvm-ubuntu-cloud -v -r impish
$ autopkgtest lxc -s -U --apt-pocket=proposed=src:systemd --env
"http_proxy=http://squid.internal:3128"; --env
"https_proxy=http://squid.internal:3128"; --env
"no_proxy=127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,launchpad.net,10.24.0.0/24"
-- qemu autopkgtest-impish-amd64.img
I used "../lxc_4.0.10-0ubuntu4+wip0_amd64.changes" instead of the
"lxc" SRCPKG name, to use a custom package, skipping the additional
"lxc-test-exit-code" test.
Interestingly, the same set of tests fails if I run the test using the
old (non cgroups v2) systemd (248.3-1ubuntu3), i.e. by leaving out the
"--apt-pocket=proposed=src:systemd" parameter. Although, they fail in
a slightly different way (see attached lxc-vs-old-systemd.log).
Running a baseline test using the old systemd passed on the Ubuntu
infrastructure. – I cannot really explain this infra-baseline vs
local-autopkgtest difference... But it doesn't matter too much either,
as we need to fix the situation for the new (cgroupv2) enabled
systemd.
Logs (full logs attached):
FAIL: lxc-tests: lxc-test-apparmor-mount (0s)
---
/usr/sbin/deluser: The user `lxcunpriv' does not exist.
./lxc-test-apparmor-mount: 152: cannot create
/sys/fs/cgroup/-.mount/lxctest/tasks: Permission denied
lxc-destroy: tmp.6hX6BylHCU: tools/lxc_destroy.c: main: 242 Container is not
defined
umount: /sys/kernel/security/apparmor/features/mount: not mounted.
sed: can't read /run/lxc/nics: No such file or directory
---
=> "./lxc-test-apparmor-mount: 152: cannot create
/sys/fs/cgroup/-.mount/lxctest/tasks: Permission denied" seems to be
relevant/related to unified cgroup hierarchy here.
=> fails in a different way with old (non cgroup v2) systemd, locally
FAIL: lxc-tests: lxc-test-autostart (21s)
---
Setting up the GPG keyring
Downloading the image index
ERROR: Failed to download
http://images.linuxcontainers.org//meta/1.0/index-system
lxc-create: lxc-test-auto: lxccontainer.c: create_run_template: 1621 Failed
to create container from template
lxc-create: lxc-test-auto: tools/lxc_create.c: main: 319 Failed to create
container lxc-test-auto
FAIL
---
=> fails in the same way with old (non cgroup v2) systemd, locally.
FAIL: lxc-tests: lxc-test-no-new-privs (22s)
---
+ DONE=0
+ trap cleanup EXIT SIGHUP SIGINT SIGTERM
+ '[' '!' -d /etc/lxc ']'
+ ARCH=i386
+ type dpkg
++ dpkg --print-architecture
+ ARCH=amd64
+ lxc-create -t download -n c1 -- -d ubuntu -r xenial -a amd64
Setting up the GPG keyring
Downloading the image index
ERROR: Failed to download
http://images.linuxcontainers.org//meta/1.0/index-system
lxc-create: c1: lxccontainer.c: create_run_template: 1621 Failed to create
container from template
lxc-create: c1: tools/lxc_create.c: main: 319 Failed to create container c1
+ cleanup
+ cd /
+ lxc-destroy -n c1 -f
lxc-destroy: c1: tools/lxc_destroy.c: main: 242 Container is not defined
+ true
+ '[' 0 -eq 0 ']'
+ echo FAIL
FAIL
+ exit 1
---
=> fails in the same way with old (non cgroup v2) systemd, locally.
FAIL: lxc-tests: lxc-test-unpriv (0s)
---
./lxc-test-unpriv: line 163: /sys/fs/cgroup/-.mount/lxctest/tasks: Permission
denied
cat: /tmp/tmp.w4zIOZHyAA: No such file or directory
---
=> "./lxc-test-unpr
[Touch-packages] [Bug 1943984] Re: No archive files for static compilation are included in the -dev package
The attachment "debdiff.patch" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+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 1943990] [NEW] After updating systemd packages to 245.4-4ubuntu3.13 and libvirt packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm virtual machines
Public bug reported: # systemctl status systemd-machined.service ● systemd-machined.service - Virtual Machine and Container Registration Service Loaded: loaded (/lib/systemd/system/systemd-machined.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-machined.service(8) https://www.freedesktop.org/wiki/Software/systemd/machined Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Trying to start a virtual machine from openstack, it defines the machine, but is not able to execute it. I used to have libvirt apparmor errors, but disabling libvirt in apparmor didn't solve the problem: [ 27.785713] audit: type=1400 audit(1631888214.441:67): apparmor="DENIED" operation="capable" profile="libvirtd" pid=4817 comm="libvirtd" capability=17 capname="sys_rawio" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-container 245.4-4ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 17 16:23:39 2021 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- 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/1943990 Title: After updating systemd packages to 245.4-4ubuntu3.13 and libvirt packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm virtual machines Status in systemd package in Ubuntu: New Bug description: # systemctl status systemd-machined.service ● systemd-machined.service - Virtual Machine and Container Registration Service Loaded: loaded (/lib/systemd/system/systemd-machined.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-machined.service(8) https://www.freedesktop.org/wiki/Software/systemd/machined Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Trying to start a virtual machine from openstack, it defines the machine, but is not able to execute it. I used to have libvirt apparmor errors, but disabling libvirt in apparmor didn't solve the problem: [ 27.785713] audit: type=1400 audit(1631888214.441:67): apparmor="DENIED" operation="capable" profile="libvirtd" pid=4817 comm="libvirtd" capability=17 capname="sys_rawio" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-container 245.4-4ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 17 16:23:39 2021 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https
[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault
Yes it seems i am still seeing crashes too. They are more rare, but still appearing. -- 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/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Confirmed Status in systemd source package in Hirsute: Confirmed Status in systemd source package in Impish: Fix Released Bug description: [Impact] * systemd-resolved stops replying to clients on the local LAN. * logging segfault crashes in dmesg: [836786.046514] systemd-resolve[872009]: segfault at 399 ip 0399 sp 7ffd7959a6d8 error 14 in systemd-resolved[556398695000+9000] [836786.046524] Code: Bad RIP value. [840887.303994] traps: systemd-resolve[877019] general protection fault ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4] [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4] [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8 * The upload backports the upstream fix (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute. [Test Plan] * Setup /etc/systemd/resolved.conf: [Resolve] DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net DNSSEC=yes DNSOverTLS=opportunistic MulticastDNS=no LLMNR=no Cache=yes DNSStubListener=yes Domains=~. * wait for ~24-48 hours and observe if any crash happens [Where problems could occur] * Any regression would likely cause crashes in systemd-resolved, making it unresponsive to DNS network name requests to local applications. [Other Info] * Reported upstream: https://github.com/systemd/systemd/issues/18427 * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832 === Original description === systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd/libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X399-E GAMING 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.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: 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: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+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 1943990] Re: After updating systemd packages to 245.4-4ubuntu3.13 and libvirt packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm virtual machines
I tried to downgrade the packages, but the problem persisted. For libvirt, the packages for 6.0.0-0ubuntu8.13 were no longer available, so I downgraded for 6.0.0-0ubuntu8.3. -- 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/1943990 Title: After updating systemd packages to 245.4-4ubuntu3.13 and libvirt packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm virtual machines Status in systemd package in Ubuntu: Incomplete Bug description: # systemctl status systemd-machined.service ● systemd-machined.service - Virtual Machine and Container Registration Service Loaded: loaded (/lib/systemd/system/systemd-machined.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-machined.service(8) https://www.freedesktop.org/wiki/Software/systemd/machined Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Trying to start a virtual machine from openstack, it defines the machine, but is not able to execute it. I used to have libvirt apparmor errors, but disabling libvirt in apparmor didn't solve the problem: [ 27.785713] audit: type=1400 audit(1631888214.441:67): apparmor="DENIED" operation="capable" profile="libvirtd" pid=4817 comm="libvirtd" capability=17 capname="sys_rawio" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-container 245.4-4ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 17 16:23:39 2021 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/1943990/+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 1943990] Re: After updating systemd packages to 245.4-4ubuntu3.13 and libvirt packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm virtual machines
you state you have systemd version 245.4-4ubuntu3.13 installed, but your description shows otherwise: Package: systemd-container 245.4-4ubuntu3.11 ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1943990 Title: After updating systemd packages to 245.4-4ubuntu3.13 and libvirt packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm virtual machines Status in systemd package in Ubuntu: Incomplete Bug description: # systemctl status systemd-machined.service ● systemd-machined.service - Virtual Machine and Container Registration Service Loaded: loaded (/lib/systemd/system/systemd-machined.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-machined.service(8) https://www.freedesktop.org/wiki/Software/systemd/machined Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Trying to start a virtual machine from openstack, it defines the machine, but is not able to execute it. I used to have libvirt apparmor errors, but disabling libvirt in apparmor didn't solve the problem: [ 27.785713] audit: type=1400 audit(1631888214.441:67): apparmor="DENIED" operation="capable" profile="libvirtd" pid=4817 comm="libvirtd" capability=17 capname="sys_rawio" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-container 245.4-4ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 17 16:23:39 2021 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/1943990/+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 1931902] Re: [AMD Ellesmere HDMI Audio over DisplayPort] Crackling sound on Pulseaudio for Ubuntu 21.04
OK, so I've found out that the crackling only starts when I change the audio output for the first time after starting Ubuntu up. After that, it only stops if I restart the pulseaudio service, or by restarting the PC. So, the issue clearly has something to do with the change in output audio device. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1931902 Title: [AMD Ellesmere HDMI Audio over DisplayPort] Crackling sound on Pulseaudio for Ubuntu 21.04 Status in pulseaudio package in Ubuntu: New Bug description: While playing back any sounds, a certain crackling sound (static) will play with a fixed delay of the sound being played. The amount and volume of the static will depend on the sound/music that is being played, and this only starts occurring after a somewhat long time (30 minutes or more). What is interesting to see is that while playing back music from Spotify (Snap) the static will only start after a second or so, but when playing YouTube videos on Firefox, it will be immediate and output that static while the video is playing. I've added two sound recordings, one while playing back a song from Spotify and the other while playing a song from YouTube. This issue goes away when restarting the PulseAudio service, but it comes back after a random amount of time. 1) Description: Ubuntu 21.04 Release: 21.04 2) pulseaudio: Installed: 1:14.2-1ubuntu1 Candidate: 1:14.2-1ubuntu1 Version table: 1:14.2-1ubuntu1.1 1 (phased 10%) 500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:14.2-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: matheus 18662 F pulseaudio /dev/snd/controlC2: matheus 18662 F pulseaudio /dev/snd/controlC0: matheus 18662 F pulseaudio /dev/snd/pcmC0D8p: matheus 18662 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 14 16:58:43 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-05-03 (41 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931902/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
** Changed in: ubuntu-meta (Ubuntu Impish) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: ubuntu-release-upgrader (Ubuntu Impish) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in ubuntu-meta source package in Impish: Confirmed Status in ubuntu-release-upgrader source package in Impish: Confirmed Bug description: Per Canonical's distribution agreement with Mozilla, we're making the snap¹ the default installation of firefox on desktop ISOs starting with Ubuntu 21.10. The snap is built and published for amd64, armhf and arm64. It is jointly maintained by Mozilla and the Ubuntu desktop team, and published by Mozilla. This requires updating the desktop-minimal seed, as well as ubuntu- release-upgrader. ¹ https://snapcraft.io/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
** Merge proposal linked: https://code.launchpad.net/~osomon/ubuntu-seeds/+git/ubuntu/+merge/408825 -- 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/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in ubuntu-meta source package in Impish: Confirmed Status in ubuntu-release-upgrader source package in Impish: Confirmed Bug description: Per Canonical's distribution agreement with Mozilla, we're making the snap¹ the default installation of firefox on desktop ISOs starting with Ubuntu 21.10. The snap is built and published for amd64, armhf and arm64. It is jointly maintained by Mozilla and the Ubuntu desktop team, and published by Mozilla. This requires updating the desktop-minimal seed, as well as ubuntu- release-upgrader. ¹ https://snapcraft.io/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
Proposed seed update: https://code.launchpad.net/~osomon/ubuntu- seeds/+git/ubuntu/+merge/408825 -- 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/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in ubuntu-meta source package in Impish: Confirmed Status in ubuntu-release-upgrader source package in Impish: Confirmed Bug description: Per Canonical's distribution agreement with Mozilla, we're making the snap¹ the default installation of firefox on desktop ISOs starting with Ubuntu 21.10. The snap is built and published for amd64, armhf and arm64. It is jointly maintained by Mozilla and the Ubuntu desktop team, and published by Mozilla. This requires updating the desktop-minimal seed, as well as ubuntu- release-upgrader. ¹ https://snapcraft.io/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1943990] Re: After updating systemd packages to 245.4-4ubuntu3.13 and libvirt packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm virtual machines
As I stated in the comment, I downgraded the systemd packages to 3.11 to try to get to a working state, but the error persisted after the downgrade. To get the full picture, these were the updated packages after which kvm stopped to work: root@MGL1-SRV-0006:~# apt list --upgradable Listing... Done libnss-mymachines/focal-updates 245.4-4ubuntu3.13 amd64 [upgradable from: 245.4-4ubuntu3.11] libnss-systemd/focal-updates 245.4-4ubuntu3.13 amd64 [upgradable from: 245.4-4ubuntu3.11] libpam-systemd/focal-updates 245.4-4ubuntu3.13 amd64 [upgradable from: 245.4-4ubuntu3.11] libsystemd0/focal-updates 245.4-4ubuntu3.13 amd64 [upgradable from: 245.4-4ubuntu3.11] libudev1/focal-updates 245.4-4ubuntu3.13 amd64 [upgradable from: 245.4-4ubuntu3.11] libudisks2-0/focal-updates 2.8.4-1ubuntu2 amd64 [upgradable from: 2.8.4-1ubuntu1] libvirt-clients/focal-updates 6.0.0-0ubuntu8.14 amd64 [upgradable from: 6.0.0-0ubuntu8.13] libvirt-daemon-driver-qemu/focal-updates 6.0.0-0ubuntu8.14 amd64 [upgradable from: 6.0.0-0ubuntu8.13] libvirt-daemon-driver-storage-rbd/focal-updates 6.0.0-0ubuntu8.14 amd64 [upgradable from: 6.0.0-0ubuntu8.13] libvirt-daemon-system-systemd/focal-updates 6.0.0-0ubuntu8.14 amd64 [upgradable from: 6.0.0-0ubuntu8.13] libvirt-daemon-system/focal-updates 6.0.0-0ubuntu8.14 amd64 [upgradable from: 6.0.0-0ubuntu8.13] libvirt-daemon/focal-updates 6.0.0-0ubuntu8.14 amd64 [upgradable from: 6.0.0-0ubuntu8.13] libvirt0/focal-updates 6.0.0-0ubuntu8.14 amd64 [upgradable from: 6.0.0-0ubuntu8.13] python3-os-vif/focal-updates 2.0.0-0ubuntu2 all [upgradable from: 2.0.0-0ubuntu1] python3-pyroute2/focal-updates 0.5.9-0ubuntu2 all [upgradable from: 0.5.9-0ubuntu1] systemd-container/focal-updates 245.4-4ubuntu3.13 amd64 [upgradable from: 245.4-4ubuntu3.11] systemd-sysv/focal-updates 245.4-4ubuntu3.13 amd64 [upgradable from: 245.4-4ubuntu3.11] systemd/focal-updates 245.4-4ubuntu3.13 amd64 [upgradable from: 245.4-4ubuntu3.11] udev/focal-updates 245.4-4ubuntu3.13 amd64 [upgradable from: 245.4-4ubuntu3.11] udisks2/focal-updates 2.8.4-1ubuntu2 amd64 [upgradable from: 2.8.4-1ubuntu1] -- 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/1943990 Title: After updating systemd packages to 245.4-4ubuntu3.13 and libvirt packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm virtual machines Status in systemd package in Ubuntu: Incomplete Bug description: # systemctl status systemd-machined.service ● systemd-machined.service - Virtual Machine and Container Registration Service Loaded: loaded (/lib/systemd/system/systemd-machined.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-machined.service(8) https://www.freedesktop.org/wiki/Software/systemd/machined Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Trying to start a virtual machine from openstack, it defines the machine, but is not able to execute it. I used to have libvirt apparmor errors, but disabling libvirt in apparmor didn't solve the problem: [ 27.785713] audit: type=1400 audit(1631888214.441:67): apparmor="DENIED" operation="capable" profile="libvirtd" pid=4817 comm="libvirtd" capability=17 capname="sys_rawio" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-container 245.4-4ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 17 16:23:39 2021 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/1943990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : h
[Touch-packages] [Bug 1943990] Re: After updating systemd packages to 245.4-4ubuntu3.13 and libvirt packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm virtual machines
The full downgrade requests were: # apt install libvirt0=6.0.0-0ubuntu8.3 libvirt-daemon=6.0.0-0ubuntu8.3 libvirt-clients=6.0.0-0ubuntu8.3 libvirt-daemon-driver-qemu=6.0.0-0ubuntu8.3 libvirt-daemon-driver-storage-rbd=6.0.0-0ubuntu8.3 libvirt-daemon-system=6.0.0-0ubuntu8.3 # apt install systemd=245.4-4ubuntu3.11 udev=245.4-4ubuntu3.11 systemd-container=245.4-4ubuntu3.11 systemd-sysv=245.4-4ubuntu3.11 libudev1=245.4-4ubuntu3.11 libsystemd0=245.4-4ubuntu3.11 libnss-mymachines=245.4-4ubuntu3.11 libnss-systemd=245.4-4ubuntu3.11 libpam-systemd=245.4-4ubuntu3.11 I tried just downgrading libvirt, then upgraded it again and downgraded systemd, then both sets. None option worked. -- 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/1943990 Title: After updating systemd packages to 245.4-4ubuntu3.13 and libvirt packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm virtual machines Status in systemd package in Ubuntu: Incomplete Bug description: # systemctl status systemd-machined.service ● systemd-machined.service - Virtual Machine and Container Registration Service Loaded: loaded (/lib/systemd/system/systemd-machined.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-machined.service(8) https://www.freedesktop.org/wiki/Software/systemd/machined Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual Machine and Container Registration Service. Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job systemd-machined.service/start failed with result 'dependency'. Trying to start a virtual machine from openstack, it defines the machine, but is not able to execute it. I used to have libvirt apparmor errors, but disabling libvirt in apparmor didn't solve the problem: [ 27.785713] audit: type=1400 audit(1631888214.441:67): apparmor="DENIED" operation="capable" profile="libvirtd" pid=4817 comm="libvirtd" capability=17 capname="sys_rawio" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-container 245.4-4ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 17 16:23:39 2021 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/1943990/+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 1940656] Re: Potential use after free bugs in 1.1.1
Hello Dimitri, or anyone else affected, Accepted openssl into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1f-1ubuntu2.9 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: openssl (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940656 Title: Potential use after free bugs in 1.1.1 Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Committed Bug description: [Impact] * There have been multiple use-after-free bugs fixed in OpenSSL 1.1.1 stable branches which have not yet been applied in Focal. They are difficult to reproduce, often require an engine to be used, and somehow fail, as these use-after-free bugs are all in error conditions and error paths. Usually fixing local configuration, and making engine available is the right solution. It is however better to return errors than crash. These patches are in 1.1.1h+ and openssl-3. [Test Plan] * The fixes were applied upstream without clear reproducers, or unit tests * Check that all autopkgtests pass and there no regressions * Configure and use openssl with any engine and ensure that it continues to work [Where problems could occur] * There will be behaviour change, such that multithreaded applications may now notice Null pointers from the openssl engine apis, when previously they saw valid pointers which were freed already. Meaning that on connection failures, daemon or application shutdowns, different messages might be generated i.e. invalid engine context, unallocated methods, instead of crashing with double free. [Other Info] * Multiple customers are using openssl 1.1.1 with engines these days, reporting various issues, it is better to have more resilient openssl w.r.t. engine use in case of engine missuse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940656/+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 1944002] [NEW] The selection schreen for the open app overview is unresponsive most of the time
Public bug reported: I have a surface pro 4 and if i play a game from steam or if i just have an application open if i press the windows button / app overview button the overview hangs and is unresponsive to open the apps i want to open. for example i have VS Code open and i press the windows key on accident i cant select VS Code anymore and my progress at that point is gone if i have not saved it yet, and i am forced to turn off the laptop with the normal menu on top to shutdown and start again. i also expreienced this issiue on the surface pro 3. i tried installing a up to date kernel and screen driver for the surface with and without touchschreen support but it keeps happening also when i place my mouse on the top left corner it happens always the windows key only sometimes. Release:Ubuntu 21.04 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.13.7-surface x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 17 15:24:32 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Microsoft Corporation Skylake GT2 [HD Graphics 520] [1414:0015] InstallationDate: Installed on 2021-08-09 (39 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Surface Type Cover Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bluetooth and Wireless LAN Composite Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 3, If 1, Class=Wireless, Driver=btusb, 480M |__ Port 5: Dev 3, If 0, Class=Wireless, Driver=btusb, 480M |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Microsoft Corporation Surface Pro 4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.7-surface root=UUID=a725e530-a1f9-4c3a-8977-3bab6c37a4ce ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05.04.2021 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 109.3748.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr109.3748.768:bd05.04.2021:svnMicrosoftCorporation:pnSurfacePro4:pvr1240D0B08F1C03P38:skuSurface_Pro_4:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.sku: Surface_Pro_4 dmi.product.version: 1240D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1944002 Title: The selection schreen for the open app overview is unresponsive most of the time Status in xorg package in Ubuntu: New Bug description: I have a surface pro 4 and if i play a game from steam or if i just have an application open if i press the windows button / app overview button the overview hangs and is unresponsive to open the apps i want to open. for example i have VS Code open and i press the windows key on accident i cant select VS Code anymore and my progress at that point is gone if i have not saved it yet, and i am forced to turn off the laptop with the normal menu on top to shutdown and start again. i also expreienced this issiue on the surface pro 3. i tried installing a up to date kernel and screen driver for the surface with and without touchschreen support but it keeps happening also
[Touch-packages] [Bug 1943990] Re: After updating systemd packages to 245.4-4ubuntu3.13 and libvirt packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm virtual machines
Some additional info:
The servers where I had problem were running a hyper convergent
solution, with ceph installed via ceph-ansible, including at least a
docker container (running node_exporter) - it is failing as well. These
servers were initially installed with general kernel (5.4.0-81-generic)
and a hwe kernel (5.8.0-34) was installed afterwards.
I succeeded in installing a new server with hwe kernel and updated
libraries, as well as upgrade a system without ceph nor docker; at the
upgrade, some errors concerned me, but didn't cause any bigger trouble:
Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu8.14) ...
Setting up libvirt-daemon (6.0.0-0ubuntu8.14) ...
Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu8.14) ...
Setting up libvirt-daemon-system (6.0.0-0ubuntu8.14) ...
Job failed. See "journalctl -xe" for details.
virtlockd.service is a disabled or a static unit, not starting it.
virtlogd.service is a disabled or a static unit, not starting it.
Setting up libvirt-daemon dnsmasq configuration.
-- A start job for unit libvirtd.service has begun execution.
--
-- The job identifier is 369924.
Sep 17 18:18:25 MGL1-SRV-0018 systemd[1]: Started Virtualization daemon.
-- Subject: A start job for unit libvirtd.service has finished successfully
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit libvirtd.service has finished successfully.
--
-- The job identifier is 369924.
Sep 17 18:18:25 MGL1-SRV-0018 nova-compute[3163250]: 2021-09-17 18:18:25.703
3163250 ERROR nova.scheduler.client.report
[req-b80a57e5-3e9d-4dec-a861-d04363077b0c - - - - -]
[req-38886c27-53ea-41b9-bf14-f68080cac535] Failed to update traits to
[COMPUTE_TRUSTED_CERTS,COMPUTE_IMAGE_TYPE_AMI,HW_CPU_X86_VMX,HW_CPU_X86_MPX,COMPUTE_VOLUME_ATTACH_WITH_TAG,HW_CPU_X86_AVX512DQ,COMPUTE_GRAPHICS_MODEL_QXL,COMPUTE_NET_VIF_MODEL_E1000,COMPUTE_NET_VIF_MODEL_E1000E,HW_CPU_X86_AESNI,COMPUTE_NET_ATTACH_INTERFACE_WITH_TAG,COMPUTE_NET_ATTACH_INTERFACE,COMPUTE_DEVICE_TAGGING,HW_CPU_X86_SSE2,HW_CPU_X86_AVX2,COMPUTE_STORAGE_BUS_VIRTIO,HW_CPU_X86_SSSE3,COMPUTE_ACCELERATORS,COMPUTE_NET_VIF_MODEL_PCNET,HW_CPU_X86_AVX512CD,COMPUTE_GRAPHICS_MODEL_CIRRUS,HW_CPU_X86_FMA3,HW_CPU_X86_SSE41,HW_CPU_X86_AVX512F,COMPUTE_IMAGE_TYPE_QCOW2,COMPUTE_STORAGE_BUS_SATA,COMPUTE_GRAPHICS_MODEL_VGA,HW_CPU_X86_BMI,COMPUTE_STORAGE_BUS_IDE,COMPUTE_IMAGE_TYPE_ARI,COMPUTE_STATUS_DISABLED,COMPUTE_NET_VIF_MODEL_SPAPR_VLAN,HW_CPU_X86_MMX,COMPUTE_NET_VIF_MODEL_RTL8139,COMPUTE_IMAGE_TYPE_RAW,COMPUTE_STORAGE_BUS_FDC,COMPUTE_GRAPHICS_MODEL_NONE,HW_CPU_X86_F16C,HW_CPU_X86_SSE,COMPUTE_RESCUE_BFV,HW_CPU_X86_AVX,COMPUTE_NET_VIF_MODEL_NE2K_PCI,COMPUTE_IMAGE_TYPE_AKI,COMPUTE_STORAGE_BUS_SCSI,HW_CPU_X86_BMI2,COMPUTE_IMAGE_TYPE_ISO,COMPUTE_VOLUME_MULTI_ATTACH,COMPUTE_VOLUME_EXTEND,HW_CPU_HYPERTHREADING,HW_CPU_X86_SSE42,HW_CPU_X86_AVX512VL,HW_CPU_X86_ABM,COMPUTE_NET_VIF_MODEL_VIRTIO,HW_CPU_X86_CLMUL,HW_CPU_X86_AVX512BW,HW_CPU_X86_AVX512VNNI,COMPUTE_GRAPHICS_MODEL_VMVGA,COMPUTE_GRAPHICS_MODEL_VIRTIO,COMPUTE_NODE,COMPUTE_STORAGE_BUS_USB]
for resource provider with UUID f16fc1ab-3b42-431f-9d20-96a27224b90e. Got
409: {"errors": [{"status": 409, "title": "Conflict", "detail": "There was a
conflict when trying to complete your request.\n\n Resource provider's
generation already changed. Please update the generation and try again. ",
"request_id": "req-38886c27-53ea-41b9-bf14-f68080cac535"}]}
Sep 17 18:18:25 MGL1-SRV-0018 nova-compute[3163250]: 2021-09-17 18:18:25.703
3163250 WARNING nova.virt.libvirt.driver
[req-b80a57e5-3e9d-4dec-a861-d04363077b0c - - - - -] An error occurred while
updating compute node resource provider status to "disabled" for provider:
f16fc1ab-3b42-431f-9d20-96a27224b90e:
nova.exception.ResourceProviderUpdateConflict: A conflict was encountered
attempting to update resource provider f16fc1ab-3b42-431f-9d20-96a27224b90e
(generation 27): {"errors": [{"status": 409, "title": "Conflict", "detail":
"There was a conflict when trying to complete your request.\n\n Resource
provider's generation already changed. Please update the generation and try
again. ", "request_id": "req-38886c27-53ea-41b9-bf14-f68080cac535"}]}
2021-09-17 18:18:25.703
3163250 ERROR nova.virt.libvirt.driver Traceback (most recent call last):
2021-09-17 18:18:25.703
3163250 ERROR nova.virt.libvirt.driver File
"/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 4434, in
_update_compute_provider_status
2021-09-17 18:18:25.703
3163250 ERROR nova.virt.libvirt.driver
self.virtapi.update_compute_provider_status(
2021-09-17 18:18:25.703
3163250 ERROR nova.virt.libvirt.driver File
"/usr/lib/python3/dist-packages/nova/compute/manager.py", line 555, in
update_compute_provider_status
[Touch-packages] [Bug 1943988] [NEW] [ROG Flow X13 GV301QH_GV301QH, Realtek ALC294, Speaker, Internal] No sound at all
You have been subscribed to a public bug: I plugged in the headphone jack it's working perfectly only the internal speakers are not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: texma 1093 F pulseaudio texma 28187 F alsamixer /dev/snd/controlC0: texma 1093 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 17 21:28:25 2021 InstallationDate: Installed on 2021-09-16 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: texma 1093 F pulseaudio texma 28187 F alsamixer /dev/snd/controlC0: texma 1093 F pulseaudio /dev/snd/pcmC1D0p: texma 1093 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ROG Flow X13 GV301QH_GV301QH, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GV301QH.407 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GV301QH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301QH.407:bd05/31/2021:br5.19:efr3.9:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301QH_GV301QH:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnGV301QH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Flow X13 dmi.product.name: ROG Flow X13 GV301QH_GV301QH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-09-16T23:00:51.470792 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [ROG Flow X13 GV301QH_GV301QH, Realtek ALC294, Speaker, Internal] No sound at all https://bugs.launchpad.net/bugs/1943988 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 1943988] Re: [ROG Flow X13 GV301QH_GV301QH, Realtek ALC294, Speaker, Internal] No sound at all
** 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/1943988 Title: [ROG Flow X13 GV301QH_GV301QH, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: I plugged in the headphone jack it's working perfectly only the internal speakers are not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: texma 1093 F pulseaudio texma 28187 F alsamixer /dev/snd/controlC0: texma 1093 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 17 21:28:25 2021 InstallationDate: Installed on 2021-09-16 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: texma 1093 F pulseaudio texma 28187 F alsamixer /dev/snd/controlC0: texma 1093 F pulseaudio /dev/snd/pcmC1D0p: texma 1093 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ROG Flow X13 GV301QH_GV301QH, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GV301QH.407 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GV301QH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGV301QH.407:bd05/31/2021:br5.19:efr3.9:svnASUSTeKCOMPUTERINC.:pnROGFlowX13GV301QH_GV301QH:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnGV301QH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Flow X13 dmi.product.name: ROG Flow X13 GV301QH_GV301QH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-09-16T23:00:51.470792 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1943988/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
** Merge proposal linked: https://code.launchpad.net/~osomon/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/408838 -- 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/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in ubuntu-meta source package in Impish: Confirmed Status in ubuntu-release-upgrader source package in Impish: Confirmed Bug description: Per Canonical's distribution agreement with Mozilla, we're making the snap¹ the default installation of firefox on desktop ISOs starting with Ubuntu 21.10. The snap is built and published for amd64, armhf and arm64. It is jointly maintained by Mozilla and the Ubuntu desktop team, and published by Mozilla. This requires updating the desktop-minimal seed, as well as ubuntu- release-upgrader. ¹ https://snapcraft.io/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
Proposed update for ubuntu-release-upgrader: https://code.launchpad.net/~osomon/ubuntu-release-upgrader/+git/ubuntu- release-upgrader/+merge/408838 Please note that these were not actually tested. This requires thorough testing before actually being considered for upload. -- 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/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in ubuntu-meta source package in Impish: Confirmed Status in ubuntu-release-upgrader source package in Impish: Confirmed Bug description: Per Canonical's distribution agreement with Mozilla, we're making the snap¹ the default installation of firefox on desktop ISOs starting with Ubuntu 21.10. The snap is built and published for amd64, armhf and arm64. It is jointly maintained by Mozilla and the Ubuntu desktop team, and published by Mozilla. This requires updating the desktop-minimal seed, as well as ubuntu- release-upgrader. ¹ https://snapcraft.io/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1944006] [NEW] focal cloud image on kvm does not have ip_tables kernel module
Public bug reported: $ sudo iptables -L modprobe: FATAL: Module ip_tables not found in directory /lib/modules/5.4.0-84-generic iptables v1.6.1: can't initialize iptables table `filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. No ip_tables.ko ``` $ ls -l /lib/modules/`uname -r`/kernel/net/ipv4 total 24 -rw-r--r-- 1 root root 11257 Aug 26 18:48 gre.ko -rw-r--r-- 1 root root 12161 Aug 26 18:48 udp_tunnel.ko ``` Cloud images downloaded from - http://cloud-images.ubuntu.com/releases/focal/release/ ``` $ ls -l total 569308 -rw-rw-r-- 1 rtip rtip 543817728 Sep 7 17:35 ubuntu-20.04-server-cloudimg-amd64-disk-kvm.img -rw-rw-r-- 1 libvirt-qemu kvm 27373249 Sep 7 17:37 ubuntu-20.04-server-cloudimg-amd64-initrd-generic -rw-rw-r-- 1 libvirt-qemu kvm 11776256 Sep 7 17:37 ubuntu-20.04-server-cloudimg-amd64-vmlinuz-generic ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iptables 1.6.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 Date: Fri Sep 17 20:57:42 2021 ProcEnviron: LANG=C.UTF-8 SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iptables (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- 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/1944006 Title: focal cloud image on kvm does not have ip_tables kernel module Status in iptables package in Ubuntu: New Bug description: $ sudo iptables -L modprobe: FATAL: Module ip_tables not found in directory /lib/modules/5.4.0-84-generic iptables v1.6.1: can't initialize iptables table `filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. No ip_tables.ko ``` $ ls -l /lib/modules/`uname -r`/kernel/net/ipv4 total 24 -rw-r--r-- 1 root root 11257 Aug 26 18:48 gre.ko -rw-r--r-- 1 root root 12161 Aug 26 18:48 udp_tunnel.ko ``` Cloud images downloaded from - http://cloud-images.ubuntu.com/releases/focal/release/ ``` $ ls -l total 569308 -rw-rw-r-- 1 rtip rtip 543817728 Sep 7 17:35 ubuntu-20.04-server-cloudimg-amd64-disk-kvm.img -rw-rw-r-- 1 libvirt-qemu kvm 27373249 Sep 7 17:37 ubuntu-20.04-server-cloudimg-amd64-initrd-generic -rw-rw-r-- 1 libvirt-qemu kvm 11776256 Sep 7 17:37 ubuntu-20.04-server-cloudimg-amd64-vmlinuz-generic ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iptables 1.6.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 Date: Fri Sep 17 20:57:42 2021 ProcEnviron: LANG=C.UTF-8 SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1944006/+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 1943189] Re: "cannot refresh whilst network offline" bug
This bug was fixed in the package packagekit - 1.2.2-2ubuntu2 --- packagekit (1.2.2-2ubuntu2) impish; urgency=medium * Add wait-until-online-to-activate-systemd-service.patch: Wait until after network-online.target to start packagekitd so it knows if it is online, thanks to Erich Eickmeyer for the patch (LP: #1943189) -- Julian Andres Klode Fri, 17 Sep 2021 17:40:40 +0200 ** Changed in: packagekit (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1943189 Title: "cannot refresh whilst network offline" bug Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Focal: New Status in packagekit source package in Hirsute: New Status in packagekit source package in Impish: Fix Released Bug description: Impact] In Ubuntu Impish, an issue has been noted in regards to refreshing packages in Plasma Discover for upgrade or installation. An error appears upon initialization of the Discover interface: "cannot refresh whilst network offline" This will happen regardless of if a system is online or not. I identified a race condition in which this is occurring on systems where packagekitd is initialized before the network service is online. This was a relatively easy fix and required adding one line to the packagekit.service file: Wants=network-online.target This ensures that packagekitd is not initialized prior to being online. If the 90 second deadline isn't met, then packagekitd will simply not start as a background process until the user connects to the network and initializes it via a graphical utility, such as with GNOME Software or Plasma Discover, both of which initialize packagekitd on a user level. The attached patch will easily apply the fix via normal Debian packaging methods. [Test Plan] * Install Kubuntu or Ubuntu Studio * While connected to network, Run Discover * Discover will complain about "cannot refresh whilst offline", which is being communicated from PackageKit. All functionality in Discover is hindered from this point forward. This is due to a hung packagekitd process which sees the network offline, even though this is false. [Where problems could occur] * packagekitd's systemd service will time-out after 90 seconds if systemd finds no network, which means any update notifications will not automatically start until packagekitd is manually started. Luckily, Discover and GNOME Software both attempt to start packagekitd for the user when run. I'd consider this to be expected behavior for an offline system. The fix is mostly to prevent the false-negative of the system being offline when it's really not. [Other Info] * This fix has been accepted upstream by the PackageKit maintainers as a sane workaround for when gio misbehaves or otherwise. It's a decent safety net. https://github.com/PackageKit/PackageKit/pull/506 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu1 [modified: lib/systemd/system/packagekit.service] ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 9 16:34:12 2021 InstallationDate: Installed on 2021-03-20 (172 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+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 1944006] Re: focal cloud image on kvm does not have ip_tables kernel module
Hello, can you please look for ip_tables.ko in /lib/modules/*/kernel/net/ipv4/netfilter/ip_tables.ko ? Which linux- modules-* package and which linux-image-* packages do you have installed? Thanks ** Package changed: iptables (Ubuntu) => linux (Ubuntu) -- 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/1944006 Title: focal cloud image on kvm does not have ip_tables kernel module Status in linux package in Ubuntu: New Bug description: $ sudo iptables -L modprobe: FATAL: Module ip_tables not found in directory /lib/modules/5.4.0-84-generic iptables v1.6.1: can't initialize iptables table `filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. No ip_tables.ko ``` $ ls -l /lib/modules/`uname -r`/kernel/net/ipv4 total 24 -rw-r--r-- 1 root root 11257 Aug 26 18:48 gre.ko -rw-r--r-- 1 root root 12161 Aug 26 18:48 udp_tunnel.ko ``` Cloud images downloaded from - http://cloud-images.ubuntu.com/releases/focal/release/ ``` $ ls -l total 569308 -rw-rw-r-- 1 rtip rtip 543817728 Sep 7 17:35 ubuntu-20.04-server-cloudimg-amd64-disk-kvm.img -rw-rw-r-- 1 libvirt-qemu kvm 27373249 Sep 7 17:37 ubuntu-20.04-server-cloudimg-amd64-initrd-generic -rw-rw-r-- 1 libvirt-qemu kvm 11776256 Sep 7 17:37 ubuntu-20.04-server-cloudimg-amd64-vmlinuz-generic ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iptables 1.6.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 Date: Fri Sep 17 20:57:42 2021 ProcEnviron: LANG=C.UTF-8 SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944006/+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 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
In MacBook Pro 2015, the inbuilt SD Card Reader needs to be filtered out. Comment#16 helped me fix the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) Status in lvm2 package in Ubuntu: Confirmed Bug description: sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.0-17-generic Found initrd image: /boot/initrd.img-5.0.0-17-generic Found linux image: /boot/vmlinuz-5.0.0-16-generic Found initrd image: /boot/initrd.img-5.0.0-16-generic /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdd: open failed: No medium found /dev/sde: open failed: No medium found /dev/sdf: open failed: No medium found Adding boot menu entry for EFI firmware configuration done -- lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda8:00 3.7T 0 disk ├─sda1 8:10 512M 0 part /boot/efi ├─sda2 8:20 732M 0 part /boot └─sda3 8:30 3.7T 0 part └─sda3_crypt 253:00 3.7T 0 crypt ├─kubuntu--vg-swap_1 253:10 976M 0 lvm [SWAP] └─kubuntu--vg-root 253:20 3.7T 0 lvm / sdb8:16 0 3.7T 0 disk └─sdb1 8:17 0 3.7T 0 part sdg8:96 0 7.3T 0 disk └─sdg1 8:97 0 7.3T 0 part /media/scott/8TB Ext Drive sr0 11:01 15.7G 0 rom -- cat /etc/default/grub GRUB_DEFAULT=0 GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on" GRUB_CMDLINE_LINUX="" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2-common 2.02+dfsg1-12ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jun 25 15:05:29 2019 InstallationDate: Installed on 2019-06-14 (10 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190614) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1834250/+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 1940656] Autopkgtest regression report (openssl/1.1.1f-1ubuntu2.9)
All autopkgtests for the newly accepted openssl (1.1.1f-1ubuntu2.9) for focal have finished running. The following regressions have been reported in tests triggered by the package: puma/3.12.4-1ubuntu2 (s390x) kopanocore/8.7.0-7ubuntu1 (amd64, arm64) casync/2+20190213-1 (s390x) uftp/4.10.1-1 (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/focal/update_excuses.html#openssl [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 openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940656 Title: Potential use after free bugs in 1.1.1 Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Committed Bug description: [Impact] * There have been multiple use-after-free bugs fixed in OpenSSL 1.1.1 stable branches which have not yet been applied in Focal. They are difficult to reproduce, often require an engine to be used, and somehow fail, as these use-after-free bugs are all in error conditions and error paths. Usually fixing local configuration, and making engine available is the right solution. It is however better to return errors than crash. These patches are in 1.1.1h+ and openssl-3. [Test Plan] * The fixes were applied upstream without clear reproducers, or unit tests * Check that all autopkgtests pass and there no regressions * Configure and use openssl with any engine and ensure that it continues to work [Where problems could occur] * There will be behaviour change, such that multithreaded applications may now notice Null pointers from the openssl engine apis, when previously they saw valid pointers which were freed already. Meaning that on connection failures, daemon or application shutdowns, different messages might be generated i.e. invalid engine context, unallocated methods, instead of crashing with double free. [Other Info] * Multiple customers are using openssl 1.1.1 with engines these days, reporting various issues, it is better to have more resilient openssl w.r.t. engine use in case of engine missuse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940656/+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 1930301] Re: package libpam0g:amd64 1.3.1-5ubuntu4.2 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: debconf (Ubuntu) Status: New => Confirmed -- 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/1930301 Title: package libpam0g:amd64 1.3.1-5ubuntu4.2 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 Status in debconf package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Bug description: My laptop system continuously pops the message system crashed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.3.1-5ubuntu4.2 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 31 22:05:36 2021 DuplicateSignature: package:libpam0g:amd64:1.3.1-5ubuntu4.2 Setting up libpam0g:amd64 (1.3.1-5ubuntu4.2) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-08-08 (296 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: pam Title: package libpam0g:amd64 1.3.1-5ubuntu4.2 failed to install/upgrade: installed libpam0g:amd64 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/debconf/+bug/1930301/+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 1930301] Re: package libpam0g:amd64 1.3.1-5ubuntu4.2 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pam (Ubuntu) Status: New => Confirmed -- 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/1930301 Title: package libpam0g:amd64 1.3.1-5ubuntu4.2 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 Status in debconf package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Bug description: My laptop system continuously pops the message system crashed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.3.1-5ubuntu4.2 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 31 22:05:36 2021 DuplicateSignature: package:libpam0g:amd64:1.3.1-5ubuntu4.2 Setting up libpam0g:amd64 (1.3.1-5ubuntu4.2) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-08-08 (296 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: pam Title: package libpam0g:amd64 1.3.1-5ubuntu4.2 failed to install/upgrade: installed libpam0g:amd64 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/debconf/+bug/1930301/+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 1710060]
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1710060 Title: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Fedora: Won't Fix Bug description: Whenever I choose the Jabra Evolve 65 UC Headset as the playback device, there are sound chipmunks. The same was the case with Jabra Motion Headset as well. But those two headsets worked perfectly in Windows, Mac OS and Android. There was a workaround mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1282285 by editing the contents of /etc/pulseaudio/daemon.conf : Changing ;default-sample-rate=44100 to default-sample-rate=48000 and then running pulseaudio -k made the sound on Jabra good (no more chipmunks). Also, when I opened the Sound Settings with the changes in daemon.conf in place, there seems to be some distortions in headset sound, which goes away few seconds after I close the sound settings window. This problem should be fixed, as many new Linux users will find it difficult to edit files requiring root access, and those who do not use command line won't be okay with it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: itachi10880 F...m pulseaudio /dev/snd/controlC2: itachi10880 F pulseaudio /dev/snd/controlC1: itachi10880 F pulseaudio /dev/snd/controlC0: itachi10880 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 10 21:11:18 2017 InstallationDate: Installed on 2016-08-27 (349 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-08-10T21:07:55.637386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/+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 1710060]
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1710060 Title: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Fedora: Won't Fix Bug description: Whenever I choose the Jabra Evolve 65 UC Headset as the playback device, there are sound chipmunks. The same was the case with Jabra Motion Headset as well. But those two headsets worked perfectly in Windows, Mac OS and Android. There was a workaround mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1282285 by editing the contents of /etc/pulseaudio/daemon.conf : Changing ;default-sample-rate=44100 to default-sample-rate=48000 and then running pulseaudio -k made the sound on Jabra good (no more chipmunks). Also, when I opened the Sound Settings with the changes in daemon.conf in place, there seems to be some distortions in headset sound, which goes away few seconds after I close the sound settings window. This problem should be fixed, as many new Linux users will find it difficult to edit files requiring root access, and those who do not use command line won't be okay with it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: itachi10880 F...m pulseaudio /dev/snd/controlC2: itachi10880 F pulseaudio /dev/snd/controlC1: itachi10880 F pulseaudio /dev/snd/controlC0: itachi10880 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 10 21:11:18 2017 InstallationDate: Installed on 2016-08-27 (349 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-08-10T21:07:55.637386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/+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 1710060] Re: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset
** Changed in: pulseaudio (Fedora) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1710060 Title: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Fedora: Won't Fix Bug description: Whenever I choose the Jabra Evolve 65 UC Headset as the playback device, there are sound chipmunks. The same was the case with Jabra Motion Headset as well. But those two headsets worked perfectly in Windows, Mac OS and Android. There was a workaround mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1282285 by editing the contents of /etc/pulseaudio/daemon.conf : Changing ;default-sample-rate=44100 to default-sample-rate=48000 and then running pulseaudio -k made the sound on Jabra good (no more chipmunks). Also, when I opened the Sound Settings with the changes in daemon.conf in place, there seems to be some distortions in headset sound, which goes away few seconds after I close the sound settings window. This problem should be fixed, as many new Linux users will find it difficult to edit files requiring root access, and those who do not use command line won't be okay with it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: itachi10880 F...m pulseaudio /dev/snd/controlC2: itachi10880 F pulseaudio /dev/snd/controlC1: itachi10880 F pulseaudio /dev/snd/controlC0: itachi10880 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 10 21:11:18 2017 InstallationDate: Installed on 2016-08-27 (349 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-08-10T21:07:55.637386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/+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 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it
A workaround of my own was to correct the nvidia driver's behaviour. Running Ubuntu 21.04 and nvidia-drivers-460, I upgraded to nvidia- drivers-470 (which I had installed once before), resulting in no masked services, and files paths to real .service files. Before: ❯ systemctl status nvidia-suspend nvidia-hibernate nvidia-resume ● nvidia-suspend.service Loaded: masked (Reason: Unit nvidia-suspend.service is masked.) Active: inactive (dead) ● nvidia-hibernate.service Loaded: masked (Reason: Unit nvidia-hibernate.service is masked.) Active: inactive (dead) ● nvidia-resume.service Loaded: masked (Reason: Unit nvidia-resume.service is masked.) Active: inactive (dead) After: systemctl status nvidia-suspend nvidia-hibernate nvidia-resume ● nvidia-suspend.service - NVIDIA system suspend actions Loaded: loaded (/lib/systemd/system/nvidia-suspend.service; enabled; vendor preset: enabled) Active: inactive (dead) ● nvidia-hibernate.service - NVIDIA system hibernate actions Loaded: loaded (/lib/systemd/system/nvidia-hibernate.service; enabled; vendor preset: enabled) Active: inactive (dead) ● nvidia-resume.service - NVIDIA system resume actions Loaded: loaded (/lib/systemd/system/nvidia-resume.service; enabled; vendor preset: enabled) Active: inactive (dead) -- 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/1933880 Title: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it Status in nvidia-graphics-drivers-465 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run `sudo apt install nvidia-driver-465`. Then, without a need for a restart, run `sudo apt autoremove nvidia-driver-465`. 2. Leaving the terminal open, suspend the machine. Expected behavior: the machine suspend successfully and can be woken up successfully. Actual behavior: the machine doesn't suspend. It either: - hang with no respond other than SysRq+REISUB (or maybe network, but I didn't test), or - return you back to the login screen. Upon logging in, you'll notice that the terminal you opened is gone. Upon further inspection (on a session that doesn't hang), it's been found that X server died with: Fatal server error: [66.422] (EE) systemd-logind disappeared (stopped/restarted?) And checking journal for systemd-logind log, it said: Error during inhibitor-delayed operation (already returned success to client): Unit nvidia-suspend.service is masked. before the new process takes it place. The system is Ubuntu 20.04, X.org session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 03:34:00 2021 InstallationDate: Installed on 2021-03-15 (105 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=th_TH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=06f2a676-a62c-443a-8bc8-4e0eda4600f4 ro log_buf_len=2M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55756 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1933880/+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
