June 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1172412] alsa: Kingston HyperX Quadcast USB audio output silent at low volume
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172412 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tyson(a)tyson.me Flags| |needinfo?(tyson(a)tyson.me) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172292] Support for 64-bot processors on motherboards with 32-bit UEFI
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172292 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |glin(a)suse.com, | |jlee(a)suse.com, | |tiwai(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172412] alsa: Kingston HyperX Quadcast USB audio output silent at low volume
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172412 http://bugzilla.suse.com/show_bug.cgi?id=1172412#c2 --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- The percentage is a bogus number and cannot be used for judging the loudness in general. The USB audio specifies the volume in 1/100 dB unit, and most likely your firmware is buggy and provides a wrong dB value for the playback volume. Looking at the alsa-info.sh output: state.Quadcast { ..... control.6 { iface MIXER name 'Speaker Playback Volume' value.0 1 value.1 1 comment { access 'read write' type INTEGER count 2 range '0 - 31' dbmin -4000 dbmax -900 dbvalue.0 -3900 dbvalue.1 -3900 } } So the control receives the raw value from 0 to 31 corresponding the dB level from -40dB to -9dB. This looks already strange. Could you check whether you get any signal if you set the raw value greater than 0? e.g. amixer -c0 cset name='Speaker Playback Volume' 0,0 should set the values to 0 and it's likely the silence. Then amixer -c0 cset name='Speaker Playback Volume' 1,1 and check whether you get some output at all. Then increase the value and confirm that you have higher corresponding volume. Then the next step is identify the real loudness (in dB level) to each raw value. At best, compare the output level with other device. You might be able to compare with the output from the onboard audio, too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172215] thumbnail.so do no close while after thumbnails are generated
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172215 http://bugzilla.suse.com/show_bug.cgi?id=1172215#c5 Wolfgang Bauer <wbauer(a)tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #5 from Wolfgang Bauer <wbauer(a)tmo.at> --- Update released. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1099548] can't PXE-boot into openSUSE Leap 15.0 Live image
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1099548 http://bugzilla.suse.com/show_bug.cgi?id=1099548#c15 --- Comment #15 from David Cassany <dcassany(a)suse.com> --- KIWI offers support for two different dracut modules to handle Live images, as stated and well explained in comment 5. PXE-booting live images built with KIWI is already possible by using the livenet and dmsquash dracut modules, however as Marcus and Fabian already pointed, this is not the module used in Leap Live images. Those images use the `kiwi-live` module which provides automatic persistency on writable media. Either using one module or the other is a design choice as this is part of the image description. The feature set of each module is different. KIWI module, currently, is not supporting PXE like features as it does dmsquash plus livenet modules. Please note that this is not a KIWI bug, as mentioned in comment 5 there are two ways to solve that: * Include new features in kiwi-live module to enable pxe boot. We try to address community demands at https://github.com/OSInside/kiwi * Use dmsquash module at the cost of having to rebuild live images changing the dracut live module in use and at the cost of loosing the automatic persistency on writable media. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172303] Missing 32-bit OpenCL support
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172303 http://bugzilla.suse.com/show_bug.cgi?id=1172303#c2 --- Comment #2 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2020:0758-1: An update that has one recommended fix can now be installed. Category: recommended (low) Bug References: 1172303 CVE References: Sources used: openSUSE Leap 15.1 (src): ocl-icd-2.2.11-lp151.4.4.1, opencl-headers-2.2+git.20170617-lp151.3.2.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172413] New: ignition: better handling of missing config
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172413 Bug ID: 1172413 Summary: ignition: better handling of missing config Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: iforster(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When ignition finds no config the system keeps booting nevertheless. As MicroOS has no root password set the system is useless as noone can log in. A second boot will not start ignition again as the trigger file is gone. So how about stopping boot in initrd already if ignition can't find a config? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172412] New: alsa: Kingston HyperX Quadcast USB audio output silent at low volume
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172412 Bug ID: 1172412 Summary: alsa: Kingston HyperX Quadcast USB audio output silent at low volume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: tyson(a)tyson.me QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 838432 --> http://bugzilla.opensuse.org/attachment.cgi?id=838432&action=edit lsusb -v output I'm running Tumbleweed 20200528 with kernel 5.6.14. There is an issue with the Kingston HyperX QuadCast USB microphone + headphone interface (USB 0951:16df). The microphone works fine, but the headphone output only produces sound when the volume in KDE Plasma/ALSAmixer is set at 31% or higher. At 30% or below, there is no sound from the headphone interface. In Windows and macOS, audio output starts from 1%. I'm not sure whether this is the right place to report or if it should've gone upstream. It seems like this device may need a quirk entry in ALSA, but that's just a guess. I know this will be difficult to diagnose without direct access to the hardware, but am happy to provide more information or test any patches. I will attach alsa-info and lsusb -v output. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1172291] New: [Build 20200528] openQA test fails in glibc_locale, locale setup not reflected in ldd --help output
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172291 Bug ID: 1172291 Summary: [Build 20200528] openQA test fails in glibc_locale, locale setup not reflected in ldd --help output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1282825/modules/glib c_locale/steps/33 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mloviska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos@64bit_virtio fails in [glibc_locale](https://openqa.opensuse.org/tests/1282825/modules/glibc_local… Test case from fails in first verification step of locale setup. The tested JeOS image sets en_US locale setup in jeos-firstboot. Test module glibc_locale modifies locale from en_US to de_DE, verifies if the changes have been applied, reboots and verifies locale settings again. One of the verification steps is to parse output of `ldd --help`. The test case fails because `ldd --help` does not reflect changed locale settings to German. Test strings in the failing step: ``` Expected = Eine Anleitung zum Melden von Programmfehlern finden Sie hier: Got = For bug reporting instructions, please see: ``` https://openqa.opensuse.org/tests/1282825#step/glibc_locale/35 ## Reproducible Fails since (at least) Build [20200520](https://openqa.opensuse.org/tests/1275389) ## Expected result * [sle-15-SP2-JeOS-for-kvm-and-xen](https://openqa.suse.de/tests/4294055#step/glibc_locale/35) * [opensuse-15.2-JeOS-for-kvm-and-xen](https://openqa.opensuse.org/tests/12830… * [opensuse-15.1-JeOS-for-kvm-and-xen](https://openqa.opensuse.org/tests/12831… ## 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 5

[Bug 1172407] printer drivers missing BuildRequires cups-rpm-helper
by bugzilla_noreply＠suse.com 02 Jun '20

02 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1172407 http://bugzilla.suse.com/show_bug.cgi?id=1172407#c1 --- Comment #1 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1172407) was mentioned in https://build.opensuse.org/request/show/810863 Factory / printer-driver-brlaser -- You are receiving this mail because: You are on the CC list for the bug.

1 0