September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1190946] PAM module packages should use %_pam_moduledir
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190946 Bug 1190946 depends on bug 1190949, which changed state. Bug 1190949 Summary: pam_csync: use %_pam_moduledir http://bugzilla.opensuse.org/show_bug.cgi?id=1190949 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190949] pam_csync: use %_pam_moduledir
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190949 http://bugzilla.opensuse.org/show_bug.cgi?id=1190949#c4 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Ludwig Nussel <lnussel(a)suse.com> --- closing -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1196967] kernel 5.14, 5.16.11 and 5.17-rc7 crash on NVIDIA jetson nano
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1196967 https://bugzilla.suse.com/show_bug.cgi?id=1196967#c21 --- Comment #21 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Alexandre Vicenzi from comment #19) > (In reply to Takashi Iwai from comment #17) > > If you can still reproduce the problem with 5.19, at best, report this to > > the upstream. It should be fixed there at first. > > > > I was not able to reproduce this issue with 5.19. Aha, so it's been fixed between 5.18 and 5.19, supposedly? > > Just to be sure: you've tested vanilla kernel, and 5.15.x is only to 5.15.13? > > I'm asking it because 5.15.23 contains a known problematic stuff (the commit > > f0a60c7c4edee3f108ec435d457149175d0b0afa). > > Yes, the vanilla versions I tested were only 5.14.15, 5.15.13, and 5.16.16. OK, any chance to give a quick try with the revert of f0a60c7c4edee3f108ec435d457149175d0b0afa? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203119] New: Installation the Selinux Enforcing/Permissive is not available to choose
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203119 Bug ID: 1203119 Summary: Installation the Selinux Enforcing/Permissive is not available to choose Classification: openSUSE Product: openSUSE Leap Micro Version: 5.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: jalausuch(a)suse.com Found By: --- Blocker: --- Created attachment 861303 --> http://bugzilla.opensuse.org/attachment.cgi?id=861303&action=edit selinux permissive Seems like user can choose in between App Armor and SELinux, but he seems not to be able to change mode from Permissive (the list box seems disabled/ro). More details in the screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1199630] selinux policy blocks nss-systemd
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199630 https://bugzilla.suse.com/show_bug.cgi?id=1199630#c4 Filippo Bonazzi <filippo.bonazzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |filippo.bonazzi(a)suse.com Resolution|--- |FIXED --- Comment #4 from Filippo Bonazzi <filippo.bonazzi(a)suse.com> --- Closing as done -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188998] New: magnetic tape drive control (mt) missing from rescue system of 15.3 ISO
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188998 Bug ID: 1188998 Summary: magnetic tape drive control (mt) missing from rescue system of 15.3 ISO 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: Installation Assignee: yast2-maintainers(a)suse.de Reporter: wefing(a)gmx.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Program "mt" for controlling a magnetic tape drive is not part of the rescue system of the opensuse 15.3 installation ISO. Hence it is rather cumbersome to select a certain tar file from a tape for recovery (no fast forward positioning to file N on the tape). The last rescue system with an mt program was part of the ISO of opensuse 42.3. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1199895] PackageKit does not honor zypper package locks
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199895 https://bugzilla.suse.com/show_bug.cgi?id=1199895#c32 Ednilson Miura <emiura(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emiura(a)suse.com --- Comment #32 from Ednilson Miura <emiura(a)suse.com> --- Hello, while testing S:M:24915:275232 (packagekit update for SLE15SP3) I'm having some issues reproducing this issue. What I have tried: I know that there is a tigervnc pending update,so: # zypper al tigervnc Specified lock has been successfully added. ligur:~ # zypper ll # | Name | Type | Repository | Comment --+----------+---------+------------+-------- 1 | tigervnc | package | (any) | But now: # pkcon update Getting updates [=========================] Finished [=========================] Refreshing software list [=========================] Testing changes [=========================] Finished [=========================] Fatal error: the to be installed patch:SUSE-SLE-Module-Basesystem-15-SP3-2022-3012-1.noarch conflicts with 'tigervnc.x86_64 < 1.9.0-150100.19.20.1' provided by the installed tigervnc-1.9.0-150100.19.17.1.x86_64 It says that it "conflicts" with the updated package. Removing the lock solves the issue. Is there another way to reproduce this issue? (I have the same behaviour before/after applying packagekit update) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203118] New: glibc debuginfo makes inferior call difficult
by bugzilla_noreply＠suse.com 05 Sep '22

05 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203118 Bug ID: 1203118 Summary: glibc debuginfo makes inferior call difficult Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- [ Minimized from gdb test-case gdb.base/break-main-file-remove-fail.exp. ] Consider test-case test.c: ... #include <sys/mman.h> int main (void) { int res = munmap (0, 0); return 0; } ... Compiled like this: ... $ gcc -g test.c ... Trying to do an inferior call to munmap has become complicated: ... $ gdb -q -batch -iex "set debuginfod enabled on" a.out \ -ex "set trace-commands on" \ -ex start \ -ex n \ -ex "p res" \ -ex "p munmap" \ -ex "p munmap (0, 0)" \ -ex "p (int) munmap (0, 0)" \ -ex "p ((int (*) (void *, size_t)) munmap) (0, 0)" +start Temporary breakpoint 1 at 0x40113e: file test.c, line 6. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Temporary breakpoint 1, main () at test.c:6 6 int res = munmap (0, 0); +n 8 return 0; +p res $1 = -1 +p munmap $2 = {void (void)} 0x7ffff7feb9a0 <__GI_munmap> +p munmap (0, 0) $3 = void +p (int) munmap (0, 0) Invalid cast. +p ((int (*) (void *, size_t)) munmap) (0, 0) $4 = -1 ... AFAICT, this is due to libc debuginfo: ... <0><189683>: Abbrev Number: 1 (DW_TAG_compile_unit) <189684> DW_AT_stmt_list : 0xeba4b <189688> DW_AT_low_pc : 0x10cad0 <189690> DW_AT_high_pc : 37 <189691> DW_AT_name : ../sysdeps/unix/syscall-template.S <189695> DW_AT_comp_dir : /usr/src/debug/glibc-2.36-1.3.x86_64/misc <189699> DW_AT_producer : GNU AS 2.39.0 <18969d> DW_AT_language : 32769 (MIPS assembler) <1><18969f>: Abbrev Number: 2 (DW_TAG_subprogram) <1896a0> DW_AT_name : __munmap <1896a4> DW_AT_external : 1 <1896a5> DW_AT_low_pc : 0x10cad0 <1896ad> DW_AT_high_pc : 37 <1><1896ae>: Abbrev Number: 2 (DW_TAG_subprogram) <1896af> DW_AT_name : __GI___munmap <1896b3> DW_AT_external : 1 <1896b4> DW_AT_low_pc : 0x10cad0 <1896bc> DW_AT_high_pc : 37 <1><1896bd>: Abbrev Number: 2 (DW_TAG_subprogram) <1896be> DW_AT_name : munmap <1896c2> DW_AT_external : 0 <1896c3> DW_AT_low_pc : 0x10cad0 <1896cb> DW_AT_high_pc : 37 <1><1896cc>: Abbrev Number: 2 (DW_TAG_subprogram) <1896cd> DW_AT_name : __GI_munmap <1896d1> DW_AT_external : 1 <1896d2> DW_AT_low_pc : 0x10cad0 <1896da> DW_AT_high_pc : 37 ... If we ignore the shared library info using nosharedlibrary, we get instead: ... +nosharedlibrary +p munmap $2 = {<text variable, no debug info>} 0x401030 <munmap@plt> +p munmap (0, 0) 'munmap@plt' has unknown return type; cast the call to its declared return type +p (int) munmap (0, 0) $3 = -1 +p ((int (*) (void *, size_t)) munmap) (0, 0) $4 = -1 ... -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[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#c3 --- Comment #3 from Ralf Habacker <ralf.habacker(a)freenet.de> --- (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: $ 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) $ 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? -- 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#c20 Marius Tomaschewski <mt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ralf.habacker@fre | |enet.de) | --- Comment #20 from Marius Tomaschewski <mt(a)suse.com> --- (In reply to Ralf Habacker from comment #18) > https://bugzilla.opensuse.org/show_bug.cgi?id=1202658 See also the rejection of the incomplete routing settings by the kernel in an attempt to apply them manually in: https://bugzilla.suse.com/show_bug.cgi?id=1202658#c2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0