July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1144506] New: sphinx-build requires python-attrs to run but does not require it
by bugzilla_noreply＠novell.com 14 Dec '22

14 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1144506 Bug ID: 1144506 Summary: sphinx-build requires python-attrs to run but does not require it 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: dcermak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The sphinxcontrib-autopgrogram and sphinxcontrib-asyncio packages started to fail to build on OBS with the following error: [ 43s] + sphinx-build -b html -d doc/_build/doctrees doc doc/_build/html [ 43s] Traceback (most recent call last): [ 43s] File "/usr/bin/sphinx-build", line 6, in <module> [ 43s] from pkg_resources import load_entry_point [ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3241, in <module> [ 43s] @_call_aside [ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3225, in _call_aside [ 43s] f(*args, **kwargs) [ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3254, in _initialize_master_working_set [ 43s] working_set = WorkingSet._build_master() [ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 583, in _build_master [ 43s] ws.require(__requires__) [ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 900, in require [ 43s] needed = self.resolve(parse_requirements(requirements)) [ 43s] File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 786, in resolve [ 43s] raise DistributionNotFound(req, requirers) [ 43s] pkg_resources.DistributionNotFound: The 'attrs' distribution was not found and is required by packaging [ 43s] error: Bad exit status from /var/tmp/rpm-tmp.tYlY4G (%build) Both invoke sphinx-build during %build. For some reason sphinx-build appears to require python-attrs now, but this is not reflected in the rpm. Thus OBS does not know about this dependency and leaves out python-attrs out of the buildroot (thereby causing the above error). Affected packages: - https://build.opensuse.org/package/show/devel:languages:python/python-sphin… - https://build.opensuse.org/package/show/devel:languages:python/python-sphin… -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 1111657] New: python-cffi build fail with glibc maintenance update
by bugzilla_noreply＠novell.com 14 Dec '22

14 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1111657 Bug ID: 1111657 Summary: python-cffi build fail with glibc maintenance update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With glibc maintenance update https://build.opensuse.org/request/show/639803 , python-cffi build failed due to it can not pass unittest[1]. Both package are from SLE. [1] https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.1:Stagin… -- You are receiving this mail because: You are on the CC list for the bug.

2 31

[Bug 1177900] New: openSUSE Tumbleweed: Boot from Live ISO - only emergency mode
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177900 Bug ID: 1177900 Summary: openSUSE Tumbleweed: Boot from Live ISO - only emergency mode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Live Medium Assignee: dimstar(a)opensuse.org Reporter: adrian.feliks(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0 Build Identifier: All Tumbleweed versions do not start when booting from the ISO image by Grub2 ("iso-scan/filename=$iso_path") Stuck in Emergency Mode. I tested on my laptop and in QEMU (EFI and bios). Last time it was ok. openSUSE Leap 15.2 boots correctly. openSUSE-Tumbleweed-*-Live-x86_64-Snapshot20201014-Media.iso openSUSE-Tumbleweed-Rescue-CD-x86_64-Snapshot20201014-Media.iso Grub config file: https://github.com/Mexit/MultiOS-USB/blob/master/config/openSUSE/openSUSE-L… Reproducible: Always Actual Results: Stuck in Emergency Mode Expected Results: Starts to the desktop I attach a screenshot and rdsosreport.txt -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1201502] New: Segmentation fault in libfabric in fi_rdm_atomic
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1201502 Bug ID: 1201502 Summary: Segmentation fault in libfabric in fi_rdm_atomic Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mmoese(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860174 --> https://bugzilla.suse.com/attachment.cgi?id=860174&action=edit dmesg output When running fabtest for libfabric I get the following segmentation fault: fi_rdm_atomic:6436 terminated with signal 11 at PC=7f6d3d79b088 SP=7ffd760d0600. Backtrace: /lib64/libfabric.so.1(+0x36088)[0x7f6d3d79b088] /lib64/libfabric.so.1(+0xcb821)[0x7f6d3d830821] /lib64/libfabric.so.1(+0xcc17b)[0x7f6d3d83117b] /lib64/libfabric.so.1(+0xcc2f1)[0x7f6d3d8312f1] /lib64/libfabric.so.1(+0x416bd)[0x7f6d3d7a66bd] /lib64/libfabric.so.1(+0x40b4e)[0x7f6d3d7a5b4e] fi_rdm_atomic(+0x7242)[0x55b25295e242] fi_rdm_atomic(+0x8144)[0x55b25295f144] fi_rdm_atomic(+0x8b3e)[0x55b25295fb3e] fi_rdm_atomic(+0x3a81)[0x55b25295aa81] /lib64/libc.so.6(+0x405b0)[0x7f6d3d5735b0] /lib64/libc.so.6(__libc_start_main+0x8b)[0x7f6d3d573679] fi_rdm_atomic(+0x4a85)[0x55b25295ba85] The hardware used are two Mellanox Connect-X5 with a back to back connection without a switch. Please tell me if you need anything else. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1200234] New: apparmor blocks access of php-fpm to scripts under $HOME/public_html
by bugzilla_noreply＠suse.com 12 Dec '22

12 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200234 Bug ID: 1200234 Summary: apparmor blocks access of php-fpm to scripts under $HOME/public_html Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: d_werner(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After the upgrade from Leap 15.3 to Leap 15.4 a php webpage with scripts located under $HOME/public_html was no longer working. The webserver log said: 2022-06-03 17:55:06: (mod_fastcgi.c.451) FastCGI-stderr:Unable to open primary script: /home/user/public_html/project/index.php (Permission denied) /var/log/audit/audit.log: type=AVC msg=audit(1654271706.674:267): apparmor="DENIED" operation="open" profile="php-fpm" name="/home/user/public_html/project/index.php" pid=2282 comm="php-fpm" requested_mask="r" denied_mask="r" fsuid=473 ouid=1000 Adding read access to scripts in the directory restored the functionality: cat /etc/apparmor.d/local/php-fpm # Site-specific additions and overrides for 'php-fpm' @{HOME}/public_html/**/*.php r, In the release notes of Leap 15.4 I did not find a hint that public_html is deprecated and which directory should be used instead. For Leap 15.3 the access to home directories was restored after applying systemd hardening settings, see bug 1195465. Therefore I think either the apparmor profile should be updated or the release notes should give a recommendation where to move such projects. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1149754] New: Translations are good!
by bugzilla_noreply＠novell.com 12 Dec '22

12 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1149754 Bug ID: 1149754 Summary: Translations are good! Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: snwint(a)suse.com QA Contact: ke(a)suse.com Found By: --- Blocker: --- Weblate creates automated github commits that unfortunately don't align to the usual workflow as there a bugzilla (or jira) reference is required. So I've created this bug to auto-add its number to every Weblate commit message. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1190434] New: crash is unable to find debuginfo of usrmerged kernel
by bugzilla_noreply＠suse.com 12 Dec '22

12 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1190434 Bug ID: 1190434 Summary: crash is unable to find debuginfo of usrmerged kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dmair(a)suse.com, ptesarik(a)suse.com Found By: --- Blocker: --- With a usrmerged kernel, vmlinux(.xz) is in the modules directory for the kernel: /usr/lib/modules/5.14.1-1-default/vmlinux.xz This means the debug info ends up here: /usr/lib/debug/usr/lib/modules/5.14.1-1-default/vmlinux.debug Crash only looks at the old location though, and fails: please wait... (uncompressing /usr/lib/modules/5.14.1-1-default/vmlinux.xz) readmem: read_diskdump() NOTE: gnu_debuglink file: vmlinux.debug crc32: f73ed3b0 /usr/lib/modules/5.14.1-1-default//vmlinux.debug: not readable/found /usr/lib/modules/5.14.1-1-default//.debug/vmlinux.debug: not readable/found /usr/lib/debug/boot/vmlinux.debug: not readable/found crash: /var/tmp/vmlinux.xz_DZPxr5: no debugging data available crash: vmlinux.debug: debuginfo file not found crash: either install the appropriate kernel debuginfo package, or copy vmlinux.debug to this machine -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1189975] New: cleanup: remove or document patches.suse/kbd-ignore-gfx.patch
by bugzilla_noreply＠suse.com 12 Dec '22

12 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1189975 Bug ID: 1189975 Summary: cleanup: remove or document patches.suse/kbd-ignore-gfx.patch Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jeffm(a)suse.com Reporter: jeffm(a)suse.com QA Contact: jeffm(a)suse.com Blocks: 1189946 Found By: --- Blocker: --- This is an automated report to queue a potentially obsolete patch for removal. The patch patches.suse/kbd-ignore-gfx.patch will be removed from the master branch in 30 days if the assignee does not remove it before then. Alternatively, the assignee may update the patch tags and this report to indicate what efforts are being made to land the patch in the upstream kernel or to justify why it should require ongoing maintenance effort. Thank you for your cooperation. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1201421] New: TW 20220710 and later: ibus not working
by bugzilla_noreply＠suse.com 11 Dec '22

11 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 Bug ID: 1201421 Summary: TW 20220710 and later: ibus not working 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: Mathias.Homann(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since TW 20220710 (or possibly earlier) ibus isn't working anymore: - the ibus panel applet is not autostarting - after manually calling ibus-autostart, switching input method stops working after a few switches -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1185201] New: firewalld enhancement
by bugzilla_noreply＠suse.com 11 Dec '22

11 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1185201 Bug ID: 1185201 Summary: firewalld enhancement Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- on a opensuse tumbleweed or leap system i have noticed, that, when you comletely disable ipv6 from yast2 network, firewalld still continues to configure ipv6 rules even though your system isn't using ipv6 could this please be looked at. it just seems strange -- You are receiving this mail because: You are on the CC list for the bug.

1 4