openSUSE Bugs February 2021

bugs@lists.opensuse.org

1 participants
2659 discussions

[Bug 1177695] New: kernel: parport_pc: `none' invalid for parameter `dma' on openSUSE MicroOS

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1177695 Bug ID: 1177695 Summary: kernel: parport_pc: `none' invalid for parameter `dma' on openSUSE MicroOS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: jalausuch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 842620 --> https://bugzilla.suse.com/attachment.cgi?id=842620&action=edit full journal openSUSE MicroOS DVD image for Leap 15.2 in UEFI boot fails with message > kernel: parport_pc: `none' invalid for parameter `dma' https://openqa.opensuse.org/tests/1432542#step/journal_check/11 -- You are receiving this mail because: You are on the CC list for the bug.

11 hours, 35 minutes

[Bug 1172267] New: OpenSSL 3.0.0 upgrade tracker bug

by bugzilla_noreply＠suse.com

http://bugzilla.suse.com/show_bug.cgi?id=1172267 Bug ID: 1172267 Summary: OpenSSL 3.0.0 upgrade tracker bug Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: vcizek(a)suse.com Reporter: vcizek(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jsikes(a)suse.com, meissner(a)suse.com, pmonrealgonzalez(a)suse.com Found By: --- Blocker: --- This bug collects the challenges and packages that need to be adapted for OpenSSL 3.0.0 upgrade. Major changes in 3.0.0: * OpenSSL 3.0 is a major release and consequently any application that currently uses an older version of OpenSSL will at the very least need to be recompiled in order to work with the new version. * The OpenSSL versioning scheme has changed with the 3.0 release to format: MAJOR.MINOR.PATCH The patch level is indicated by the third number instead of a letter * Providers and FIPS support Providers collect together and make available algorithm implementations. * Use of the low level APIs have been deprecated. * Some cryptographic algorithms that were available via the EVP APIs are now considered legacy and their use is strongly discouraged. * Engines and "METHOD" APIs are deprecated and shall be transformed to providers Detailed list of changes since 1.1.1: https://www.openssl.org/news/changelog.html#openssl-30 The final release is planned for 2020 early Q4. https://www.openssl.org/policies/releasestrat.html OpenSSL 3.0.0 wiki: https://wiki.openssl.org/index.php/OpenSSL_3.0 Design changes in 3.0.0: https://www.openssl.org/docs/OpenSSL300Design.html -- You are receiving this mail because: You are on the CC list for the bug.

18 hours, 31 minutes

[Bug 1102408] New: trackerbug: packages do not build reproducibly from race conditions

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1102408 Bug ID: 1102408 Summary: trackerbug: packages do not build reproducibly from race conditions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Depends on: 1021335, 1021353 Blocks: 1081754 Found By: Development Blocker: --- See also https://reproducible-builds.org/ and https://github.com/bmwiedemann/theunreproduciblepackage/tree/master/race When packages build with make -j$N (N>1), it sometimes results in binaries that differ between builds and thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. Build results can also be incorrect due to races. Often it is possible to fix races by adding proper dependencies between build targets (e.g. https://bugzilla.sudo.ws/show_bug.cgi?id=842 ) or fixing involved racy tools -- You are receiving this mail because: You are on the CC list for the bug.

20 hours, 22 minutes

[Bug 1181316] New: yast2 fails to remember window size and position

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1181316 Bug ID: 1181316 Summary: yast2 fails to remember window size and position Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: devguy.ca(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I have gone into the windows and application setting to tell yast2 to remember position and size and the app doesn't save this info. Even the new added properties fail to save. I honestly think by default all window size and position should be maintained between invocations. -- You are receiving this mail because: You are on the CC list for the bug.

2 days, 8 hours

[Bug 1101735] New: 40grub2: debug messages

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1101735 Bug ID: 1101735 Summary: 40grub2: debug messages Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: novell(a)howorth.org.uk QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- there are a lot of messages in /var/log/messages that start with 40grub2: debug: parsing: Why are they there and how do I get them to stop? PS Why is openSUSE Leap 15.0 not in the list of OS? -- You are receiving this mail because: You are on the CC list for the bug.

2 days, 17 hours

[Bug 993885] New: Kde-Live net installer does not reboot after installation

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=993885 Bug ID: 993885 Summary: Kde-Live net installer does not reboot after installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium Assignee: fvogt(a)suse.com Reporter: okurz(a)suse.com QA Contact: okurz(a)suse.com Found By: --- Blocker: --- ## observation Continuing through the whole installation process of the NET installer on the Kde-Live medium until the "reboot now" dialog shows up works fine but the reboot does not seem to happen ## steps to reproduce I am in the process of automating this but it can be as easy as * start Kde-Live * call installation from within plasma session * let installer run into "reboot now" action * observe that the system does not reboot ## expected result system should reboot into installed system ## workaround manual reboot of the system yields a properly setup Tumbleweed installation so the installation is ok. -- You are receiving this mail because: You are on the CC list for the bug.

3 days, 4 hours

[Bug 1033081] New: fetchmail hardcoded to use log file - syslogging thus unavailable

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=1033081 Bug ID: 1033081 Summary: fetchmail hardcoded to use log file - syslogging thus unavailable Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jmozdzen(a)nde.ag QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- :~ # rpm -qi fetchmail Name : fetchmail Version : 6.3.26 Release : 18.1 Architecture: x86_64 Looking at fetchmail.service -> /usr/lib/fetchmail-systemd-exec, I see that using logging to log file is hard-coded there: --- cut here: /usr/lib/fetchmail-systemd-exec --- [...] exec /usr/bin/fetchmail $OPTS $FETCHMAIL_EXPERT_OPTIONS \ -f $FETCHMAIL_RC_PATH -L /var/log/fetchmail --- cut here --- Hence, activating logging to syslog via options doesn't work: --- cut here --- :~ # grep syslog /etc/fetchmailrc set syslog :~ # systemctl restart fetchmail :~ # 2017-04-09T17:36:13.480966+02:00 myhost fetchmail[4441]: syslog and logfile options are both set, ignoring syslog, and logging to /var/log/fetchmail --- cut here --- A possible change would be to move "-L /var/log/fetchmail" to /etc/sysconfig/fetchmail (i.e. to FETCHMAIL_EXPERT_OPTIONS variable, or a new one). -- You are receiving this mail because: You are on the CC list for the bug.

3 days, 12 hours

[Bug 1105282] New: vc4 not working in linuxrc because of PCM

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=1105282 Bug ID: 1105282 Summary: vc4 not working in linuxrc because of PCM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: afaerber(a)suse.com Reporter: agraf(a)suse.com QA Contact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com, snwint(a)suse.com, tzimmermann(a)suse.com Found By: --- Blocker: --- When I boot up the current Tumbleweed installer system on the Raspberry Pi, HDMI output is not showing. This is related to the vc4 driver being unable to properly load: [ 17.735109] vc4_hdmi 3f902000.hdmi: Could not register PCM component: -517 [ 17.742312] vc4-drm soc:gpu: failed to bind 3f902000.hdmi (ops vc4_hdmi_ops [vc4]): -517 [ 17.750679] vc4-drm soc:gpu: master bind failed: -517 I think there are 2 bugs here really: The first one is with vc4. It shouldn't declare itself as viable graphics output driver (kicking out the well working efifb one) when it can not find all of its dependencies. The other one is that we probably need to include snd_pcm and snd_soc_core in the linuxrc initrd so that vc4 does load properly and allows us to install: rpi31:~ # lsmod | grep -i snd snd_soc_core 237568 1 vc4 snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 151552 3 vc4,snd_pcm_dmaengine,snd_soc_core snd_timer 36864 1 snd_pcm snd 106496 3 snd_timer,snd_soc_core,snd_pcm soundcore 20480 1 snd I'll leave it to Andreas to determine who to assign this bug to and thus which path of the 2 to fix this we should take ;). -- You are receiving this mail because: You are on the CC list for the bug.

4 days

[Bug 1178257] New: rpm-build-python needs setuptools but cannot require on it

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1178257 Bug ID: 1178257 Summary: rpm-build-python needs setuptools but cannot require on it Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: code(a)bnavigator.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Some packages can build without python-setuptools and thus do not depend on it. In this case /usr/lib/rpm/pythondistdeps.py fails in rpm packaging phase: [ 17s] Traceback (most recent call last): [ 17s] File "/usr/lib/rpm/pythondistdeps.py", line 105, in <module> [ 17s] from pkg_resources import Distribution, FileMetadata, PathMetadata, Requirement [ 17s] ModuleNotFoundError: No module named 'pkg_resources' But rpm-build-python depending on python-setuptools is not possible, because that would create a dependency loop with setuptools and its build dependencies (python-ordered-set) -- You are receiving this mail because: You are on the CC list for the bug.

4 days, 6 hours

[Bug 1161823] New: Adding compress=zstd in fstab option in YaST2 on / partition result in "compression type 0x3 not supported"

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1161823 Bug ID: 1161823 Summary: Adding compress=zstd in fstab option in YaST2 on / partition result in "compression type 0x3 not supported" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: andythe_great(a)pm.me QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 828281 --> http://bugzilla.opensuse.org/attachment.cgi?id=828281&action=edit Step 1 of installation When installing OpenSUSE TW, by adding compress=zstd in fstab arbitrary option value will result in broken grub "compression type 0x3 not supported" even it grub already support zstd compression on btrfs. Or maybe I did something wrong. Installation process photos were attached. -- You are receiving this mail because: You are on the CC list for the bug.

4 days, 11 hours

Jump to page:

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs February 2021