November 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1205137] New: zypper: Cannot query info of particular version
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205137 Bug ID: 1205137 Summary: zypper: Cannot query info of particular version Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: zypp-maintainers(a)suse.de Reporter: amajer(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I can install a particular version of a package available, but I cannot show into on it. For example, zypper install nodejs18=18.12.0-1.1 But this does not work, zypper info nodejs18=18.12.0-1.1 and it seems to list installed package by default. It would be nice if same syntax available for install package match would be available for other subcommands. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 944832] installing updates during shutdown causes reboot
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=944832 http://bugzilla.opensuse.org/show_bug.cgi?id=944832#c18 --- Comment #18 from Milachew <milachew(a)mail.lv> --- (In reply to Jonathan Kang from comment #17) > And they should be available soon. I also suggested changes directly to SP4 so that the fix would be delivered faster : https://build.opensuse.org/request/show/1033003 https://build.opensuse.org/request/show/1033005 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205134] New: elixir -j1 build gets stuck
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205134 Bug ID: 1205134 Summary: elixir -j1 build gets stuck Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: fabrizio.sestito(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- Steps To Reproduce: osc co openSUSE:Factory/elixir && cd $_ osc build --vm-type=kvm --clean --noservice -j1 standard Actual result: [ 374s] Finished in 190.1 seconds (11.6s on load, 0.05s async, 178.3s sync) [ 374s] 6 doctests, 758 tests, 5 failures [ 374s] [ 374s] Randomized with seed 96765 [ 374s] make: *** [Makefile:116: test_mix] Error 2 [ 374s] error: Bad exit status from /var/tmp/rpm-tmp.cQ6X6W (%check) [ 374s] [ 374s] RPM build errors: [ 374s] Bad exit status from /var/tmp/rpm-tmp.cQ6X6W (%check) [97624s] qemu-kvm: terminating on signal 2 [97624s] -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205094] New: user is not in the sudoers file
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205094 Bug ID: 1205094 Summary: user is not in the sudoers file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: reiokorn(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- So, after updating tumbleweed, I was no longer able to use the sudo command and got the above error message. NAME="openSUSE Tumbleweed" # VERSION="20221103" It seems the error stems from the revised patch (?): https://build.opensuse.org/request/show/1032755 I was able to get the desired result: = entering the user password instead of root password after adding the apparently previous default settings from my system in yast after the update: https://i.ibb.co/M9JZgpz/Bildschirmfoto-vom-2022-11-04-22-51-13.png https://i.ibb.co/q92JdsP/Bildschirmfoto-vom-2022-11-04-22-51-26.png works as expected, asks for user password now instead of root.... So if that's the intention, the patch needs to be revised again. -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1199661] Autoload amd-pstate CPU Performance Scaling Driver
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1199661 https://bugzilla.suse.com/show_bug.cgi?id=1199661#c18 Giovanni Gherdovich <giovanni.gherdovich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(reiokorn@tutanota | |.com) | --- Comment #18 from Giovanni Gherdovich <giovanni.gherdovich(a)suse.com> --- Closing as per comment 17. Thanks Takashi and Boris for helping the user out. The commit fixing this problem is fbd74d16890b9f5d08ea69b5282b123c894f8860 (" ACPI: CPPC: Fix enabling CPPC on AMD systems with shared memory") from Linux v5.19, which has now been available on Tumbleweed for a while. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205090] New: --no-color argument does not completely remove ANSI codes from the output of Zypper
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205090 Bug ID: 1205090 Summary: --no-color argument does not completely remove ANSI codes from the output of Zypper Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: dobiwad221(a)hoxds.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Passing --no-color option removes colors but leaves some ANSI codes in the output. They should be completely removed as the intent of passing --no-color is clear: no extra characters should appear in the output. Example with --no-color: Retrieving: desktop-translations-84.87.20220427.80cb897f-150400.1.3.noarch.rpm ........<22%>==================================================[\\ (1018.4 KiB/s)]��[2K ��[2K -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1204929] dracut-pre-udev complains about missing group rpc:rpc
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204929 https://bugzilla.suse.com/show_bug.cgi?id=1204929#c14 Antonio Feijoo <antonio.feijoo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #14 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- Ok, let's give it a try. A test package can be downloaded here: https://download.suse.de/ibs/home:/afeijoo:/branches:/SUSE:/SLE-15-SP4:/Upd… Can anyone test this using the installation media? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204929] dracut-pre-udev complains about missing group rpc:rpc
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204929 https://bugzilla.suse.com/show_bug.cgi?id=1204929#c13 --- Comment #13 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Antonio Feijoo from comment #12) > (In reply to Thomas Blume from comment #11) > > So, most probably the chown shouldn't be necessary. > > > > I case of: > > > > https://bugzilla.suse.com/show_bug.cgi?id=1177461#c39 > > > > it seems that /run/rpcbind was already present with wrong permissions. > > So, I guess an "rm -rf /run/rpcbind" instead of a chown in the initrd would > > do. > > Thanks Thomas. The /run/rpcbind directory is created by root in the initrd > (see comment #6 - > https://github.com/dracutdevs/dracut/blob/master/modules.d/95nfs/nfs-start- > rpc.sh#L10-L14), that's why the chown is done after. > Then, IIUC we can avoid the mkdir and the chown, because rpcbind will create > /run/rpcbind if it does not exist, right? Yes, the change came in 2016: --> commit 2e78e6fb51292fea798355e5cb749dbc1de26ca6 Author: NeilBrown <neilb(a)suse.com> Date: Wed Nov 16 10:53:07 2016 -0500 Move default state-dir to a subdirectory of /var/run --< that should cover all dracut versions we maintain. > And, does the same apply to the /var/lib/rpcbind directory (see > https://github.com/dracutdevs/dracut/blob/master/modules.d/95nfs/parse- > nfsroot.sh#L126-L128), could we skip that mkdir & chown? At least for SUSE that directory is obsolete: --> ------------------------------------------------------------------- Sat Nov 12 21:19:10 CET 2016 - kukuk(a)suse.de - Move /var/lib/rpcbind to /run/rpcbind, data should not survive reboot and this makes read-only root filesystem easier. --< and there is no code in rpcbind to create it. Still, it might be present on other distros. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204786] Boot is hanging when intel Ethernet Controller I225-LM [8086:15f2] is enabled
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204786 https://bugzilla.suse.com/show_bug.cgi?id=1204786#c12 --- Comment #12 from Bechir BEN KAHLA <bechir.kahla(a)suse.com> --- Created attachment 862688 --> https://bugzilla.suse.com/attachment.cgi?id=862688&action=edit ethernet_nic_hang_issue_sysrq_logs Hello please find attached the requested logs. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201015] New: transactional-update can't run with selinux=permissive under cloud-init
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201015 Bug ID: 1201015 Summary: transactional-update can't run with selinux=permissive under cloud-init 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: fcrozat(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On openSUSE MicroOS, openstack flavor, I can't run transactional-updates from cloud-init when SELinux is in enforcing mode: type=USER_AVC msg=audit(1656516575.658:44): pid=565 uid=483 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_return dest=:1.15 spid=1393 tpid=1392 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:system_r:cloud_init_t:s0 tclass=dbus permissive=0 exe="/usr/bin/dbus-daemon" sauid=483 hostname=? addr=? terminal=?' -- You are receiving this mail because: You are on the CC list for the bug.

1 4