July 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213615] New: SuperCollider does not see supercollider-sc3-plugins when installed
by bugzilla_noreply＠suse.com 10 Aug '23

10 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213615 Bug ID: 1213615 Summary: SuperCollider does not see supercollider-sc3-plugins when installed 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: arinlares(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have just installed the supercollider and supercollider-sc3-plugins packages. I installed SuperDirt, a quark that depends on supercollider-sc3-plugins, which could not find parts of this extension. I ran rpm -ql supercollider-sc3-plugins and found they were installed to /usr/share/SuperCollider/SC3plugins/ They should have been installed to /usr/share/SuperCollider/Extensions/SC3Plugins to be found by SuperCollider. I resolved this with a symlink after checking SuperCollider's documentation: sudo ln -s /usr/share/SuperCollider/SC3plugins /usr/share/SuperCollider/Extensions/SC3Plugins This allowed SuperCollider to see the plugins, everything worked as expected afterward. Here's the relevant part of the documentation that mentions where the plugins should be installed: https://doc.sccode.org/Guides/UsingExtensions.html -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213609] New: Yast2 Firewall does not display configured Ports for zone
by bugzilla_noreply＠suse.com 09 Aug '23

09 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213609 Bug ID: 1213609 Summary: Yast2 Firewall does not display configured Ports for zone Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: christian.tallner(a)gmx.de QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Build Identifier: I added TCP Port rules to my home zone in the Yast2 Firewall Configuration. After closing and opening the Firewall Configuration the Port is not visible. when executing "sudo firewall-cmd --list-all-zones" the configured port 8080 is listed though: home (active) target: default ingress-priority: 0 egress-priority: 0 icmp-block-inversion: no interfaces: wlo1 sources: services: dhcpv6-client kdeconnect mdns samba-client ssh ports: 8080/tcp protocols: forward: yes masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Reproducible: Always Steps to Reproduce: 1.Add a new Port rule for a zone in the Yast2 Firewall Configuration 2.Close the Firewall Configuration and restart Yast2 3.Open the Firewall Configuration and inspect the Ports tab of the zone. Actual Results: No Ports are displayed in the ports tab. Expected Results: The added Port should be displayed in the ports tab. It is only possible for me to remove the configured port by using firewall-cmd, You can not do so from the GUI, because it is not displayed. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213277] New: rpm crashes when passed invalid file
by bugzilla_noreply＠suse.com 09 Aug '23

09 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213277 Bug ID: 1213277 Summary: rpm crashes when passed invalid file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: mls(a)suse.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868175 --> https://bugzilla.suse.com/attachment.cgi?id=868175&action=edit _buildenv Run rpm with the attached file: # rpm -Fvh _buildenv Program received signal SIGSEGV, Segmentation fault. I did rpm -Fvh * in a directory created by "osc getbinaries". I know I should've used *.rpm, but rpm should not crash when passed bad files. It looks like it recurses in glob() to death: > #0 0x00007ffff7f0d934 in glob ( > pattern=pattern@entry=0x7fffff81ce80 "didnt move in 1.5h (seen in libreoffice builds) BuildFlags: logidlelimit:5400 %endif %if "%_project" == "openSUSE:Factory" || "%_project" == "openSUSE:Factory:NonFre"..., flags=flags@entry=5152, pglob=pglob@entry=0x7fffffffb5d0, errfunc=0x0) > at /usr/src/debug/rpm-4.18.0/rpmio/rpmglob.c:165 > #1 0x00007ffff7f0e2fc in glob ( > pattern=pattern@entry=0x7fffff83f090 "didnt move in 1.5h (seen in libreoffice builds) BuildFlags: logidlelimit:5400 %endif %if "%_project" == "openSUSE:Factory" || "%_project" == "openSUSE:Factory:NonFre"..., flags=flags@entry=5152, pglob=pglob@entry=0x7fffffffb5d0, errfunc=0x0) > at /usr/src/debug/rpm-4.18.0/rpmio/rpmglob.c:213 > #2 0x00007ffff7f0e2fc in glob ( > pattern=pattern@entry=0x7fffff8612a0 "didnt move in 1.5h (seen in libreoffice builds) BuildFlags: logidlelimit:5400 %endif %if "%_project" == "openSUSE:Factory" || "%_project" == "openSUSE:Factory:NonFre"..., flags=flags@entry=5152, pglob=pglob@entry=0x7fffffffb5d0, errfunc=0x0) > at /usr/src/debug/rpm-4.18.0/rpmio/rpmglob.c:213 > ... > #58 0x00007ffff7f0e2fc in glob ( > pattern=pattern@entry=0x7ffffffd92d0 "didnt move in 1.5h (seen in libreoffice builds) BuildFlags: logidlelimit:5400 %endif %if "%_project" == "openSUSE:Factory" || "%_project" == "openSUSE:Factory:NonFre"..., flags=flags@entry=5152, pglob=pglob@entry=0x7fffffffb5d0, errfunc=0x0) > at /usr/src/debug/rpm-4.18.0/rpmio/rpmglob.c:213 > #59 0x00007ffff7f0e2fc in glob ( > pattern=0x7ffff7596fc4 "didnt move in 1.5h (seen in libreoffice builds) BuildFlags: logidlelimit:5400 %endif %if "%_project" == "openSUSE:Factory" || "%_project" == "openSUSE:Factory:NonFre"..., > flags=flags@entry=5120, pglob=pglob@entry=0x7fffffffb5d0, errfunc=0x0) > at /usr/src/debug/rpm-4.18.0/rpmio/rpmglob.c:213 > #60 0x00007ffff7f0f073 in rpmGlob ( > patterns=patterns@entry=0x7ffff75dd010 "<buildinfo project=\"graphics:gimp:master\" repository=\"openSUSE_Tumbleweed\" package=\"maxflow\"> <arch>x86_64</arch> <srcmd5>59b2ebc06df29ffc1e28e301625e9be2</srcmd5> <verifymd5>59b2ebc06df29ffc1e28e3016"..., argcPtr=argcPtr@entry=0x7fffffffb73c, > argvPtr=argvPtr@entry=0x7fffffffb740) > at /usr/src/debug/rpm-4.18.0/rpmio/rpmglob.c:864 > #61 0x00007ffff7f4b45a in rpmReadPackageManifest (fd=<optimized out>, > argcPtr=0x5555555728e8, argvPtr=0x5555555728f0) > at /usr/src/debug/rpm-4.18.0/lib/manifest.c:121 > #62 0x00007ffff7f667b3 in tryReadManifest (eiu=0x5555555728b0) > at /usr/src/debug/rpm-4.18.0/lib/rpminstall.c:333 > #63 rpmInstall (ts=ts@entry=0x555555571b30, ia=<optimized out>, > fileArgv=<optimized out>) at /usr/src/debug/rpm-4.18.0/lib/rpminstall.c:565 > #64 0x00005555555567e1 in main (argc=3, argv=<optimized out>) > at /usr/src/debug/rpm-4.18.0/rpm.c:274 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213692] New: AUDIT-WHITELIST: org.freedesktop.home1.service is being moved from systemd-experimental to systemd-homed
by bugzilla_noreply＠suse.com 08 Aug '23

08 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213692 Bug ID: 1213692 Summary: AUDIT-WHITELIST: org.freedesktop.home1.service is being moved from systemd-experimental to systemd-homed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, systemd-homed is no more considered as an experimental feature and as such it has been moved to a dedicated sub-package named "systemd-homed". This change has just been submitted: sr#1100898 Since rpmlint whitelistings are tied to individual packages it needs to be updated accordingly. For the logs of the build failure, see: https://build.opensuse.org/package/live_build_log/Base:System/systemd/stand… Could anyone take care of this ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213592] New: Disable old unmaintained serial drivers
by bugzilla_noreply＠suse.com 08 Aug '23

08 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213592 Bug ID: 1213592 Summary: Disable old unmaintained serial drivers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jslaby(a)suse.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- These drivers are enabled in master/stable, but should not. They are for very old HW and are mostly unmaintained nowadays. They are even a potential risk. CONFIG_SYNCLINK_GT=m CONFIG_MOXA_INTELLIO=m (moxa) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213365] New: kernel 6.4.2 - error messages and dropouts for usb hub and network adapter
by bugzilla_noreply＠suse.com 07 Aug '23

07 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213365 Bug ID: 1213365 Summary: kernel 6.4.2 - error messages and dropouts for usb hub and network adapter Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting with Linux 6.4.2-1-default I get the following new error messages in my log: kernel: usb 9-1: device descriptor read/64, error -71 kernel: usb 9-1: device descriptor read/64, error -71 kernel: usb 9-1: device descriptor read/64, error -71 kernel: usb 9-1: device descriptor read/64, error -71 kernel: usb 9-1: device not accepting address 4, error -71 kernel: usb 9-1: device not accepting address 5, error -71 kernel: usb usb9-port1: unable to enumerate USB device ... kernel: r8152 10-2.3:1.0: ram code speedup mode fail kernel: r8152 10-2.3:1.0 (unnamed net_device) (uninitialized): netif_napi_add_weight() called with weight 256 Actual system version is openSUSE Tumbleweed 20230714. usb 9-1 is Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub which is an integrated usb hub in a DELL U4924DW monitor. The netowrk card also is integrated in this monitor. All usb devices connected to that hub seem to work generally, but have some dropouts from time to time. The network card sometimes loses connection. With kernel 6.3.9 this doesn't happen. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1213693] New: Black Screen during boot of kernel 6.4.x
by bugzilla_noreply＠suse.com 07 Aug '23

07 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213693 Bug ID: 1213693 Summary: Black Screen during boot of kernel 6.4.x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: grueffelokatze(a)raubtierbaendiger.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, I'm running my "MSI GS65 Stealth Thin RE8" notebook since a long time with Tumbleweed. It features a dual graphics card (intel/nvidia). When you rolled out the new kernel 6.4.x, I faced the issue, that during boot, the screen went black and never comes back. But the system itself is up and running (e.g. ssh works fine). Now, with the last update you have removed the 6.3.x kernel from the system, which was still running fine. The only thing I found which brings the graphics to work in a basic mode, is setting kernel argument "acpi=off". But this leads to a 800x600 resolution which makes me crazy. I also tried the current KDE Live CD (x86_64) version and the installation system (x86_64) of Tumbleweed. Both are ending in the same situation. They are only showing a black screen, too. Do you have any ideas where that comes from? Which kind of log files you might need for analysis? Kind regards, Gori -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1213158] New: When using the LXC Leap image, zypper is not available. Similarly, when using openSUSE Tumbleweed, both dnf and zypper are not available.
by bugzilla_noreply＠suse.com 07 Aug '23

07 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213158 Bug ID: 1213158 Summary: When using the LXC Leap image, zypper is not available. Similarly, when using openSUSE Tumbleweed, both dnf and zypper are not available. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ykla(a)bsdcn.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When using the LXC Leap image, zypper is not available. Similarly, when using openSUSE Tumbleweed, both dnf and zypper are not available. for For example, when trying to install Vim, you will encounter an error message. -------------------------- Installation of perl-5.36.1-1.2.x86_ 64 failed: ErroP's Subprocessg faited.c Error: RPM failed: Command exited with status 1 ----------------------------- In LXC Leap, replacing rpm-ndb with rpm can resolve this issue, and dnf does not encounter this problem. The issue is specific to zypper. However, in openSUSE Tumbleweed LXC, both dnf and zypper have this problem, and replacing rpm-ndb does not solve it. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1213698] New: We have .cpython-311.pyc in non-311 packages
by bugzilla_noreply＠suse.com 07 Aug '23

07 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213698 Bug ID: 1213698 Summary: We have .cpython-311.pyc in non-311 packages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: bwiedemann(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I have been reminded about this: -/usr/lib/python3.9/site-packages/blinker/__pycache__/base.cpython-311.pyc 6e33550a94efe8668e6b60422f1a674c9844fd6c44e92c0afcc5d98e71cf51cb 0 +/usr/lib/python3.9/site-packages/blinker/__pycache__/base.cpython-311.pyc 0b7e8cb203ad88028706b7204f007bb66a860cf3cfd6ebde4964a4caf6c248ef 0 why are 311.pyc files in the 3.9 path? We run make html without specifying Python used. It runs the Sphinx builder with /usr/bin/python3 which is now Python 3.11 and it loads (and generates *.pyc) when collecting information on the installed libraries. Suggested solution is https://stackoverflow.com/q/34025113/164233 and I have tried it in https://build.opensuse.org/request/show/1100942 However, it seems like too complicated problem (patching every package). Any other ideas? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1213560] New: update failed
by bugzilla_noreply＠suse.com 06 Aug '23

06 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213560 Bug ID: 1213560 Summary: update failed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: robin(a)bradbear.com.au QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- <html>Dependency resolution failed:<br/><br/>the to be installed python310-nbformat-5.9.0-2.1.noarch requires '(python310-jsonschema > 2.6 with python310-jsonschema < 4.18)', but this requirement cannot be provided the to be installed python310-jsonschema-format-nongpl-4.18.3-1.1.noarch requires 'python310-jsonschema = 4.18.3', but this requirement cannot be provided the to be installed python311-nbformat-5.9.0-2.1.noarch requires '(python311-jsonschema > 2.6 with python311-jsonschema < 4.18)', but this requirement cannot be provided the to be installed python311-jsonschema-format-nongpl-4.18.3-1.1.noarch requires 'python311-jsonschema = 4.18.3', but this requirement cannot be provided</html> -- You are receiving this mail because: You are on the CC list for the bug.

1 3