July 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1188146] Request for a free implementation of aptX be added
by bugzilla_noreply＠suse.com 09 Jul '21

09 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188146 https://bugzilla.suse.com/show_bug.cgi?id=1188146#c1 --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Well, Bugzilla is a place to track "bugs", or at most some enhancements on the existing stuff. At best, raise the issue on opensuse factory ML. We can take the package build on OBS multimedia:libs at first (unless it looks dubious), and ask the legal team to review for TW. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188105] virtualbox after last updates of tumbleweed did not run vbox machines
by bugzilla_noreply＠suse.com 09 Jul '21

09 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188105 http://bugzilla.opensuse.org/show_bug.cgi?id=1188105#c4 --- Comment #4 from Sebastian Wagner <sebix+novell.com(a)sebix.at> --- > A workaround is to supply the option 'split_lock_detect=none' as a boot-time parameter. This can be set using YaST under the System->BootLoader option. Using the 'Kernel Parameters' tab, add the option there. This workaround does not work for me, with kernel 5.13.0-1-default. Using the older kernel version 5.12.13-1-default works for me. Possibly this bug is a duplicate of https://bugzilla.opensuse.org/show_bug.cgi?id=1188089 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188120] nothing provides '/usr/bin/pidof' needed by the to be installed lsb-4.0.fake-lp153.1.1.x86_64
by bugzilla_noreply＠suse.com 09 Jul '21

09 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188120 https://bugzilla.suse.com/show_bug.cgi?id=1188120#c5 --- Comment #5 from Martin Wilck <martin.wilck(a)suse.com> --- The release request is actually in "accepted" status: https://build.opensuse.org/request/show/900169 Not sure why it hasn't hit the repos yet. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188120] nothing provides '/usr/bin/pidof' needed by the to be installed lsb-4.0.fake-lp153.1.1.x86_64
by bugzilla_noreply＠suse.com 09 Jul '21

09 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188120 https://bugzilla.suse.com/show_bug.cgi?id=1188120#c4 --- Comment #4 from Martin Wilck <martin.wilck(a)suse.com> --- It isn't lost. https://build.opensuse.org/project/show/openSUSE:Maintenance:16451 It seems to be held back by unrelated failures. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188105] virtualbox after last updates of tumbleweed did not run vbox machines
by bugzilla_noreply＠suse.com 09 Jul '21

09 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188105 Sebastian Wagner <sebix+novell.com(a)sebix.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebix+novell.com(a)sebix.at -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186258] New: [Build 20210518] psmisc: calling out to setcap not allowed
by bugzilla_noreply＠suse.com 09 Jul '21

09 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1186258 Bug ID: 1186258 Summary: [Build 20210518] psmisc: calling out to setcap not allowed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1749271/modules/lsof /steps/3 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-filesystem@64bit_virtio fails in [lsof](https://openqa.opensuse.org/tests/1749271/modules/lsof/steps/3) ## Test suite description Filesystems JeOS test suite. Maintainer: qa-c(a)suse.de Explicitly calling out to setcap in a spec file is not permitted. For this, we have the permissions package that assigns capabilities to binaries, based on the wanted trust level of an admin. As the change is not working reliably anyway (setcap is not available in all cases) the change is being reverted in :Factory ## Reproducible Fails since (at least) Build [20210518](https://openqa.opensuse.org/tests/1749271) (current job) ## Expected result Last good: [20210517](https://openqa.opensuse.org/tests/1747260) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1188157] New: [yast instserver] missing final line break in SLP's reg file
by bugzilla_noreply＠suse.com 09 Jul '21

09 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188157 Bug ID: 1188157 Summary: [yast instserver] missing final line break in SLP's reg file 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: jiri.belka(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- `yast instserver` (yast2-instserver-4.4.0-1.1.noarch) does not add final line break in SLPd's reg file: ---%>--- t14s:~ # cat -nvte /etc/slp.reg.d/YaST-sle15sp2-x86_64.reg;echo 1 service:install.suse:http://0.0.0.0/suse/sle15sp2-x86_64/CD1,en,65535$ 2 description= t14s:~ # ---%<--- ^^ see missing '$' after 'description='. repro steps: 1. yast instserver 2. add new repo and enable SLP 3. check reg file content if it has final line break -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188143] Firewall Zone-Interface association not applied with "Reload"
by bugzilla_noreply＠suse.com 09 Jul '21

09 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188143 https://bugzilla.suse.com/show_bug.cgi?id=1188143#c3 Georg Pfuetzenreuter <mail(a)georg-pfuetzenreuter.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mail@georg-pfuetz | |enreuter.net) | --- Comment #3 from Georg Pfuetzenreuter <mail(a)georg-pfuetzenreuter.net> --- Created attachment 850889 --> https://bugzilla.suse.com/attachment.cgi?id=850889&action=edit save_y2logs_fwdrestart And this one is after having worked around it by restarting the service (in case one which has the changes show up is needed). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188143] Firewall Zone-Interface association not applied with "Reload"
by bugzilla_noreply＠suse.com 09 Jul '21

09 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188143 https://bugzilla.suse.com/show_bug.cgi?id=1188143#c2 --- Comment #2 from Georg Pfuetzenreuter <mail(a)georg-pfuetzenreuter.net> --- Created attachment 850888 --> https://bugzilla.suse.com/attachment.cgi?id=850888&action=edit save_y2logs_failed My apologies! I forgot to attach the archive. This one is after performing the steps to reproduce. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186884] New: Launching Tumbleweed under SEV-ES currently fails when kernel parses MOVVar EFI table
by bugzilla_noreply＠suse.com 09 Jul '21

09 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1186884 Bug ID: 1186884 Summary: Launching Tumbleweed under SEV-ES currently fails when kernel parses MOVVar EFI table Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jroedel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 849947 --> https://bugzilla.suse.com/attachment.cgi?id=849947&action=edit Full guest boot log with efi=debug Launching TW as an SEV-ES guest currently fails with this kernel panic: [ 2.907677] general protection fault, probably for non-canonical address 0x43a3c02ebe2b54c6: 0000 [#1] SMP NOPTI [ 2.910048] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.12.4-2-default #1 openSUSE Tumbleweed [ 2.911636] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 [ 2.911636] RIP: 0010:efi_mokvar_entry_next+0x34/0x40 [ 2.911636] Code: c5 01 48 8b 17 48 c7 07 00 00 00 00 48 85 c0 74 24 48 85 d2 74 14 80 3a 00 74 18 48 8b 82 00 01 00 00 48 8d 84 02 08 01 00 00 <80> 38 00 74 04 48 89 07 c3 31 c0 c3 0f 1f 44 00 00 41 54 4c 8b 25 [ 2.911636] RSP: 0018:ffffbca30001fe48 EFLAGS: 00010286 [ 2.911636] RAX: 43a3c02ebe2b54c6 RBX: 0000000000000000 RCX: 0000000000000000 [ 2.911636] RDX: ffffbca300294000 RSI: ffff9e8fc417b448 RDI: ffffbca30001fe50 [ 2.911636] RBP: ffff9e8fc4005a80 R08: 0000000000000000 R09: ffff9e8fc011ad90 [ 2.911636] R10: ffff9e8fc1294270 R11: 0000000000000000 R12: 0000000000000000 [ 2.911636] R13: ffffffff96e88774 R14: 0000000000000000 R15: 0000000000000000 [ 2.911636] FS: 0000000000000000(0000) GS:ffff9e903bc00000(0000) knlGS:0000000000000000 [ 2.911636] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 2.911636] CR2: 0000000000000000 CR3: 000080001fc10000 CR4: 00000000003506f0 [ 2.911636] Call Trace: [ 2.911636] efi_mokvar_sysfs_init+0x12a/0x172 [ 2.911636] ? efi_mokvar_table_init+0x18a/0x18a [ 2.911636] do_one_initcall+0x44/0x1d0 [ 2.911636] ? __kmalloc+0xc0/0x2d0 [ 2.911636] kernel_init_freeable+0x1ef/0x24b [ 2.911636] ? rest_init+0xb4/0xb4 [ 2.911636] kernel_init+0xa/0x10c [ 2.911636] ret_from_fork+0x22/0x30 [ 2.911636] Modules linked in: [ 2.944868] ---[ end trace 7fa546069e99e464 ]--- [ 2.946173] RIP: 0010:efi_mokvar_entry_next+0x34/0x40 [ 2.947389] Code: c5 01 48 8b 17 48 c7 07 00 00 00 00 48 85 c0 74 24 48 85 d2 74 14 80 3a 00 74 18 48 8b 82 00 01 00 00 48 8d 84 02 08 01 00 00 <80> 38 00 74 04 48 89 07 c3 31 c0 c3 0f 1f 44 00 00 41 54 4c 8b 25 [ 2.951803] RSP: 0018:ffffbca30001fe48 EFLAGS: 00010286 [ 2.953227] RAX: 43a3c02ebe2b54c6 RBX: 0000000000000000 RCX: 0000000000000000 [ 2.954899] RDX: ffffbca300294000 RSI: ffff9e8fc417b448 RDI: ffffbca30001fe50 [ 2.956397] RBP: ffff9e8fc4005a80 R08: 0000000000000000 R09: ffff9e8fc011ad90 [ 2.957987] R10: ffff9e8fc1294270 R11: 0000000000000000 R12: 0000000000000000 [ 2.959624] R13: ffffffff96e88774 R14: 0000000000000000 R15: 0000000000000000 [ 2.961414] FS: 0000000000000000(0000) GS:ffff9e903bc00000(0000) knlGS:0000000000000000 [ 2.963132] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 2.964493] CR2: 0000000000000000 CR3: 000080001fc10000 CR4: 00000000003506f0 [ 2.965970] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 2.967745] Kernel Offset: 0x13c00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) The reason for this is an upstream bug where the MOKVar EFI table is mapped as u nencrypted memory while it needs to be mapped encrypted. -- You are receiving this mail because: You are on the CC list for the bug.

1 6