July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1185528] shim-15.4-lp152.4.6.1 fails to mirror enrolled keys
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1185528 https://bugzilla.suse.com/show_bug.cgi?id=1185528#c7 --- Comment #7 from Luke Morrison <lfmorrison(a)gmail.com> --- I can confirm that with shim-15.4-4.7.1.x86_64 installed on the same hardware, mokutil successfully lists all enrolled keys. It seems that the bug, for me, has been resolved. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201015] [SELinux] transactional-update can't run with selinux=permissive under cloud-init
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201015 https://bugzilla.suse.com/show_bug.cgi?id=1201015#c6 --- Comment #6 from Zdenek Kubala <zkubala(a)suse.com> --- Just for the record here is the same denial for audit.log. type=USER_AVC msg=audit(1657632830.178:57): pid=649 uid=483 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_return dest=:1.15 spid=1452 tpid=1451 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:system_r:cloud_init_t:s0 tclass=dbus permissive=0 exe="/usr/bin/dbus-daemon" sauid=483 hostname=? addr=? terminal=?' -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201015] [SELinux] transactional-update can't run with selinux=permissive under cloud-init
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201015 https://bugzilla.suse.com/show_bug.cgi?id=1201015#c5 Zdenek Kubala <zkubala(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zkubala(a)suse.com Assignee|jsegitz(a)suse.com |zkubala(a)suse.com --- Comment #5 from Zdenek Kubala <zkubala(a)suse.com> --- Hi, I take over the bug for the time being and I think I have been able to reproduce it. I'm looking into an issue now. karel:~ # date Tue Jul 12 16:09:52 UTC 2022 karel:~ # ps awux | egrep "trans|snapp" root 399 0.0 0.0 0 0 ? S 13:32 0:00 [btrfs-transaction] root 453 0.0 0.0 0 0 ? S 13:32 0:00 [btrfs-transaction] root 1255 0.0 0.2 8028 4352 ? S 13:33 0:00 /bin/bash /usr/sbin/transactional-update -n pkg in cifs-utils root 1256 0.0 0.0 2832 1208 ? S 13:33 0:00 tee -a /var/log/transactional-update.log root 1448 0.0 0.1 8028 2100 ? S 13:33 0:00 /bin/bash /usr/sbin/transactional-update -n pkg in cifs-utils root 1450 0.0 0.0 2832 1148 ? S 13:33 0:00 tee -a /var/log/transactional-update.log root 1451 0.0 0.3 14792 6520 ? S 13:33 0:00 snapper create --from 1 --read-write --print-number --description Snapshot Update of #1 --userdata transactional-update-in-progress=yes root 1452 0.0 0.3 161772 6812 ? Ssl 13:33 0:00 /usr/sbin/snapperd root 2491 0.0 0.0 4064 2016 pts/0 S+ 16:09 0:00 grep -E --color=auto trans|snapp -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 966042] yast command-line usage emits "unable to close filehandle properly" perl warning from ag_tty at exit
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=966042 https://bugzilla.suse.com/show_bug.cgi?id=966042#c13 Martin Vidner <mvidner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msvec(a)suse.com --- Comment #13 from Martin Vidner <mvidner(a)suse.com> --- *** Bug 1201046 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201046] New: yast2-users cmdline error
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201046 Bug ID: 1201046 Summary: yast2-users cmdline error Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: msvec(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Adding a user using yast2-users cmdline interface throws an error: bash# yast2 users add username=someuser uid=12345 Password for New User: Confirm the password: Warning: unable to close filehandle properly: Bad file descriptor, <STDIN> line 9 during global destruction (#1) (S io) There were errors during the implicit close() done on a filehandle when its reference count reached zero while it was still open, e.g.: { open my $fh, '>', $file or die "open: '$file': $!\n"; print $fh $data or die "print: $!"; } # implicit close here Because various errors may only be detected by close() (e.g. buffering could allow the print in this example to return true even when the disk is full), it is dangerous to ignore its result. So when it happens implicitly, perl will signal errors by warning. Prior to version 5.22.0, perl ignored such errors, so the common idiom shown above was liable to cause silent data loss. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1196632] Raspberry Pi 3: kernel errors in journal
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1196632 https://bugzilla.suse.com/show_bug.cgi?id=1196632#c12 Stefan Wahren <stefan.wahren(a)i2se.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan.wahren(a)i2se.com Flags| |needinfo? --- Comment #12 from Stefan Wahren <stefan.wahren(a)i2se.com> --- Can anyone provide the version of the videocore firmware (visible as a date in the kernel log)? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201392] Kernel 5.18.9-2.1 with enabled simpledrm breaks nvidia driver (use kernel boot option 'nosimplefb=1' as workaround)
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201392 https://bugzilla.suse.com/show_bug.cgi?id=1201392#c36 Thomas Zimmermann <tzimmermann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #36 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi (In reply to Kriton Kyrimis from comment #33) > (In reply to Kriton Kyrimis from comment #31) > > I think I'll add "nosimplefb=1" to /etc/default/grub.conf until further > > notice. > > Hmmm.. no. This way I can't get a Linux console wit ctl-alt-f2. Oh, well. > Back to nouveau. Thanks for the log. Nvidia requires efifb for displaying the console, but that driver isn't mentioned in your log, which is surprising. I'll try to reproduce the bug tomorrow -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200990] New: yast2-perl-bindings does not work with perl-5.36.0
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200990 Bug ID: 1200990 Summary: yast2-perl-bindings does not work with perl-5.36.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: mls(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- New perl versions like 5.36.0, calling SvPV or SvPV_nolen will no longer set the POK flag. The perldelta man page says: Reading the string form of an integer value no longer sets the flag SVf_POK. The string form is still cached internally, and still re-read directly by the macros SvPV(sv) etc (inline, without calling a C function). XS code that already calls the APIs to get values will not be affected by this change. XS code that accesses flags directly instead of using API calls to express its intent might break, but such code likely is already buggy if passed some other values, such as floating point values or objects with string overloading. The code in yast2-perl-bindings relies on the old behavior in a couple of places. For example, YPerl::fromPerlScalarToAny looks like this: const char *pv = SvPV_nolen (sv); if (SvPOK (sv)) { val = YCPString (pv); } This will no longer work. Please change the if condition to: if (SvPOK(sv) || SvIOK(sv) || SvNOK(sv)) -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1201349] [Build 20220708] pipewire: no audio after logout/login
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201349 https://bugzilla.suse.com/show_bug.cgi?id=1201349#c2 --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Fabian Vogt from comment #1) > So pipewire needs to check for accessibility of more device files. I'll file > a report upstream. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2534 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201349] [Build 20220708] pipewire: no audio after logout/login
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201349 https://bugzilla.suse.com/show_bug.cgi?id=1201349#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |fvogt(a)suse.com --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- I was able to reproduce it with wireplumber log-level 3. It appears to be a race condition between logind/inotify and pipewire/wireplumber. Works: Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Unknown PCM dcahdmi:0,10 Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Error opening PCM device dcahdmi:0,10: No such file or directory Jul 12 10:15:00 localhost.localdomain org_kde_powerdevil[1642]: org.kde.powerdevil: The profile "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, a configuration problem, or because the action is not supported Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Successfully attached to mixer 'hw:0' Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Device hw:0,0 doesn't support 64 channels, changed to 2. Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Device hw:0,0 doesn't support sample format s32le, changed to s16le. Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Device hw:0,0 doesn't support 64 channels, changed to 2. Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Device hw:0,0 doesn't support sample format s32le, changed to s16le. Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Profile output:stereo-fallback+input:stereo-fallback available unknown -> yes Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Profile output:stereo-fallback available unknown -> yes Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Profile input:stereo-fallback available unknown -> yes Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Profile pro-audio available yes -> unknown Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: activate profile: off (0) Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: <WpDevice:35:0x55a0872b34f0> restore routes for profile off Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Default profile not found for alsa_card.pci-0000_00_0a.0 Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Best profile changed to output:stereo-fallback+input:stereo-fallback in alsa_card.pci-0000_00_0a.0 Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Setting profile output:stereo-fallback+input:stereo-fallback on alsa_card.pci-0000_00_0a.0 Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: activate profile: output:stereo-fallback+input:stereo-fallback (1) Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Device: Stereo mapping 'Stereo' (stereo-fallback). Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Activating path analog-output-lineout Jul 12 10:15:00 localhost.localdomain wireplumber[2315]: Hardware volume ranges from -125.00 dB to 0.00 dB. Fails: Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: Unknown PCM dcahdmi:0,10 Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: Error opening PCM device dcahdmi:0,10: No such file or directory Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: open '/dev/snd/pcmC0D0c' failed (-13) Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: Error opening PCM device hw:0: Permission denied Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: open '/dev/snd/pcmC0D0c' failed (-13) Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: Error opening PCM device hw:0: Permission denied Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: open '/dev/snd/pcmC0D0c' failed (-13) Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: Error opening PCM device hw:0: Permission denied Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: open '/dev/snd/pcmC0D0p' failed (-13) Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: Error opening PCM device hw:0: Permission denied Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: open '/dev/snd/pcmC0D0p' failed (-13) Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: Error opening PCM device hw:0: Permission denied Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: open '/dev/snd/pcmC0D0p' failed (-13) Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: Error opening PCM device hw:0: Permission denied Jul 12 10:12:16 localhost.localdomain org_kde_powerdevil[1642]: org.kde.powerdevil: The profile "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, a configuration problem, or because the action is not supported Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: Device hw:0,0 doesn't support 64 channels, changed to 2. Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: Device hw:0,0 doesn't support sample format s32le, changed to s16le. Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: Device hw:0,0 doesn't support 64 channels, changed to 2. Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: Device hw:0,0 doesn't support sample format s32le, changed to s16le. Jul 12 10:12:16 localhost.localdomain wireplumber[2315]: activate profile: off (0) When switching active sessions, logind adds and removes "uaccess" acls for sound device access. pipewire listens to inotify ATTRIB events on /dev/snd/* and checks for accessibility there. The order of those ATTRIB changes appears to be random, and some combinations result in wireplumber trying to enable devices before they're completely accessible. Specifically, if /dev/snd/controlC0 is made accessible before the others, it breaks. If it made accessible last, it works. This can be reproduced manually by assuming the role of logind and setting acls manually: # Break access -> audio disabled setfacl -m user:linux:- /dev/snd/* # Grant access in the working order -> audio works again setfacl -m user:linux:rw- /dev/snd/{pcm,hw,seq,timer}*; sleep 1; setfacl -m user:linux:rw- /dev/snd/controlC0 # Break access again -> audio disabled setfacl -m user:linux:- /dev/snd/* # Grant access in the broken order -> audio still broken! setfacl -m user:linux:rw- /dev/snd/controlC0; sleep 1; setfacl -m user:linux:rw- /dev/snd/* So pipewire needs to check for accessibility of more device files. I'll file a report upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 0