September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1203156] New: Dolphin focus incorrect in split-window mode: Always on r.h.s. at Dolphin start, want l.h.s.
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203156 Bug ID: 1203156 Summary: Dolphin focus incorrect in split-window mode: Always on r.h.s. at Dolphin start, want l.h.s. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ludger.ricken(a)thyssenkrupp.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running openSUSE Tumbleweed, latest updates, KDE Plasma desktop. I use Dolphin in split-window [two-column] mode (old Norton Commander habit...), and I use Krusader the same way. Dolphin has an issue with which of the two windows [columns] gets the focus when Dolphin starts, while Krusader does everything alright. This holds for both the standard and root versions of invoking Dolphin. I want Dolphin to always have the focus on the l.h.s. window [column] when Dolphin starts. Thus, in Dolphin "Preferences", I have "Start" -> "Show at start" -> "Folders, sub-windows, window status as of last start" (translated from German). However, annoyingly, Dolphin always comes up with the focus on the r.h.s. window [column]. It doesn't help to exit Doplhin with the focus on the l.h.s., and there is no setting I can chose in Preferences to help either. I am first filing this bug here on the openSUSE Bugzilla, and I might also file it on the KDE Bugtracker. Having asked on the openSUSE Forum has not produced a result yet. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1184817] System becomes unstable and unusable when using wired network
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1184817 https://bugzilla.suse.com/show_bug.cgi?id=1184817#c38 --- Comment #38 from teo teo <php4fan(a)gmail.com> --- > The fact that web browser doesn't open That's never happened to me. The browser (which is already open and I've been using for a while) stops responding (meaning I'm unable to switch between tabs, and/or close tabs, and/or scroll, and/or etc.), but when I close it and relaunch it it opens immediately, and usually works for a while. And the same with other applications. > When the problem happens, and when you unplug the USB Ethernet device (instead of power-off / reset), does the problem persist? Yes. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203064] sar2pcp from pcp-import-sar2pcp broken
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203064 https://bugzilla.suse.com/show_bug.cgi?id=1203064#c3 --- Comment #3 from David Disseldorp <ddiss(a)suse.com> --- (In reply to David Disseldorp from comment #2) ... > # /usr/bin/sar2pcp ./int14.file int14.pcp > perl: symbol lookup error: > /usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi/auto/PCP/ > LogImport/LogImport.so: undefined symbol: pmiStart > > # rpm -qf > /usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi/auto/PCP/ > LogImport/LogImport.so > perl-PCP-LogImport-5.2.2-1.4.x86_64 > > # rpm -qf /usr/lib64/libpcp_import.so.1 > libpcp_import1-5.2.2-1.4.x86_64 > > pcp (522)> git blame src/libpcp_import/src/exports > 35ce669f6a (Nathan Scott 2013-12-03 16:16:53 +1100 1) PCP_IMPORT_1.0 { > 35ce669f6a (Nathan Scott 2013-12-03 16:16:53 +1100 2) global: > 35ce669f6a (Nathan Scott 2013-12-03 16:16:53 +1100 3) pmiStart; The required pmiStart symbol is present: # readelf -aW /usr/lib64/libpcp_import.so.1|grep pmiStart 84: 0000000000003360 2487 FUNC GLOBAL DEFAULT 14 pmiStart@@PCP_IMPORT_1.0 But the perl library doesn't have libpcp_import.so as a depedency: # ldd /usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi/auto/PCP/LogImport/LogImport.so linux-vdso.so.1 (0x00007ffd64a67000) libc.so.6 => /lib64/libc.so.6 (0x00007f051d91e000) /lib64/ld-linux-x86-64.so.2 (0x00007f051df1c000) I won't pretend to understand Makefile.PL logic, but pcp/src/perl/LogImport/Makefile.PL does appear to link against libpcp_import: 18 $libs = ["-L$ENV{PCP_TOPDIR}/src/libpcp/src -L$ENV{PCP_TOPDIR}/src/libpcp_import/src -lpcp_import -lpcp"]; ... 32 WriteMakefile( 33 NAME => 'PCP::LogImport', ... 46 LIBS => $libs, -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203156] Dolphin focus incorrect in split-window mode: Always on r.h.s. at Dolphin start, want l.h.s.
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203156 https://bugzilla.suse.com/show_bug.cgi?id=1203156#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fvogt(a)suse.com Resolution|--- |UPSTREAM --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- > I am first filing this bug here on the openSUSE Bugzilla, and I might also file it on the KDE Bugtracker. Yes, I think it makes sense to handle this upstream on bugs.kde.org. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203147] dracut reports: /usr/lib/plymouth/plymouth-populate-initrd: line 450: +: command not found
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203147 Antonio Feijoo <antonio.feijoo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |qzhao(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199840] New: Allow YaST to configure a different target system (mounted in e.g. /mnt)
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199840 Bug ID: 1199840 Summary: Allow YaST to configure a different target system (mounted in e.g. /mnt) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lslezak(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- This would allow running YaST in a container and manage the host system. Advantages: - Really minimal "minimal system", no need to install Ruby, etc. in the system - Containers would allow to use newer Ruby or libraries than shipped in SLE -- You are receiving this mail because: You are on the CC list for the bug.

1 2

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

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202658 https://bugzilla.suse.com/show_bug.cgi?id=1202658#c4 --- Comment #4 from Marius Tomaschewski <mt(a)suse.com> --- (In reply to Ralf Habacker from comment #3) > (In reply to Marius Tomaschewski from comment #2) > > Example showing the reason for using the incomplete static settings. > > (while dhcp is in use and therefore there is no static IPADDR): > > I think the use case I reported is a bit different: No, it isn't. See bellow. > $ ip addr > ... > 2: enps03 > inet 10.1.1.30/24 metric 1024 brd 10.1.1.255 scope global dynamic enp0s3 > > The host has received an IP address from the DHCP server on the 10.1.1.0/24 > network. > > $ ip route > default via 10.1.1.250 dev enps03 proto dhcp > 10.1.1.250 dev enp0s3 proto dhcp scope link src 10.1.1.30 metric 1024 > 10.1.1.0/24 dev enps03 proto kernel scope link src 10.1.1.30 metric 1024 > > These settings were retrieved from the dhcp server. > > If I add the static route manually after the network has been started and > the host has received the IP configuration from the DHCP server (please note > that the gateway for the static route is on the local network) Yes, if and if. The host _may_ receive something from DHCP server (at a random point of time compared to apply time of the static settings) _or_ _not_ and it _may_ (accidentially) provide also an IP address from a network that matches the gateway from the static setup _or_ _not_. > $ ip route add 10.2.1.1/32 via 10.1.1.252 dev enps03 > > I did not receive an error message, instead the desired route was added. > > $ ip route > ... > 10.2.1.1 via 10.1.1.252 dev enp0s3 > > and is reachable > > $ ping 10.2.1.1 > PING 10.2.1.1 (10.2.1.1) 56(84) bytes of data. > 64 bytes of 10.2.1.1: icmp_seq=1 ttl=63 time=1.19 ms > > If this works, why doesn't adding this route to > /etc/sysconfig/network/ifroute-enps03 work? Because the static settings (static "lease") in ifroute files and the dhcp lease are two different leases "config sets" and applied independently of each other -- without conditions or dependencies between them. Both capable to provide the complete configuration and both need to be complete by themself. The clean way is to fix the dhcp server config to provide the routes as described in bug 907495 to provide all routes via dhcp (e.g. classless routes option). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201802] New: Firewall applet does not show up in system tray
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201802 Bug ID: 1201802 Summary: Firewall applet does not show up in system tray Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: fkrueger(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Given TW20220719 with KDE Plasma 5.25.3, firewall-applet-1.2.0-1.1.noarch, and > sudo firewall-cmd --state running the firewall applet does not show up automatically in the system tray anymore. Starting firewall-applet from the console works fine, without any error messages. Any idea? Thx. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1199520] SELinux broken on fresh Tumbleweed transactional server installation with enforcing SELinux
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199520 https://bugzilla.suse.com/show_bug.cgi?id=1199520#c23 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Assignee|yast-community(a)opensuse.org |fvogt(a)suse.com --- Comment #23 from Fabian Vogt <fvogt(a)suse.com> --- I thought I already closed this yesterday, but apparently I didn't hit save... Fixed with https://build.opensuse.org/request/show/1001330. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199520] SELinux broken on fresh Tumbleweed transactional server installation with enforcing SELinux
by bugzilla_noreply＠suse.com 06 Sep '22

06 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199520 Filippo Bonazzi <filippo.bonazzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also|https://bugzilla.suse.com/s | |how_bug.cgi?id=1202449 | -- You are receiving this mail because: You are on the CC list for the bug.

1 0