July 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1187326] New: system won't boot if selinux is enabled during install
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187326 Bug ID: 1187326 Summary: system won't boot if selinux is enabled during install Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: vampird(a)adinet.com.uy QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- During the install you can click on security and change the selinux mode to permissive or enforcing, since there's no selinux policy available to install... the system won't boot after the install. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1187825] New: Wrong/"Missing" firmware for Creative ZxR audio card with compressed kernel-modules
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187825 Bug ID: 1187825 Summary: Wrong/"Missing" firmware for Creative ZxR audio card with compressed kernel-modules Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: stabsy(a)tuta.io QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0 Build Identifier: When using the compressed kernel-firmware modules with the Creative SB ZxR audio card, there seems to be a missing module in lib/firmware. The card needs ctefx.bin, but only ctefx-desktop.bin and ctefx-r3di.bin is in /lib/firmware. The old kernel-firmware package (the uncompressed one) seems to have it, as my soundcard always works. (And yes, I also installed the kernel-firmware-all package to pull in all the drivers to no effect). I got it working by making a copy of ctefx-desktop.bin and then renaming simply renaming the copy to ctefx.bin Reproducible: Always Steps to Reproduce: 1. Install opensuse Tumbleweed with kernel-firmware-all 2. Boot into newly installed system. Actual Results: No audio. Expected Results: That I have audio. alsa-info.sh https://paste.opensuse.org/179b8cb5 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1188068] [Build 20210705][WSL] YaST2 firstboot prompts user to define root password
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188068 https://bugzilla.suse.com/show_bug.cgi?id=1188068#c2 --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- Created attachment 850816 --> https://bugzilla.suse.com/attachment.cgi?id=850816&action=edit y2log -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188068] [Build 20210705][WSL] YaST2 firstboot prompts user to define root password
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188068 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel(a)suse.com, | |sle-ms(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188068] [Build 20210705][WSL] YaST2 firstboot prompts user to define root password
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188068 https://bugzilla.suse.com/show_bug.cgi?id=1188068#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com Component|WSL |YaST2 Assignee|sle-ms(a)suse.de |yast2-maintainers(a)suse.de QA Contact|qa-c(a)suse.de |jsrain(a)suse.com --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- There's another issue after that, firstboot_write_wsl.rb is not compatible with the new yast2-users and crashes. I made sr 904559 as a quick fix (which breaks compatibility with older YaST), but I wonder whether that could just be done in a firstboot script instead. Showing the root step only when necessary is handled in yast2-users, reassigning to YaST. I'll attach y2log, it contains a second run with my fixed yast2-firstboot-wsl as well which can be ignored. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187641] perf segfaults on armv7
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187641 https://bugzilla.suse.com/show_bug.cgi?id=1187641#c3 --- Comment #3 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos-extra https://openqa.opensuse.org/tests/1827532 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187154] systemd stopped marking framebuffer as "graphic capable" after update from 15.2 to 15.3 - no GUI present after update
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187154 https://bugzilla.suse.com/show_bug.cgi?id=1187154#c38 --- Comment #38 from Franck Bui <fbui(a)suse.com> --- (In reply to Thomas Zimmermann from comment #27) > And there's a patch floating on the ML that generalizes the x86 EFI > frambuffer code for all platforms. So simpledrm will soon work on many > systems. Thomas, can you please let me know when this will happen and will be released in SUSE distros ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187154] systemd stopped marking framebuffer as "graphic capable" after update from 15.2 to 15.3 - no GUI present after update
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187154 https://bugzilla.suse.com/show_bug.cgi?id=1187154#c37 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #37 from Franck Bui <fbui(a)suse.com> --- (In reply to Franck Bui from comment #34) > Let's see whether upstream accepts to break systems with graphical chips > without DRM support: https://github.com/systemd/systemd/pull/20070 So this was finally accepted and merged for v249. I queued the fix for v248, so we should be good now (since for SLE we reverted the change that caused the regressions). Closing, thanks all for your feedback. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1137203] [Build 20190602] openQA test fails in tk
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1137203 https://bugzilla.suse.com/show_bug.cgi?id=1137203#c29 --- Comment #29 from Reinhard Max <max(a)suse.com> --- I finally got to reproduce it after changing the graphics device from virtio-gpu-pci to qxl-vga in runqemu.nokvm. The problem is that in this case the X server reports a zero sized screen and consequently a practically infinite screen resolution which can be seen in the output of xdpyinfo: --- snip --- screen #0: dimensions: 1024x768 pixels (0x0 millimeters) resolution: 2147483647x2147483647 dots per inch --- snap --- Tk uses this information to initialize the scaling factor for translating between points and pixels which in turn is used for rendering fonts if their size is specified in points. This value can be queried by interactively running the "tk scaling" command in wish, and it can be changed by adding a value, e.g. "tk scaling 1.25". In X sessions having the absurd screen size values shown above, "tk scaling" gets initialized as infinity (Inf), resulting in the font's pixel size to be divided down to zero and hence the text isn't visible. As this test is meant to test if Tk works rather than looking for bugs in the underlaying X server, I suggest to set the scaling factor to a useful value (e.g. 1.0) at the beginning of the script, bevore creating any widgets. To check if the X server reports a reasonable screen size and resolution, a separate test could be added that parses the output of xdpyinfo and fails if the values don't look useful. Not sure who would be the right assignee for this bug at this point, but it is definitely not a bug in Tk. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187536] [Build O.91.1] yast can't handle "MOTD_FILE <blank>" in login.defs
by bugzilla_noreply＠suse.com 07 Jul '21

07 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187536 https://bugzilla.suse.com/show_bug.cgi?id=1187536#c8 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |felix.niederwanger(a)suse.com --- Comment #8 from Thorsten Kukuk <kukuk(a)suse.com> --- *** Bug 1188075 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