April 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1116225] New: qemu ALSA backend broken
by bugzilla_noreply＠novell.com 05 Jan '22

05 Jan '22

http://bugzilla.suse.com/show_bug.cgi?id=1116225 Bug ID: 1116225 Summary: qemu ALSA backend broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)forge.provo.novell.com Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It seems that qemu ALSA backend is broken. When I start an audio playback on VM, the whole VM including GUI stalls. Tested qemu 3.0.0 with qemu-audio-alsa package. Switching to PA backend seems working, so this might be specific to the audio backend. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1158152] New: provide ssl profiles by defaults
by bugzilla_noreply＠novell.com 04 Jan '22

04 Jan '22

http://bugzilla.suse.com/show_bug.cgi?id=1158152 Bug ID: 1158152 Summary: provide ssl profiles by defaults Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Apache Assignee: bnc-team-apache(a)forge.provo.novell.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On the openSUSE heroes list I learned about https://ssl-config.mozilla.org/ How about shipping those settings in config files already so the admin can choose without editing configs? -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1164887] New: Leap 15.2 Beta konqueror crash: GStreamer-WARNING External plugin loader failed
by bugzilla_noreply＠novell.com 04 Jan '22

04 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1164887 Bug ID: 1164887 Summary: Leap 15.2 Beta konqueror crash: GStreamer-WARNING External plugin loader failed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: d_werner(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Leap 15.2 Build 589.1 upgraded with zypper dup from current Leap 15.1 the upgrade worked without problems existing user home directory from Leap 15.1 Initially konqueror crashed opening "any" website. When starting konqueror from the command line this is the crash related output it produces: (konqueror:5215): GStreamer-WARNING **: 19:02:55.810: External plugin loader failed. This most likely means that the plugin loader helper binary was not found or could not be run. You might need to set the GST_PLUGIN_SCANNER environment variable if your setup is unusual. This should normally not be required though. KCrash: Application 'konqueror' crashing... I found a binary which looked promising to be the desired plugin scanner: rpm -qf /usr/lib/gstreamer-1.0/gst-plugin-scanner-x86_64 gstreamer-1.16.2-lp152.1.2.x86_64 and set the environment variable as suggested by the error output: GST_PLUGIN_SCANNER=/usr/lib/gstreamer-1.0/gst-plugin-scanner-x86_64 konqueror Now konqueror is able to open websites without crashing. And - after successfully starting konqueror with this setting from the command line once it also is able to browse websites when started again (no instance running in the background) from the startmenu or from the command line without the environment variable, seems like the setting sticks somewhere now. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1060506] New: libkolabxml packages differ for every build
by bugzilla_noreply＠novell.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1060506 Bug ID: 1060506 Summary: libkolabxml packages differ for every build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: lbeltrame(a)kde.org Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matthias(a)mailaender.name Found By: Development Blocker: --- When working on the reproducible builds project for openSUSE I found that libkolabxml packages differ for every build unless ASLR is disabled in the build system. This indicates either usage of unitinialized memory (compare [1]) or using (randomized) pointers in output. /usr/lib64/libkolabxml.so.1.1.6 differs because of /home/abuild/rpmbuild/BUILD/libkolabxml-1.1.6/build/kolabformat-xcal-schema.cxx 2018-10-30 08:42:53.622040000 +0000 @@ -9014,9 +9014,9 @@ 0x00, 0x01, 0x6d, 0x09, 0x00, 0x01, 0x3f, 0x07, 0x00, 0x01, 0x23, 0x07, 0x00, 0x01, 0x53, 0x0a, 0x00, 0x01, 0x68, 0x07, 0x00, 0x01, 0x7f, 0x09, 0x00, 0x01, 0x4e, 0x04, 0x00, 0x01, 0xfe, 0xff, 0xff, 0xff, 0x1d, 0x00, - 0x06, 0x0e, 0x00, 0x06, 0xe8, 0x08, 0x00, 0x01, 0xff, 0xff, 0xff, 0xff, + 0x06, 0x0e, 0x00, 0x06, 0x25, 0x07, 0x00, 0x01, 0xff, 0xff, 0xff, 0xff, 0x00, 0x03, 0x0c, 0x00, 0x06, 0x58, 0x53, 0x41, 0x6e, 0x6e, 0x6f, 0x74, - 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x00, 0x03, 0x11, 0x09, 0x00, 0x05, 0x3c, + 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x00, 0x03, 0xb6, 0x01, 0x00, 0x05, 0x3c, 0x00, 0xff, 0x78, 0x73, 0x3a, 0x61, 0x6e, 0x6e, 0x6f, 0x74, 0x61, 0x74, [...] which probably comes from # Compile Schemas add_custom_command(OUTPUT kolabformat-xcal-schema.cxx COMMAND ${XSDBIN} --verbose --array-name iCalendar_schema --output-dir ${CMAKE_BINARY_DIR} ${SCHEMAS} which might be from ./compiled/xsdbin.cxx and/or involving the xsd package [1] https://build.opensuse.org/package/view_file/M17N/gcin/gcin-reproducible.pa… -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1155938] New: System crash caused by i915 driver
by bugzilla_noreply＠novell.com 03 Jan '22

03 Jan '22

http://bugzilla.suse.com/show_bug.cgi?id=1155938 Bug ID: 1155938 Summary: System crash caused by i915 driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: martin.doucha(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 823409 --> http://bugzilla.suse.com/attachment.cgi?id=823409&action=edit kernel log of the crash My laptop repeatedly crashes because of bug in i915 driver. My HW setup: - Dell Latitued 7490 - Dell Dock WD15 docking station - 2 monitors connected to docking station (1 via DisplayPort, 1 via HDMI-to-DVI adapter) Events leading up to the crash: At 15:30:39 (according to the log), my laptop lost connection to the network adapter in the docking station (but not the whole docking station). At 15:30:45, I've disconnected the docking station cable and plugged it back in to reset the network adapter. This also disconnected both external monitors and they didn't turn back on after reconnecting the docking station. Instead, the system froze and the Caps Lock LED started flashing. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1166743] New: /etc/subuid and /etc/subgid entries are not created for yast created users, unlike useradd
by bugzilla_noreply＠novell.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1166743 Bug ID: 1166743 Summary: /etc/subuid and /etc/subgid entries are not created for yast created users, unlike useradd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: katharine.chui(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Installation image used: openSUSE-Tumbleweed-DVD-x86_64-Snapshot20200312-Media.iso /etc/subuid and /etc/subgid entries are required for non privileged podman to work as described in https://bugzilla.opensuse.org/show_bug.cgi?id=1137059 However users added with yast2 during install and after install lacks the required entries Meanwhile, command line utility `useradd` creates those entries, introducing inconsistency Steps to reproduce: 1. Install openSuse Tumbleweed, creating the first user `with_installer` 2. `with_installer:100000:65536` should be added to /etc/subuid and /etc/subgid after installation, however that is currently not the observed behavior 3. Create a new user `with_yast` with YaST2, `with_yast:100000:65536` should be added to /etc/subuid and /etc/subgid, however that is currently not the observed behavior 4. Create a new user with `useradd -m new_user`, /etc/subuid and /etc/subgid is created with entry `new_user:100000:65536` Workaround for non privileged podman with YaST2 created users: add line `USERNAME:100000:65536` to /etc/subuid and /etc/subgid -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1061219] New: trackerbug: packages do not build reproducibly from including uninitialized memory
by bugzilla_noreply＠novell.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1061219 Bug ID: 1061219 Summary: trackerbug: packages do not build reproducibly from including uninitialized memory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Other Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- See also https://reproducible-builds.org/ When packages write uninitialized memory into files that are packaged it results in binaries that differ on every build. These thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1101756] New: enable specification of custom GRUB_DISTRIBUTOR= in UEFI bootloader installation
by bugzilla_noreply＠novell.com 31 Dec '21

31 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1101756 Bug ID: 1101756 Summary: enable specification of custom GRUB_DISTRIBUTOR= in UEFI bootloader installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 777382 --> http://bugzilla.opensuse.org/attachment.cgi?id=777382&action=edit 15.0 y2logs from host ab250 YaST2 currently offers no opportunity to specify a custom name to facilitate multiboot hosts. It needs one. Because it does not, e.g. when installation of Leap follows installation of Tumbleweed, the previous UEFI configuration is destroyed. The BIOS boot manager may or may not accommodate a proper selection of the preferred choice from the EFI/ESP partition. In the Leap follows TW case I just tried with an Asus B250M-C/CSM Kaby Lake motherboard with AMI BIOS version 1205 of 2018-05-11, the BIOS did not. As I normally do during installation, I deselected probe foreign OS. In attempting to avoid this overwrite, during installation of 15.0 I used vi to edit /mnt/etc/default/grub to include GRUB_DISTRIBUTOR="opensuse150". Actual bootloader installation at the end of overall installation changed it to GRUB_DISTRIBUTOR=, with the result that next boot only offered 15.0 to the exclusion of TW's /boot/grub2/custom.cfg which contains the custom stanzas for the other installed distros. I was forced to "choose" only 15.0 at next boot. I did work around that by using e on the 15.0 stanza to specify the TW kernel and initrd. Current EFI boot configuration: # efibootmgr BootCurrent: 0000 BootOrder: 0000,0001,0002 Boot0000* opensuse Boot0001* debian Boot0002* UEFI OS Expected EFI boot configuration subsequent to 15.0 installation was: # efibootmgr BootCurrent: 0000 BootOrder: 0000,0001,0002,0003,0004 Boot0000* opensuseTW Boot0001* debian Boot0002* ubuntu Boot0003* opensuse150 Boot0004* UEFI OS -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1109968] New: Daisy chained DisplayPort v1.2 screens randomly doesn't resume
by bugzilla_noreply＠novell.com 31 Dec '21

31 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1109968 Bug ID: 1109968 Summary: Daisy chained DisplayPort v1.2 screens randomly doesn't resume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: jkohoutek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When resuming from blank power saving, sometimes some of the displays connected trough Daisy chained DisplayPort v1.2 doesn't resume. Which one of the display doesn't wake up is random. GPU: Intel® HD Graphics 520 (Skylake GT2) Displays: 2x 1920x1080 Dell U2414H -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1060111] New: bash: have: command not found
by bugzilla_noreply＠novell.com 30 Dec '21

30 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1060111 Bug ID: 1060111 Summary: bash: have: command not found Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: matthias(a)mailaender.name QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just encountered this in openSUSE Tumbleweed where every terminal displays > bash: have: command not found upon startup. http://www.jerous.org/2016/09/19/bash-have-not-found describes the problem and proposes a solution. I don't know if it is the correct approach. -- You are receiving this mail because: You are on the CC list for the bug.

2 10