October 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1200625] New: Error message: Failed to connect to "Opensuse mirrorcache repo" port 443 after x ms: No route to host
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200625 Bug ID: 1200625 Summary: Error message: Failed to connect to "Opensuse mirrorcache repo" port 443 after x ms: No route to host Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: All OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: belazizadam04(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It's my first help request. When I use Opensuse in general my usb network (using my phone for provide internet) act really weirdly it affect zypper as "No route to host" error and also any usage of my network. When I use other distribution like Fedora / Centos / Debian Based OS I don't have this error I was thinking about where the problem from. Trying to modify my firewall or my NetworkManager-gui It dosen't solve my problem I'm really sure that the issues isn't from my phone or my DNS I think it's a Opensuse problem else why it work on any other distro ? If you want more infomation let me know ! and Thanks for helping me ! -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1189560] New: firewalld forgets wicked zone assignment on service restart
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1189560 Bug ID: 1189560 Summary: firewalld forgets wicked zone assignment on service restart Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: mrostecki(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: rfrohl(a)suse.com, wicked-maintainers(a)suse.de Found By: --- Blocker: --- When the system boots, wicked's firewalld extension mechanism informs firewalld about the configured interfaces and assignes them to the configured zones: localhost:~ # firewall-cmd --list-interfaces ens3 This is kept after a reload: localhost:~ # firewall-cmd --reload success localhost:~ # firewall-cmd --list-interfaces ens3 But not after a restart: localhost:~ # rcfirewalld restart localhost:~ # firewall-cmd --list-interfaces You're performing an operation over default zone ('public'), but your connections/interfaces are in zone 'docker' (see --get-active-zones) You most likely need to use --zone=docker option. This seems very fragile and hits openQA which (for some reason, probably a bad one) disables the firewall temporarily in some tests. Maybe wicked should save the zone assignments in the permanent config? -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1193599] New: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193599 Bug ID: 1193599 Summary: ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D 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: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following errors appear at boot broken atomic modeset userspace detected, disabling atomic [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D [drm spcon_init [i915]] *ERROR* Failed to probe lspcon [drm ntel_dp_detect [i915]] *ERROR* LSPCON init failed on port D Full log https://paste.opensuse.org/83436185 Hardware Dell Precision 7530 CPU: Intel Xeon E-2186M GPU: Intel P630 / Nvidia Quadro P3200 -- You are receiving this mail because: You are on the CC list for the bug.

1 35

[Bug 1202053] New: Nokogiri was built against LibXML version 2.9.12, but has dynamically loaded 2.9.14
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202053 Bug ID: 1202053 Summary: Nokogiri was built against LibXML version 2.9.12, but has dynamically loaded 2.9.14 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Ruby Assignee: ruby-devel(a)suse.de Reporter: duge(a)pre-sense.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the libxml2-2-2.9.14 update ruby2.5-rubygem-nokogiri reports: WARNING: Nokogiri was built against LibXML version 2.9.12, but has dynamically loaded 2.9.14 Reproduction: ruby -e 'require "nokogiri"' Please coordinate with bug 1201978. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1204320] New: Ansible: No module named 'ansible_test'
by bugzilla_noreply＠suse.com 07 Dec '22

07 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204320 Bug ID: 1204320 Summary: Ansible: No module named 'ansible_test' 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: pdostal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, in latest Tumbleweed the ansible-test is part of ansible package. But when running the command I get this error: > # zypper in ansible > (13/14) Installing: ansible-core-2.13.5-1.1.noarch [............done] > (14/14) Installing: ansible-6.4.0-1.1.noarch [............done] > $ ansible-test sanity; echo NLfh1-$?- > Traceback (most recent call last): > File "/usr/bin/ansible-test", line 45, in <module> > main() > File "/usr/bin/ansible-test", line 24, in main > from ansible_test._util.target.common.constants import CONTROLLER_PYTHON_VERSIONS > ModuleNotFoundError: No module named 'ansible_test' Previously, there was separate ansible-test package. This also works when I install ansible via pip. Thank you for your help Pavel Dost�l -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1203468] New: xrdp broken when updating TW from build 20220813 to 20220908
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203468 Bug ID: 1203468 Summary: xrdp broken when updating TW from build 20220813 to 20220908 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: jmscdba(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Updated several machines from TW 20220813 to 20220908 today and found that xrdp connections no longer work on any of the machines. The Connection Log is not real useful: Connecting to sesman on 127:0.0.1:3350 sesman connect ok sending login info to session manager.Please wait.. login successful for user denise on display 200 VNC started connecting Waiting 2000 ms for VNC to start... VNC connecting to 127.0.0.1.6100 VNC error - problem connecting some problem Error connecting to user session Comparing journal entries from build 20220813 where it was working and build 20220908 where it no longer works, I suspect that this is the source of the problem: Sep 15 12:52:27 xrdp-sesman[2328]: [mi] mieq: warning: overriding existing handler (nil) with 0x55a01f4cc210 for event 2 Sep 15 12:52:27 xrdp-sesman[2328]: [mi] mieq: warning: overriding existing handler (nil) with 0x55a01f4cc210 for event 3 Sep 15 12:52:27 xrdp-sesman[2343]: Failed to connect to bus: No medium found Reverting xrdp from xrdp-0.9.19-1.2.x86_64.rpm ( which is in 20220908 ) back to xrdp-0.9.19-1.1.x86_64.rpm ( which is in 20220813 ) resolves the issue. Looks like build 20220914 is using the same version as 20220908. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1204672] New: strip r600_drv_video.so: file format not recognized
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204672 Bug ID: 1204672 Summary: strip r600_drv_video.so: file format not recognized Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86 OS: Fedora Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: estellnb(a)elstel.org QA Contact: adrian.schroeter(a)suse.com Found By: --- Blocker: --- Created attachment 862396 --> http://bugzilla.opensuse.org/attachment.cgi?id=862396&action=edit log of the first/previous build Dear openSUSE and OBS maintainers: I always get a whimsical error trying to compile mesa-22.2 on Fedora 36 i586 though I have tried it two times (disabled/reenabled i586 to trigger rebuild): [ 2372s] /usr/bin/strip: /home/abuild/rpmbuild/BUILDROOT/mesa-22.2-65.2.i386/usr/lib/dri/r600_drv_video.so: file format not recognized [ 2375s] error: Bad exit status from /var/tmp/rpm-tmp.4RZv49 (%install) Some time before the package did compile well (just renamed some libraries). The x86_64 target also compiles well as well as i586 under three different distros. Could there be something bad about the build host? Please have a look. Here is the package: https://build.opensuse.org/project/show/home:estellnb:mageiaupdtst -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1203408] New: oscap xccdf eval notapplicable instead of fail
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203408 Bug ID: 1203408 Summary: oscap xccdf eval notapplicable instead of fail 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: pstivanin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- - download the latest qcow2 from o3 (e.g. https://openqa.opensuse.org/tests/2656844/asset/hdd/opensuse-15.5-aarch64-2…) - zypper in openscap-utils libxslt-tools - download the xml files from https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/data… - check the file with 'oscap info xccdf.xml' - oscap xccdf eval --profile standard --results out.xml xccdf.xml output: Title Direct root Logins Not Allowed Rule no_direct_root_logins Result notapplicable Title sysctl kernel.sysrq must be 0 Rule rule_misc_sysrq Result notapplicable expected output: # oscap xccdf eval --profile standard --results out.xml xccdf.xml Title Direct root Logins Not Allowed Rule no_direct_root_logins Result fail Title sysctl kernel.sysrq must be 0 Rule rule_misc_sysrq Result fail -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1193183] New: inkscape-1.1.1-lp153.87.2 is not working
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193183 Bug ID: 1193183 Summary: inkscape-1.1.1-lp153.87.2 is not working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: michael.kasimir(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- as reported in openSUSE support mailing list 28 Nov 2021 18:36 https://lists.opensuse.org/archives/list/support@lists.opensuse.org/thread/… after upgrade from 15.2 to 15.3, the start of inkscape could not be launched. Package version: inkscape-1.1.1-lp153.87.2.x86_64.rpm Terminal .bash run shows the following error message: $ inkscape inkscape: error while loading shared libraries: libinkscape_base.so: cannot open shared object file: No such file or directory As message shows apparently it should have to do with libinkscape_base.so The issue has been verified on a new, updated Leap 15.3 system and inkscape installed via opi from graphics-repository https://download.opensuse.org/repositories/graphics/openSUSE_Leap_15.3/x86_… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1191933] New: Kernel can not update on Secure boot envirnment
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191933 Bug ID: 1191933 Summary: Kernel can not update on Secure boot envirnment 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: kokeko(a)mac.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Current 20211012, update to 20211016 or 20211019. Kernel-default update failed by fallowing error. subprocess error, secure boot enabled. Is it something change? -- You are receiving this mail because: You are on the CC list for the bug.

1 3