October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1191260] kernel 5.18.8 post scriptlets failing
by bugzilla_noreply＠suse.com 04 Oct '21

04 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191260 https://bugzilla.suse.com/show_bug.cgi?id=1191260#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com, | |kernel-bugs(a)opensuse.org Assignee|kernel-bugs(a)opensuse.org |martin.wilck(a)suse.com Severity|Normal |Major --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- The previous %post always did exit 0: # vim: set sts=4 sw=4 ts=8 noet: if ! command -v mokutil >/dev/null; then exit 0 fi # Only apply CA check on the kernel package certs (bsc#1173115) if [ 0 = 0 ] && mokutil -h | grep -q "ca-check"; then MOK_ARG="--ca-check" else MOK_ARG="" fi # XXX: Only call mokutil if UEFI and shim are used for cert in 1AA60533; do cert="/etc/uefi/certs/${cert}.crt" if ! mokutil --import "$cert" --root-pw ${MOK_ARG}; then echo "Failed to import $cert" fi done exit 0 exit 0 There's also a failure inside OBS builds: [ 162s] (183/197) Installing: kernel-kvmsmall-5.14.8-1.1.x86_64 [..............done] [ 162s] Additional rpm output: [ 162s] Please run "/usr/bin/dracut -f /boot/initrd-5.14.8-1-kvmsmall 5.14.8-1-kvmsmall" as soon as your system is complete. [ 162s] You may need to setup and install the boot loader using the [ 162s] available bootloader for your platform (e.g. grub, lilo, zipl, ...). [ 162s] warning: %post(kernel-kvmsmall-5.14.8-1.1.x86_64) scriptlet failed, exit status 1 That doesn't show the cause for the non-zero exit directly though. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191109] yast2-storage-ng "Device Graph" missing since libyui-qt-graph15 neither required nor recommended
by bugzilla_noreply＠suse.com 04 Oct '21

04 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191109 https://bugzilla.suse.com/show_bug.cgi?id=1191109#c10 Jos� Iv�n L�pez Gonz�lez <jlopez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #10 from Jos� Iv�n L�pez Gonz�lez <jlopez(a)suse.com> --- Backported to SLE-15-SP3: * https://github.com/yast/yast-storage-ng/pull/1232 * https://build.suse.de/request/show/255576 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191255] New: Kernel 5.3.18 does not support nested virtualization in openstack with guests running kernel 5.14 and later
by bugzilla_noreply＠suse.com 04 Oct '21

04 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191255 Bug ID: 1191255 Summary: Kernel 5.3.18 does not support nested virtualization in openstack with guests running kernel 5.14 and later Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: dcermak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852890 --> http://bugzilla.opensuse.org/attachment.cgi?id=852890&action=edit Screenshot of the guest VM guest's VNC screen I have started observing an issue with virtualized hosts in openstack running the Leap 15.3 kernel (5.3.18): guests with the Leap 15.4 or Tumbleweed kernel fail to boot. I was only able to capture a screenshot of the VNC output of the guest VM (see attachment) and I was told that this means: RAX is holding -ENOSYS, so probably something is not supported (user-mode x86_64 kernel trying to do a mincore syscall, which seems to return -ENOSYS) Updating the host VM to a Leap 15.4 kernel makes the issue go away, but that is not really a good solution. This issue only appears on openstack. I have tried to reproduce it with ordinary virtual machines with qemu and there everything worked. Virtualbox is also not impacted and neither are bare metal hosts. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1174450] New: Can't run Flatpak Discord in Plasma Wayland session
by bugzilla_noreply＠suse.com 04 Oct '21

04 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1174450 Bug ID: 1174450 Summary: Can't run Flatpak Discord in Plasma Wayland session Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: pointedstick(a)zoho.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- flatpak run com.discordapp.Discord (Discord:4): Gtk-WARNING **: 13:36:34.116: cannot open display: :99.0 [fake-sandbox: zypak-sandbox] No data could be read (host died?) [fake-sandbox: zypak-sandbox] Quitting Zygote... I found some old discussions about this being caused by hostname issues. Here is my computer's hostname: nate@Liberator:~$ hostname Liberator nate@Liberator:~$ hostnamectl Static hostname: Liberator Icon name: computer-convertible Chassis: convertible Machine ID: c37a55dec6d94be6b9e18fb3bc8a7347 Boot ID: 47391a97617a4eb09975d676781f127a Operating System: openSUSE Tumbleweed CPE OS Name: cpe:/o:opensuse:tumbleweed:20200720 Kernel: Linux 5.7.7-1-default Architecture: x86-64 Works fine in X11, it's just broken on Wayland. Also, other Flatpak apps such as Spectral do run on Wayland. It's just Discord that's broken in this way for me. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1190882] No sound through Internet browswers
by bugzilla_noreply＠suse.com 03 Oct '21

03 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190882 https://bugzilla.suse.com/show_bug.cgi?id=1190882#c15 --- Comment #15 from Joel Miller <jm-hotmail(a)hotmail.com> --- Your queries prompted me to delve deeper into this issue, enabling me to determine what I believe is the cause of the missing audio. As you noted in Comment 7, pulseaudio is now required for web browsers. Based on my experience, this had no impact on openSuSE prior to Leap 15.3 (see the response in https://support.mozilla.org/en-US/questions/1209469) Because I frequently engage in administrative tasks, I have found it more productive to log in as root rather than as a user, notwithstanding the security concerns. In its standard configuration, pulseaudio runs only in user sessions, not in ��system�� mode (i.e., login as root). (See https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Sys… and disfavor of system-wide implementation of pulseaudio: https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Wha…) While web browser sound does not work in a root session on a 15.3 platform because pulseaudio is not running, it functions properly in a user session. I ran the alsa-info script in a user session on machine #9 (running Leap 15.3) �� the report states that pulseaudio is running (see the alsa-info.sh report 10-02-21 attachment in comment 14 above). Further, the user session report��s ALSA/HDA dmesg section is blank �� i.e., no issues. And I confirmed that Firefox sound works in 15.3 user sessions on four different machines (two Asus-motherboard desktops, an ACER all-in-one, and a 2019 Dell laptop). I looked briefly at using apulse in lieu of pulseaudio, but the comment regarding Firefox in a GitHub description gives me pause (see https://github.com/i-rinat/apulse; scroll down to ��Firefox 58, etc.�� under ��Known Issues��). Pipewire may also fail to deliver sound from Firefox. Since pulseaudio works well in a user session, I see no reason to seek an alternative at this time. Please let me have your comments. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190882] No sound through Internet browswers
by bugzilla_noreply＠suse.com 03 Oct '21

03 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190882 https://bugzilla.suse.com/show_bug.cgi?id=1190882#c14 --- Comment #14 from Joel Miller <jm-hotmail(a)hotmail.com> --- Created attachment 852886 --> https://bugzilla.suse.com/attachment.cgi?id=852886&action=edit the alsa-info.sh report 10-02-21 alsa-info script generated in a 15.3 user session -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191247] audio goes to mono after waking up from sleep
by bugzilla_noreply＠suse.com 03 Oct '21

03 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191247 http://bugzilla.opensuse.org/show_bug.cgi?id=1191247#c4 --- Comment #4 from Andrea P <pandre.x(a)gmail.com> --- (In reply to Takashi Iwai from comment #3) > Thanks for quick testing. > > Then could you load alsa-info.sh output from the patched kernel after > suspend/resume? Run the script with --no-upload, and use Bugzilla > attachment. Thank you. Sorry but I have no idea how to run this script. where is located? so sorry, I'm not that expert :D > Also, for verifying whether it's a driver PM problem, try the following: > > - Before and after suspend/resume, try to play without PA, PW or JACK but > via ALSA native API, e.g. > % aplay -Dplughw:XXX foo.wav > where XXX is the card number like 0, 1, 2, corresponding to the device > index appearing in /proc/asound/cards. > > I suppose this also results in the mono output? Yes indeed. It does sound as mono after waking up from sleep > > - Check whether the problem persists with suspend-to-RAM and suspend-to-disk > (hibernate). I assume you're dealing with the former, right? Hibernate it doesn't work on my PC (maybe because I don't have a swap partition?). > > - Last but not least, check whether re-loading the driver fixes the problem > without re-plugging. You might need to go out of desktop session once, > unload snd-usb-audio module and re-load snd-usb-audio module on Linux > console. Again, so sorry but I don't know how to stop and re-load this module. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003226] New: Slow loading/page construction
by bugzilla_noreply＠novell.com 03 Oct '21

03 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1003226 Bug ID: 1003226 Summary: Slow loading/page construction Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: matthias(a)mailaender.name QA Contact: adrian(a)suse.com Found By: --- Blocker: --- I already reported my dashboard loading extremely slow https://github.com/openSUSE/open-build-service/issues/2086 which seems to be strengthened by my activity as I have 3 pages full of open requests submitted to Factory or devel project awaiting peer review from maintainers. How since a few weeks the whole website became super slow. Viewing regular package pages or repository enable/disable sites, which I usually quickly click to avoid redundant rebuilds. See also https://github.com/openSUSE/open-build-service/issues/586 I usually only branch or create packages via the web interface and use osc with local builds and only commit stuff that works. But with the current response time it is far too tedious. Pages take several minutes to load for me. Tested on multiple V-DSL connections at various day times. It seems to be a fundamental problem that has gotten worse lately. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1191247] audio goes to mono after waking up from sleep
by bugzilla_noreply＠suse.com 03 Oct '21

03 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191247 http://bugzilla.opensuse.org/show_bug.cgi?id=1191247#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for quick testing. Then could you load alsa-info.sh output from the patched kernel after suspend/resume? Run the script with --no-upload, and use Bugzilla attachment. Also, for verifying whether it's a driver PM problem, try the following: - Before and after suspend/resume, try to play without PA, PW or JACK but via ALSA native API, e.g. % aplay -Dplughw:XXX foo.wav where XXX is the card number like 0, 1, 2, corresponding to the device index appearing in /proc/asound/cards. I suppose this also results in the mono output? - Get alsa-info.sh outputs before and after the suspend/resume. - Check whether the problem persists with suspend-to-RAM and suspend-to-disk (hibernate). I assume you're dealing with the former, right? - Last but not least, check whether re-loading the driver fixes the problem without re-plugging. You might need to go out of desktop session once, unload snd-usb-audio module and re-load snd-usb-audio module on Linux console. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191204] VUL-0: chromium: multiple security issues fixed in 94.0.4606.71
by bugzilla_noreply＠suse.com 03 Oct '21

03 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191204 http://bugzilla.opensuse.org/show_bug.cgi?id=1191204#c2 --- Comment #2 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1191204) was mentioned in https://build.opensuse.org/request/show/922846 15.2 / chromium https://build.opensuse.org/request/show/922848 Backports:SLE-15-SP3 / chromium -- You are receiving this mail because: You are on the CC list for the bug.

1 0