September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1040171] Widget Inspector (YDialogSpy) lacks a way to be closed in installer.
by bugzilla_noreply＠suse.com 24 Sep '21

24 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1040171 https://bugzilla.suse.com/show_bug.cgi?id=1040171#c4 Ladislav Slez�k <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Ladislav Slez�k <lslezak(a)suse.com> --- This has been actually fixed some time ago, I have added File->Close menu item in the dialog inspector. See https://github.com/libyui/libyui/commit/830deb857d6f2626b0a287796f625f2af21… Closing the bug... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190813] [Build 20210921] SELINUX: command not found
by bugzilla_noreply＠suse.com 24 Sep '21

24 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190813 https://bugzilla.suse.com/show_bug.cgi?id=1190813#c3 Michal Filka <mfilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers(a)suse.de |jsikes(a)suse.com --- Comment #3 from Michal Filka <mfilka(a)suse.com> --- Reassigning to the augeas maintainer. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190650] New: Cannot build SLE15-SP3 with osc since d9a1357edd73 ("rpm: Define $certs as rpm macro (bsc#1189841)").
by bugzilla_noreply＠suse.com 24 Sep '21

24 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190650 Bug ID: 1190650 Summary: Cannot build SLE15-SP3 with osc since d9a1357edd73 ("rpm: Define $certs as rpm macro (bsc#1189841)"). Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: gleep(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- To reproduce: scripts/tar-up.sh scripts/osc_wrapper build --clean kernel-source/kernel-default.spec or that + --alternative-project=Kernel:SLE15-SP3 result: ... [ 1717s] Signing certificates [ 1717s] + certs=() [ 1717s] + test y = y [ 1717s] + for f in /home/abuild/rpmbuild/SOURCES/.kernel_signing_certs/*.crt [ 1717s] + mkdir -p /home/abuild/rpmbuild/BUILDROOT/kernel-default-5.3.18-0.g316993b.x86_64/etc/uefi/certs [ 1717s] + cp -v '/home/abuild/rpmbuild/SOURCES/.kernel_signing_certs/*.crt' /home/abuild/rpmbuild/BUILDROOT/kernel-default-5.3.18-0.g316993b.x86_64/etc/uefi/certs [ 1717s] cp: cannot stat '/home/abuild/rpmbuild/SOURCES/.kernel_signing_certs/*.crt': No such file or directory [ 1717s] error: Bad exit status from /var/tmp/rpm-tmp.Qthsdz (%install) Reverting the rpm/kernel-binary.spec.in bits fixes it up for me, but that's clearly not a proper solution. Do external builders have to pass another arg to osc_wrapper or do some .oscrc configuration changes after that commit? Note: I'm running Leap-15.3, I'm filing this bug against it because SLE15-SP3 is its kernel (shrug). What I want to build is actually my local SLE15-SP3-RT, which precedes the export of the SUSE SLE15-SP3-RT branch by a lot, and which I of course consider superior, me being its 'mom' ;-) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1186500] Salt version bump to 3003
by bugzilla_noreply＠suse.com 24 Sep '21

24 Sep '21

1 0

[Bug 1190838] Unable to Disable qgroup without errors
by bugzilla_noreply＠suse.com 24 Sep '21

24 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190838 https://bugzilla.suse.com/show_bug.cgi?id=1190838#c1 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jshand2013(a)gmail.com Flags| |needinfo?(jshand2013@gmail. | |com) --- Comment #1 from Lukas Ocilka <locilka(a)suse.com> --- Would you mind sharing more details please? Such as: which tool you have used for that, how did you actually do it, what you had in fstab before? If you used YaST, please attach YaST logs. See https://en.opensuse.org/openSUSE:Report_a_YaST_bug for more information. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182850] Create homedirectories with stricter permissions
by bugzilla_noreply＠suse.com 24 Sep '21

24 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1182850 https://bugzilla.suse.com/show_bug.cgi?id=1182850#c11 --- Comment #11 from Johannes Segitz <jsegitz(a)suse.com> --- great, thank you very much -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190844] New: on some hardware dhclient is broken since TW 20210920
by bugzilla_noreply＠suse.com 24 Sep '21

24 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190844 Bug ID: 1190844 Summary: on some hardware dhclient is broken since TW 20210920 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: Mathias.Homann(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have two systems running tumbleweed with DHCP network connections handled by NetworkManager. On one of them it works, on the other dhclient does not even send out dhcp requests. Replacing dhclient with udhcpc in NetworkManager.conf works as a working workaround. The "hanging" dhclient shows as stuck in a futex() call when I look at it with strace - and when it does that it does not even send out dhcp discover packets, or at least I don't see any with tcpdump on the same host. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190817] Error: Subprocess failed. Error: RPM failed: warning: Found BDB Packages database while attempting ndb backend: using bdb_ro backend.
by bugzilla_noreply＠suse.com 24 Sep '21

24 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190817 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |libzypp QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190843] New: Changing from wicked to NetworkManager via Yast Network fails, reverts to wicked
by bugzilla_noreply＠suse.com 24 Sep '21

24 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190843 Bug ID: 1190843 Summary: Changing from wicked to NetworkManager via Yast Network fails, reverts to wicked 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: Network Assignee: screening-team-bugs(a)suse.de Reporter: account.a+opensuse(a)thingamajig.xyz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Recent install of 15.3. Seems to mimic #1185524 fixed in TW. My PSK does contain a "#" character. Other machine still on 15.2 has no issue with same SSID and PSK. Bug presented itself after clean install of 15.3 using yast, even before first boot to desktop. Continues to happen any time using yast2 to try and switch from wicked to NetworkManager. Throws error and reverts back to wicked. Similar to comments in #1185524, I can enable and disable NetworkManager service directly, only fails when using yast2. Was encouraged on opensuse forums to file bug report and reference https://github.com/hercules-team/augeas/pull/723 and ask if this change can be backported to 15.3. Full text of message: Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Caller: /usr/lib64/ruby/gems/2.5.0/gems/cfa-1.0.2/lib/cfa/augeas_parser.rb:461:in `report_activity_error!' Details: Augeas serializing error: Failed to match tree under /store/wifi-security { "key-mgmt" = "wpa-psk" } { "auth-alg" = "open" } { "psk" = "[REDACTED BUT CONTAINS A '#' CHARACTER]" } with pattern ( { /[.0-9A-Z_a-z-]+([].0-9@-[_a-z-]+)?/ = /(([^\t\n\r #][^\n\r#]*[^\t\n\r #]|[^\t\n\r #]))?/ } | { /#comment/ = /[^\t\n\r ].*[^\t\n\r ]|[^\t\n\r ]/ } | { })* for /etc/NetworkManager/system-connections/REDACTED.nmconnection with lens /usr/share/augeas/lenses/dist/inifile.aug:459.27-460.17: -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1177276] New: parted clears some partition attribute flags on GPT
by bugzilla_noreply＠suse.com 24 Sep '21

24 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1177276 Bug ID: 1177276 Summary: parted clears some partition attribute flags on GPT Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: aschnell(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- parted clears some partition attribute flags (NoBlockIOProtocol, Bit 48-63) on GPT even if not instructed to do so, e.g. when creating an additional partition. Even modifying a flag, e.g. by using 'parted /dev/sdX set 1 hidden on', the bits 48-63 are cleared. The UEFI standard states that this must not happen. -- You are receiving this mail because: You are on the CC list for the bug.

1 6