May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1171289] New: Kernel 5.6+ breaks KVM passthrough
by bugzilla_noreply＠novell.com 06 May '20

06 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171289 Bug ID: 1171289 Summary: Kernel 5.6+ breaks KVM passthrough Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: k6demello28(a)fastmail.fm QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 837477 --> http://bugzilla.opensuse.org/attachment.cgi?id=837477&action=edit stack trace generated while starting vm with passthrough I am having the problem outlined in the kernel bugzilla (207489), where pci passthrough with KVM on intel is causing a kernel panic. I have attached the stack trace produced with 5.6.11, but it is identical with all versions of the 5.6 kernel that I have tested so far. https://bugzilla.kernel.org/show_bug.cgi?id=207489 There is a patch provided in the kernel bug that solves the issue. Can this patch be included in the openSUSE kernel for versions 5.6+ that are included in tumbleweed? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1171293] New: WebRTC apps manipulating mic gain to 100%
by bugzilla_noreply＠novell.com 06 May '20

06 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171293 Bug ID: 1171293 Summary: WebRTC apps manipulating mic gain to 100% Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi there, recently I've been running into major problems with Electron apps for the Linux desktop (Microsoft Teams and Riot.im) modifying my mic input levels. Also Chromium/Chrome do the same thing during WebRTC calls, they raise my mic level to 100%, thus completely saturating the audio and making it unusable. I drop it back down manually, but within a few seconds it creeps back up to 100% again. In my case it tries to max out the mic gain, but I've read lots of other user reports where it tries to lower the user's mic gain to an unusable level. Sometimes this is the result of a "smart" VoIP program like Skype that has an option to allow the program to adjust the audio device levels. But my problem is that all my VoIP apps use WebRTC, which appears to include its own implementation of AGC as part of the protocol, and it's obviously buggy in anything based on Chromium (Chrome, electron apps, etc.), and there's no way to disable it. There have been bug reports to Chrome(ium) for years about this and they obviously don't care. Firefox doesn't exhibit this behavior, but unfortunately a lot of WebRTC apps are either Electron (based on Chromium) or else they don't support Firefox very well. Ultimately, I think this behavior should be controllable via PulseAudio, since we can't assume that all apps with have sane behavior. In Windows there's an option to not allow programs to control a specific device. It appears this should be possible in `/usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf` by changing `volume = merge` to `volume = off` or `volume = XX` according to what I've read. But since the profiles are under `/usr/share/` they're obviously not meant to be user configurable. Is there any way that these profiles could be moved to `/etc/pulse` and/or `~/.config/pulse/`? Or is there any other workaround? This is a major issue that is making it almost impossible for me to work from home.... Thanks, I appreciate the help. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171044] Incomplete list of alsa audio inputs
by bugzilla_noreply＠novell.com 06 May '20

06 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1171044 http://bugzilla.suse.com/show_bug.cgi?id=1171044#c9 --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- The revision 326 in my OBS home:tiwai:branches:multimedia:libs/alsa repo should contain the revert of the problematic change. Please check it later. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1165055] [doc] Procedure 27.2: Assigning a PCI Device to a VM Guest via VFIO
by bugzilla_noreply＠novell.com 06 May '20

06 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1165055 http://bugzilla.suse.com/show_bug.cgi?id=1165055#c1 Frank Sundermeyer <fs(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Frank Sundermeyer <fs(a)suse.com> --- Fixed with https://github.com/SUSE/doc-sle/commit/a42abc0064c548 Thanks for the report, te fix will be published soon. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171044] Incomplete list of alsa audio inputs
by bugzilla_noreply＠novell.com 06 May '20

06 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1171044 http://bugzilla.suse.com/show_bug.cgi?id=1171044#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Ah wait. You're checking the input direction, arecord -L, *not* the output aplay -L? That explains. The recent fixes changed front and iec958 to be output-only. I guess this is a bad move as applications depend on "front" capture as well. (Basically iec958 could be also captured, so it's no output-only, either.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1165697] The Bash Shell Startup Files Initialization sequence order.
by bugzilla_noreply＠novell.com 06 May '20

06 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1165697 Frank Sundermeyer <fs(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |https://trello.com/c/CZrQof | |rZ/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171044] Incomplete list of alsa audio inputs
by bugzilla_noreply＠novell.com 06 May '20

06 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1171044 http://bugzilla.suse.com/show_bug.cgi?id=1171044#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Maybe it's another commit. Let's try the another shot. Could you retest with the package in OBS home:tiwai:branches:multimedia:libs/alsa again? (The revision 324, which should be published soon later) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1170107] VUL-0: CVE-2020-6458,CVE-2020-6459,CVE-2020-6460: chromium: multiple security issues fixed in 81.0.4044.122
by bugzilla_noreply＠novell.com 06 May '20

06 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1170107 http://bugzilla.suse.com/show_bug.cgi?id=1170107#c6 --- Comment #6 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2020:0615-1: An update that fixes 5 vulnerabilities is now available. Category: security (important) Bug References: 1170107 CVE References: CVE-2020-0561,CVE-2020-6458,CVE-2020-6459,CVE-2020-6460,CVE-2020-6462 Sources used: openSUSE Backports SLE-15-SP1 (src): chromium-81.0.4044.129-bp151.3.79.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1146646] LTO: crash build failure TW ppc64le
by bugzilla_noreply＠novell.com 06 May '20

06 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1146646 http://bugzilla.suse.com/show_bug.cgi?id=1146646#c9 --- Comment #9 from Martin Liška <martin.liska(a)suse.com> --- It's caused by a fact that part of the objects are built with -mminimal-toc. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171044] Incomplete list of alsa audio inputs
by bugzilla_noreply＠novell.com 06 May '20

06 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1171044 http://bugzilla.suse.com/show_bug.cgi?id=1171044#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Hrm, I'm trying to reproduce the issue but I can't here. Do you have any own setup in ~/.asoundrc or else? It does look to me as if defaults.namehint.basic is set off. -- You are receiving this mail because: You are on the CC list for the bug.

1 0