August 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1165780] New: Reduce the number of PID1 reloading triggered by btrfsmaintenance units
by bugzilla_noreply＠novell.com 29 May '22

29 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1165780 Bug ID: 1165780 Summary: Reduce the number of PID1 reloading triggered by btrfsmaintenance units Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Apparently when btrfsmaintenance package is installed, the number of PID1 reloading increases from 0 to 4. Reloading PID1 is a quite expensive operation therefore it would be nice if this number could be reduced at its minimum and thus helping improving the boot process. Please note that enabling or disabling a unit implies a reload of PID1. If a batch of units needs to be enabled/disabled, it would be better to reload PID1 only at the end of the whole operation (see systemctl "--no-reload" option). For the context: this has been noticed in bnc#1137373, where the batch of PID1 reloading triggered by btrfsmaintenance makes a systemd race easier to happen. -- You are receiving this mail because: You are on the CC list for the bug.

2 112

[Bug 1156920] New: latest wpa_supplicant seems broken (2.9-1.1)
by bugzilla_noreply＠novell.com 26 May '22

26 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1156920 Bug ID: 1156920 Summary: latest wpa_supplicant seems broken (2.9-1.1) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: roger.whittaker(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Unable to connect to wireless with wpa_supplicant-2.9-1.1.x86_64. Downgrade to wpa_supplicant-2.6-9.1.x86_64.rpm solved the problem. With 2.9-1.1, in /var/log/wpa_supplicant.log 1573837618.431976: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837618.512991: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837619.360496: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837619.431234: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837622.973427: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837623.047145: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837624.903588: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837624.987293: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837624.987338: wlp59s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="rogeroffice" auth_failures=1 duration=10 reason=CONN_FAILED 1573837634.854847: wlp59s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="rogeroffice" 1573837634.854985: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837634.935453: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837634.935488: wlp59s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="rogeroffice" auth_failures=2 duration=20 reason=CONN_FAILED 1573837636.533619: wlp59s0: Reject scan trigger since one is already pending 1573837729.947335: nl80211: deinit ifname=p2p-dev-wlp59s0 disabled_11b_rates=0 1573837730.103068: nl80211: deinit ifname=wlp59s0 disabled_11b_rates=0 After downgrade: 1573839996.915081: wlp59s0: Trying to associate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573839996.973165: wlp59s0: Associated with e4:95:6e:40:df:9d 1573839996.990751: wlp59s0: WPA: Key negotiation completed with e4:95:6e:40:df:9d [PTK=CCMP GTK=CCMP] 1573839996.990876: wlp59s0: CTRL-EVENT-CONNECTED - Connection to e4:95:6e:40:df:9d completed [id=0 id_str=] -- You are receiving this mail because: You are on the CC list for the bug.

2 23

[Bug 1161264] New: ignition, /root and installing ssh key
by bugzilla_noreply＠novell.com 24 May '22

24 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1161264 Bug ID: 1161264 Summary: ignition, /root and installing ssh key Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: iforster(a)suse.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com Found By: --- Blocker: --- We have a chicken/egg problem with ignition and installing a root ssh key on a transactional-update system: /root is not mounted in initrd, you need to add an entry in the ignition config to mount /root. To do that, you need to know the device name. Which leads to two problems: 1. I don't know the device name upfront, I need to login first. But's that's not possible without working ignition config. 2. The device name varies on different machines. So you need an extra config/usb disk for every different machine. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1116084] New: Auto-mounting encrypted external disk requires root password
by bugzilla_noreply＠novell.com 22 May '22

22 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1116084 Bug ID: 1116084 Summary: Auto-mounting encrypted external disk requires root password Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: opensuserg(a)thefifthcontinent.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Operating System: openSUSE Tumbleweed 20181110 KDE Plasma Version: 5.14.3 Qt Version: 5.11.2 KDE Frameworks Version: 5.51.0 Kernel Version: 4.18.15-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz Memory: 7.7 GiB of RAM When auto-mounting an encrypted USB drive, it asks for the encryption password and if that is correct, it asks for the root password to perform the mount. When manually mounting the same drives, the root password is not required. This is the expected behaviour. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1084909] New: trackerbug: packages do not build reproducibly from hostname
by bugzilla_noreply＠novell.com 20 May '22

20 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1084909 Bug ID: 1084909 Summary: trackerbug: packages do not build reproducibly from hostname Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All 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 Blocks: 1081754 Found By: Development Blocker: --- When packages include the name of the build host it results in binaries that differ on every build (because the OBS scheduler chooses a random host) It thus triggers rebuilds of depending packages. Those are then 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 2

[Bug 1006815] New: [Build 20161024] yast2 nfs-client does not mount added export
by bugzilla_noreply＠novell.com 20 May '22

20 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1006815 Bug ID: 1006815 Summary: [Build 20161024] yast2 nfs-client does not mount added export Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jpupava(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 699166 --> http://bugzilla.suse.com/attachment.cgi?id=699166&action=edit y2logs ### observed nfs client does not mount added export, nfs client configuration is ok and the export is added in fstab, nfs client service is running but export is not mounted https://openqa.opensuse.org/tests/289982#step/yast2_nfs_client/14 ### workaround mount -a does mount nfs export ### expected added export should be also mounted linux-2cg7:~ # systemctl status nfs-client.target ● nfs-client.target - NFS client services Loaded: loaded (/usr/lib/systemd/system/nfs-client.target; disabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/nfs-client.target.d └─nfs.conf Active: active since Tue 2016-10-25 09:36:52 EDT; 36s ago Oct 25 09:36:52 linux-2cg7 systemd[1]: Reached target NFS client services. linux-2cg7:~ # linux-2cg7:~ # systemctl show nfs.service --property=Id --property=MainPID --property=Description --property=LoadState --property=ActiveState --property=SubState --property=UnitFileState --property=FragmentPath MainPID=0 Id=nfs.service Description=Alias for NFS client LoadState=loaded ActiveState=active SubState=exited FragmentPath=/usr/lib/systemd/system/nfs.service UnitFileState=enabled linux-2cg7:~ # mount|grep nfs sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) linux-2cg7:~ # linux-2cg7:~ # grep nfs /etc/fstab localhost:/tmp/nfs/server /tmp/nfs/client nfs defaults 0 0 linux-2cg7:~ # linux-2cg7:~ # mount -a linux-2cg7:~ # mount|grep nfs sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) localhost:/tmp/nfs/server on /tmp/nfs/client type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=::1,local_lock=none,addr=::1) linux-2cg7:~ # -- You are receiving this mail because: You are on the CC list for the bug.

2 41

[Bug 1096916] New: enlightenment_askpass causes X crash
by bugzilla_noreply＠novell.com 18 May '22

18 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1096916 Bug ID: 1096916 Summary: enlightenment_askpass causes X crash Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: nmoreychaisemartin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 773412 --> http://bugzilla.suse.com/attachment.cgi?id=773412&action=edit Full log Running on an updated Leap 15.0 $ rpm -q libecore1 libeina1 enlightenment libelementary1 libeo1 libevas1 libecore1-1.20.7-lp150.5.9.x86_64 libeina1-1.20.7-lp150.5.9.x86_64 enlightenment-0.22.3-lp150.2.1.x86_64 libelementary1-1.20.7-lp150.5.9.x86_64 libeo1-1.20.7-lp150.5.9.x86_64 libevas1-1.20.7-lp150.5.9.x86_64 Running enlightenment_askpass works fine. But when started through git imap-send this happens: git format-patch -M --to linux-rdma(a)vger.kernel.org --subject-prefix="PATCH rdma-core" --stdout origin/master | git imap-send ERR<14561>:ecore_evas modules/ecore_evas/engines/wayland/ecore_evas_wayland_common.c:2340 _ecore_evas_wl_common_new_internal() Failed to connect to Wayland Display (null) ## Copy & Paste the below (until EOF) into a terminal, then hit Enter eina_btlog << EOF /usr/lib64/libeina.so.1 0x7fd5b5af523c 0x7fd5b5acc000 /usr/lib64/libeina.so.1 0x7fd5b5af5f61 0x7fd5b5acc000 /usr/lib64/libeina.so.1 0x7fd5b5af7333 0x7fd5b5acc000 /usr/lib64/ecore_evas/engines/wayland/v-1.20/module.so 0x7fd5a814577a 0x7fd5a813d000 /usr/lib64/ecore_evas/engines/wayland/v-1.20/module.so 0x7fd5a81457f7 0x7fd5a813d000 /usr/lib64/libecore_evas.so.1 0x7fd5b6a9b397 0x7fd5b6a84000 /usr/lib64/libelementary.so.1 0x7fd5b93d7c13 0x7fd5b914c000 /usr/lib64/libelementary.so.1 0x7fd5b93d89f0 0x7fd5b914c000 /usr/lib64/libeo.so.1 0x7fd5b5f8e95e 0x7fd5b5f7e000 /usr/lib64/libeo.so.1 0x7fd5b5f86ffc 0x7fd5b5f7e000 /usr/lib64/libelementary.so.1 0x7fd5b93d26c2 0x7fd5b914c000 /usr/bin/enlightenment_askpass 0x55aa25b146cf 0x55aa25b13000 /usr/bin/enlightenment_askpass 0x55aa25b144dc 0x55aa25b13000 /lib64/libc.so.6 0x7fd5b86ddf4a 0x7fd5b86bd000 /usr/bin/enlightenment_askpass 0x55aa25b1451a 0x55aa25b13000 EOF Full error log attached. Note: This worked fined in Leap 42.3 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1174581] New: %cmake uses absolute path for CMAKE_INSTALL_LIBDIR
by bugzilla_noreply＠suse.com 17 May '22

17 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1174581 Bug ID: 1174581 Summary: %cmake uses absolute path for CMAKE_INSTALL_LIBDIR Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: simonf.lees(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- According to https://cmake.org/cmake/help/latest/module/GNUInstallDirs.html: > LIBDIR object code libraries (lib or lib64 or lib/<multiarch-tuple> on Debian) It is meant to contain the path below CMAKE_INSTALL_PREFIX, but currently %cmake sets it to %{_libdir}, which evaluates to /usr/lib64. This breaks several projects which use any variation of ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_LIBDIR} or libdir=$prefix/${CMAKE_INSTALL_LIBDIR} to generate .pc files. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 993885] New: Kde-Live net installer does not reboot after installation
by bugzilla_noreply＠novell.com 17 May '22

17 May '22

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.

2 31

[Bug 1097779] New: VUL-0: CVE-2018-12434: LibreSSL before 2.6.5 and 2.7.x before 2.7.4 allows a memory-cache side-channelattack on DSA and ECDSA signatures, aka the Return Of the Hidden Number Problemor ROHNP. To discover a key, the attacker needs access to
by bugzilla_noreply＠novell.com 16 May '22

16 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1097779 Bug ID: 1097779 Summary: VUL-0: CVE-2018-12434: LibreSSL before 2.6.5 and 2.7.x before 2.7.4 allows a memory-cache side-channelattack on DSA and ECDSA signatures, aka the Return Of the Hidden Number Problemor ROHNP. To discover a key, the attacker needs access to Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/208302/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: jengelh(a)inai.de Reporter: meissner(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2018-12434 LibreSSL before 2.6.5 and 2.7.x before 2.7.4 allows a memory-cache side-channel attack on DSA and ECDSA signatures, aka the Return Of the Hidden Number Problem or ROHNP. To discover a key, the attacker needs access to either the local machine or a different virtual machine on the same physical host. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-12434 https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.7.4-relnotes.txt https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.6.5-relnotes.txt -- You are receiving this mail because: You are on the CC list for the bug.

2 1