September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1202658] wicked ignores configured static routes when using dhcp
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202658 https://bugzilla.suse.com/show_bug.cgi?id=1202658#c2 --- Comment #2 from Marius Tomaschewski <mt(a)suse.com> --- Example showing the cause to apply the incomplete static settings (while dhcp is in use and thus there is no static IPADDR): # ip addr show dev dummy0 Device "dummy0" does not exist. # ip link add dev dummy0 type dummy # ip link set up dummy0 # ip addr show dev dummy0 55: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether ce:0e:42:76:18:82 brd ff:ff:ff:ff:ff:ff # ip route show dev dummy0 # ip route add 10.2.1.1/32 via 10.1.1.252 dev dummy0 Error: Nexthop has invalid gateway. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -> The kernel rejects to create the route with gateway. After prepending a direct route allowing to reach the gateway: # ip route add 10.1.1.252 dev dummy0 # ip route add 10.2.1.1/32 via 10.1.1.252 dev dummy0 -> both routes are applied: # ip addr show dev dummy0 55: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether ce:0e:42:76:18:82 brd ff:ff:ff:ff:ff:ff # ip route show dev dummy0 10.1.1.252 scope link 10.2.1.1 via 10.1.1.252 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202658] wicked ignores configured static routes when using dhcp
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202658 https://bugzilla.suse.com/show_bug.cgi?id=1202658#c1 Marius Tomaschewski <mt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |mt(a)suse.com Resolution|--- |DUPLICATE --- Comment #1 from Marius Tomaschewski <mt(a)suse.com> --- The static config is incorrect/incomplete and causes failure: each route with a gateway requires a direct/device route without gateway that is matching the gateway IP or the kernel will reject the gateway route. When there is an IPADDR=10.1.1.x/24, the kernel will create a route (to the 10.1.1.0/24 network and thus to the gateway) when the address is applied, but when there is no IPADDR, a route to reach the gateway is missing - fix: $ cat /etc/sysconfig/network/ifroute-enps03 10.1.1.252 - - enps03 10.2.1.1/32 10.1.1.252 - enps03 See also: https://github.com/openSUSE/wicked/wiki/FAQ/#q-why-wicked-does-not-set-my-d… *** This bug has been marked as a duplicate of bug 907495 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 907495] adding a manual route to a dhcp configured interface results in failed dhcp setup (wicked managed)
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=907495 https://bugzilla.suse.com/show_bug.cgi?id=907495#c19 --- Comment #19 from Marius Tomaschewski <mt(a)suse.com> --- *** Bug 1202658 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203109] New: scm_git service does not fetch latest git commit from github
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203109 Bug ID: 1203109 Summary: scm_git service does not fetch latest git commit from github Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: ralf.habacker(a)freenet.de QA Contact: adrian.schroeter(a)suse.com Found By: --- Blocker: --- At https://build.opensuse.org/package/show/home:rhabacker:branches:games:mingw… I have configured an scm_git service to retrieve recent git sources from the github git repository https://github.com/vsg-dev/vsgXchange.git, which has worked well for a while. The problem recently is that it does not retrieve the latest commit that is currently https://github.com/vsg-dev/vsgXchange/commit/9130566fc4c99a7834bd2bbe4a27dd…, but always retrieves an older commit after triggering the service https://github.com/vsg-dev/vsgXchange/commit/3fa705edb9a1d11a17596ca2d333ff…. With a local `osc` build the problem does not occur. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1202746] How about Version 7.4
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202746 https://bugzilla.suse.com/show_bug.cgi?id=1202746#c5 --- Comment #5 from Hansi Meir <Hansi.Meir(a)gmx.de> --- Hi Danilo, thank you so much for this work! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202746] How about Version 7.4
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202746 https://bugzilla.suse.com/show_bug.cgi?id=1202746#c4 --- Comment #4 from Danilo Spinella <danilo.spinella(a)suse.com> --- Hi Hansi, I have just seen this bug. I am currently working on Libreoffice 7.4 and it will be ready after I fix a couple of issues, hopefully by the end of this week. I'll keep you updated. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199520] [SELinux] "no shell: permission denied" error on fresh Tumbleweed transactional server installation with enforcing SELinux
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199520 https://bugzilla.suse.com/show_bug.cgi?id=1199520#c21 Felix Niederwanger <felix.niederwanger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(felix.niederwange | |r(a)suse.com) | --- Comment #21 from Felix Niederwanger <felix.niederwanger(a)suse.com> --- Yes that seems to work! > # transactional-update shell > (therein) zypper in microos-tools > (therein) touch /etc/selinux/.autorelabel > (therein) vim /etc/selinux/config # set from permissive to enforcing > reboot Then the login works, via ssh and via login terminal. SELinux is set to enforcing, so that's also OK: > bsc1199520:~ # sestatus > SELinux status: enabled > SELinuxfs mount: /sys/fs/selinux > SELinux root directory: /etc/selinux > Loaded policy name: targeted > Current mode: enforcing > Mode from config file: enforcing > Policy MLS status: enabled > Policy deny_unknown status: allowed > Memory protection checking: actual (secure) > Max kernel policy version: 33 Hope that helps. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200960] readline no longer works on Python
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1200960 https://bugzilla.suse.com/show_bug.cgi?id=1200960#c4 --- Comment #4 from Bob Vickers <bob(a)vickers.simplyms.com> --- Thanks for the helpful comments. I've just returned from holiday, so can now follow them up. It turns out I DO have Python version 3 installed and if I use the command 'python3' then readline support works fine. But my Python 3 packages do not provide a command "python"; is this expected behaviour? Here is some more info: $ ls -l /usr/bin/python* lrwxrwxrwx 1 root root 9 Jun 10 10:14 /usr/bin/python -> python2.7 lrwxrwxrwx 1 root root 9 Jun 10 10:14 /usr/bin/python2 -> python2.7 -rwxr-xr-x 1 root root 6304 Jun 10 10:15 /usr/bin/python2.7 lrwxrwxrwx 1 root root 9 Jul 6 15:30 /usr/bin/python3 -> python3.6 -rwxr-xr-x 2 root root 10584 Jul 6 15:30 /usr/bin/python3.6 -rwxr-xr-x 2 root root 10584 Jul 6 15:30 /usr/bin/python3.6m lrwxrwxrwx 1 root root 45 May 9 12:14 /usr/bin/pythontex -> ../share/texmf/scripts/pythontex/pythontex.py $ rpm -qf /usr/bin/python python-base-2.7.18-150000.41.1.x86_64 $ rpm -qf /usr/bin/python3 python3-base-3.6.15-150300.10.27.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203095] New: Dual monitor not detected after the latest Tumbleweed update on 20YQ009TUS with NVIDIA RTX A4000
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203095 Bug ID: 1203095 Summary: Dual monitor not detected after the latest Tumbleweed update on 20YQ009TUS with NVIDIA RTX A4000 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: alexstol(a)live.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0 Build Identifier: 1. After installing latest Tumbleweed with distribution with KDE Plasma end of Aug, 2022 the dual monitor was detected, displaying background, but non-responsive, not showing any windows. 2. Updated using zyper dup, now the second monitor is not detected at all. 3. Tried installing NVIDIA drivers from https://download.nvidia.com/opensuse/tumbleweed, pulled using Yast (see https://ibb.co/Hh47r9P), However, after the installation Tumbleweed loads in a black screen, therefore I am being cautious installing it again. 4. systemsettings5 kf.coreaddons: "Could not load plugin from kcm_kscreen: The shared library was not found." file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/share/kpackage/kcms/kcm_nightcolor/contents/ui/main.qml:42: TypeError: Cannot call method 'destroy' of undefined file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/share/kpackage/kcms/kcm_nightcolor/contents/ui/main.qml:263: TypeError: Cannot read property 'latitude' of undefined file:///usr/share/kpackage/kcms/kcm_nightcolor/contents/ui/main.qml:383: TypeError: Cannot read property 'longitude' of undefined file:///usr/share/kpackage/kcms/kcm_nightcolor/contents/ui/main.qml:382: TypeError: Cannot read property 'latitude' of undefined 5. sudo prime-select nvidia nvidia catched Preparing first configuration bbswitch not loaded If you want energy saving bbswitch should be loaded in intel mode. For this package 'bbswitch' needs to be installed on your system. Or make use of DynamicPowerManagement on Turing GPUs or later by switching to suse-prime's 'offload' or 'nvidia' mode. Logout to switch graphics > exit > /usr/sbin/prime-select get-current No driver configured. NVIDIA/Intel video card selection for NVIDIA Optimus laptops. usage: prime-select nvidia|intel|intel2|amd|offload|unset|get-current|get-boot|offload-set|log-view|log-clean usage: prime-select boot nvidia|intel|intel2|amd|offload|last usage: prime-select next-boot nvidia|intel|intel2|amd|offload|abort usage: prime-select service check|disable|restore nvidia: use the NVIDIA proprietary driver intel: use the Intel card with the "modesetting" driver intel2: use the Intel card with the "intel" Open Source driver (xf86-video-intel) amd: use the Amd card with the "amd" Open Source driver (xf86-video-amdgpu) offload PRIME Render Offload possible with >= 435.xx NVIDIA driver offload-set choose which intel driver use in PRIME Render Offload unset: disable effects of this script and let Xorg decide what driver to use get-current: display driver currently configured log-view: view logfile log-clean: clean logfile boot: select default card at boot or set last used supports kernel parameter nvidia.prime=intel|intel2|nvidia|amd|offload next-boot: select card ONLY for next boot, it not touches your boot preference. abort: restores next boot to default get-boot: display default card at boot service: disable, check or restore prime-select service. bbswitch not loaded If you want energy saving bbswitch should be loaded in intel mode. For this package 'bbswitch' needs to be installed on your system. Or make use of DynamicPowerManagement on Turing GPUs or later by switching to suse-prime's 'offload' or 'nvidia' mode. > sudo prime-select nvidia [sudo] password for root: nvidia catched Error: a switch operation already in execution You can undo it using sudo killall prime-select Reproducible: Always Steps to Reproduce: 1. Install new Tumbleweed on 0YQ009TUS with NVIDIA RTX A4000, KDE Plasma 2. Update using zypper dup 3. Install NVIDIA drivers Actual Results: 4. After 2-3 dual monitor not detected 5. After 3 Tumbleweed loads with the black screen. Expected Results: Dual monitor detected and configurable. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1202341] Raspi 4 (4GB): boots to blank screen with kernel 5.14.21-150400.24.11-default
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202341 https://bugzilla.suse.com/show_bug.cgi?id=1202341#c7 --- Comment #7 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- Ivan, you can try to bisect this? There were quite a few backports done on the 4th of August. Perhaps one of those broke VC4. I usually do "git log drivers/gpu/drm/vc4" on the expanded tree to find recent commits. I'll ping Petr to see if there is a a Pi4 that can be sent to me. It would make it easier when working on VC4. -- You are receiving this mail because: You are on the CC list for the bug.

1 0