May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 1159840] New: chrony is build failed in Leap 15.2
by bugzilla_noreply＠novell.com 22 Dec '21

22 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1159840 Bug ID: 1159840 Summary: chrony is build failed in Leap 15.2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: max(a)suse.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- chrony is build failed in Leap 15.2, the full build log can be found at https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.2:Rings:… it fails to pass pre-testing stage: [ 51s] Testing addrfilt PASS [ 51s] Testing clientlog PASS [ 52s] Testing hwclock PASS [ 54s] Testing keys PASS [ 54s] Testing ntp_core PASS [ 54s] Testing ntp_sources PASS [ 55s] Testing regress PASS [ 55s] Testing smooth PASS [ 55s] Testing sources PASS [ 55s] Testing util FAIL (on line 46) [ 55s] make[1]: *** [Makefile:26: check] Error 1 chrony is SLE package, assign to SLE maintainer. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1144316] New: VUL-1: CVE-2019-1010301: jhead: Stack buffer overflow in gpsinfo.c when running jhead
by bugzilla_noreply＠novell.com 22 Dec '21

22 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1144316 Bug ID: 1144316 Summary: VUL-1: CVE-2019-1010301: jhead: Stack buffer overflow in gpsinfo.c when running jhead Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: sbrabec(a)suse.com Reporter: atoptsoglou(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- CVE-2019-1010301 jhead 3.03 is affected by: Buffer Overflow. The impact is: Denial of service. The component is: gpsinfo.c Line 151 ProcessGpsInfo(). The attack vector is: Open a specially crafted JPEG file. References https://bugzilla.redhat.com/show_bug.cgi?id=1679952 https://nvd.nist.gov/vuln/detail/CVE-2019-1010301 http://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-1010301.html -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1136292] New: ktorrent don't find the file "http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz"
by bugzilla_noreply＠novell.com 22 Dec '21

22 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1136292 Bug ID: 1136292 Summary: ktorrent don't find the file "http://geolite.maxmind.com/download/geoip/database/Ge oLiteCountry/GeoIP.dat.gz" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: x3.141592(a)yahoo.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 805988 --> http://bugzilla.opensuse.org/attachment.cgi?id=805988&action=edit ktorrent message Please see the attachment. I get this message when I start ktorrent. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1152964] New: Fetchmail needs an update (from 6.3 to 6.4)
by bugzilla_noreply＠novell.com 19 Dec '21

19 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1152964 Bug ID: 1152964 Summary: Fetchmail needs an update (from 6.3 to 6.4) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bjoernv(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- "On 2019-09-28, fetchmail 6.4.1 has been released (click this link to download, or to see changes since 6.3.26) . Note that you will need OpenSSL 1.0.2 to compile. This is a RECOMMENDED update for all users. Fetchmail 6.3.x versions are discontinued and no longer supported." Source: Fetchmail homepage -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 937067] New: efi=1 does not seem to work anymore
by bugzilla_noreply＠novell.com 17 Dec '21

17 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=937067 Bug ID: 937067 Summary: efi=1 does not seem to work anymore Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: kukuk(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In the past, you could add efi=1 as argument for the installer, and your system was setup for EFI boot, even if the detection fails. This works only partly with Tumbleweed 20150630: the bootloader still installs and configures grub2-x86_64-efi, but the storage proposal does not create a vfat /boot/EFI partition anymore. This works with SLES12, haven't tested openSUSE 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

2 10