October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1191762] New: [SLPP] libepc: E: shlib-policy-name-error
by bugzilla_noreply＠suse.com 23 May '22

23 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191762 Bug ID: 1191762 Summary: [SLPP] libepc: E: shlib-policy-name-error 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: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following rpmlint error was seen for the package: libepc.log:[ 62s] libepc-1_0-2.x86_64: E: shlib-policy-name-error SONAME: libepc-1.0.so.3, expected package suffix: 1_0-3 libepc.log:[ 62s] libepc-1_0-2.x86_64: E: shlib-policy-name-error SONAME: libepc-ui-1.0.so.3, expected package suffix: 1_0-3 Note the updated rpmlint will reach openSUSE:Factory soon. We would like to make 'shlib-policy-name-error' a package build failure error, so please fix the error. Link to the SLPP documentation: https://en.opensuse.org/openSUSE:Shared_library_packaging_policy#Package_na… -- You are receiving this mail because: You are on the CC list for the bug.

1 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 1192096] New: no keyboard or mouse response in SDDM greeter in 20211025
by bugzilla_noreply＠suse.com 21 May '22

21 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1192096 Bug ID: 1192096 Summary: no keyboard or mouse response in SDDM greeter in 20211025 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: fabian(a)ritter-vogt.de Found By: --- Blocker: --- Original Summary: no keyboard or mouse response in SDDM greeter in 20211025 This followed a normal zypper dup from 20210817 to 20210825. Now I get a pretty login screen that's useless for entering username or password. Switching to tty2 and back doesn't help. Restarting xdm from tty2 doesn't help either. Switching to LightDM worked, but its appeal is sub-zero. I asked about this on support mailing list, but as yet, no response. After isolating multi-user.target, startx succeeds to open a Plasma session. # rpmqa sddm kcm_sddm-5.23.1-1.1.x86_64 sddm-0.19.0-4.2.x86_64 sddm-branding-upstream-0.19.0-4.2.x86_64 # inxi -SMCPmy System: Host: p5bse Kernel: 5.14.14-1-default x86_64 bits: 64 Console: tty pts/0 Distro: openSUSE Tumbleweed 20211025 Machine: Type: Desktop Mobo: ASUSTeK model: P5B SE v: Rev 1.xx serial: MS6C79B32413550 BIOS: American Megatrends v: 1103 date: 06/04/2009 Memory: RAM: total: 3.82 GiB used: 546.5 MiB (14.0%) Array-1: capacity: 8 GiB slots: 4 EC: None Device-1: DIMM_A1 size: 2 GiB speed: 800 MT/s Device-2: DIMM_A2 size: No Module Installed Device-3: DIMM_B1 size: 2 GiB speed: 800 MT/s Device-4: DIMM_B2 size: No Module Installed CPU: Info: Dual Core model: Intel Core2 Duo E7500 bits: 64 type: MCP cache: L2: 3 MiB Speed: 1600 MHz min/max: 1596/2926 MHz Core speeds (MHz): 1: 1600 2: 1600 Partition: ID-1: / size: 6.16 GiB used: 4.43 GiB (71.9%) fs: ext4 dev: /dev/sda24 ID-2: /home size: 4.23 GiB used: 1.27 GiB (30.0%) fs: ext3 dev: /dev/sda9 ID-3: swap-1 size: 1.82 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[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 1191345] New: opendkim segv in libunbound8
by bugzilla_noreply＠suse.com 20 May '22

20 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191345 Bug ID: 1191345 Summary: opendkim segv in libunbound8 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: patrick.schaaf(a)yalwa.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I run two loadbalanced postfix MX servers, both kept kind of up-to-date with tumbleweed. Part of that install, on both of them, is opendkim for mail signing. Setup basically has been running flawlessly for a few years. One system was updated about 40 days ago, to tumbleweed 20210810, which has libunbound8-1.13.1-2.1.x86_64 Today I updated the other one to even newer tumbleweed, 20210929, which brought newerlibunbound8-1.13.2-1.2.x86_64 package. And there, I experienced opendkim hitting a segv, after ~1500 seconds of uptime, restarted it manually, and it ran into a second one at ~3600 seconds of system uptime. The dmesg output, see below, pointed at libunbound8. So I manually force-downgraded just that package to the version that has been running on the partner machine for some days - and the segvs are gone now after several hours. Unfortunately, these are busy mailservers with multiple mails flowing through each second, so I cannot pinpoint / reproduce the segv precisely, and I cannot risk much experimenting on them. I hope this observations can help resolve the issue, anyway. So here's the dmesg output I saw: 2021-10-05T14:02:56.385231+02:00 phobos kernel: [ 1521.425408] opendkim[2552]: segfault at 10 ip 00007fd1f33256aa sp 00007fd1eb7fd640 error 4 in libunbound.so.8. 1.13[7fd1f328c000+cb000] 2021-10-05T14:02:56.385242+02:00 phobos kernel: [ 1521.425422] Code: fc 55 48 89 f5 53 48 83 ec 28 48 8b 9e 20 01 00 00 48 8b 43 10 4c 8b 38 4c 8b 50 08 48 8b 86 30 01 00 00 48 8b 80 b8 00 00 00 <4c> 8b 58 10 48 c7 86 30 01 00 00 00 00 00 00 83 fa fe 0f 84 46 02 ... 2021-10-05T14:38:48.875262+02:00 phobos kernel: [ 3674.051115] opendkim[11676]: segfault at 10 ip 00007f96636696aa sp 00007f965b7fd640 error 4 in libunbound.so.8.1.13[7f96635d0000+cb000] 2021-10-05T14:38:48.875273+02:00 phobos kernel: [ 3674.051128] Code: fc 55 48 89 f5 53 48 83 ec 28 48 8b 9e 20 01 00 00 48 8b 43 10 4c 8b 38 4c 8b 50 08 48 8b 86 30 01 00 00 48 8b 80 b8 00 00 00 <4c> 8b 58 10 48 c7 86 30 01 00 00 00 00 00 00 83 fa fe 0f 84 46 02 -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[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 1190853] New: VUL-1: CVE-2021-41581: x509_constraints_parse_mailbox in lib/libcrypto/x509/x509_constraints.c in LibreSSL through 3.4.0 has a stack-based buffer over-read. When the input exceeds DOMAIN_PART_MAX_LEN, the buffer lacks '\0' termination.
by bugzilla_noreply＠suse.com 19 May '22

19 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1190853 Bug ID: 1190853 Summary: VUL-1: CVE-2021-41581: x509_constraints_parse_mailbox in lib/libcrypto/x509/x509_constraints.c in LibreSSL through 3.4.0 has a stack-based buffer over-read. When the input exceeds DOMAIN_PART_MAX_LEN, the buffer lacks '\0' termination. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other URL: https://smash.suse.de/issue/310834/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: jengelh(a)inai.de Reporter: gabriele.sonnu(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- x509_constraints_parse_mailbox in lib/libcrypto/x509/x509_constraints.c in LibreSSL through 3.4.0 has a stack-based buffer over-read. When the input exceeds DOMAIN_PART_MAX_LEN, the buffer lacks '\0' termination. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-41581 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41581 https://github.com/libressl-portable/openbsd/issues/126 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1191938] New: VUL-1: CVE-2020-27304: civetweb: missing uploaded filepath validation in the default form-based file upload mechanism
by bugzilla_noreply＠suse.com 18 May '22

18 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1191938 Bug ID: 1191938 Summary: VUL-1: CVE-2020-27304: civetweb: missing uploaded filepath validation in the default form-based file upload mechanism Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other URL: https://smash.suse.de/issue/313299/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: axel.braun(a)gmx.de Reporter: gabriele.sonnu(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- The CivetWeb web library does not validate uploaded filepaths when running on an OS other than Windows, when using the built-in HTTP form-based file upload mechanism, via the mg_handle_form_request API. Web applications that use the file upload form handler, and use parts of the user-controlled filename in the output path, are susceptible to directory traversal References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27304 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27304 https://jfrog.com/blog/cve-2020-27304-rce-via-directory-traversal-in-civetw… https://groups.google.com/g/civetweb/c/yPBxNXdGgJQ -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[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 1176214] New: After last updates xfce4-notifyd service did not start
by bugzilla_noreply＠suse.com 18 May '22

18 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1176214 Bug ID: 1176214 Summary: After last updates xfce4-notifyd service did not start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXDE Assignee: andrea(a)opensuse.org Reporter: virex(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After last updates xfce4-notifyd service did not start if i start this service manualy it works (/usr/libexec/xfce4/notifyd/xfce4-notifyd &) -- You are receiving this mail because: You are on the CC list for the bug.

1 7