April 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1096241] New: [opensuse][tumbleweed][20180603][liveCD/rescue] Shutdown takes too much time when lvmetad doesn't respond to SIGKILL
by bugzilla_noreply＠novell.com 19 Apr '21

19 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1096241 Bug ID: 1096241 Summary: [opensuse][tumbleweed][20180603][liveCD/rescue] Shutdown takes too much time when lvmetad doesn't respond to SIGKILL Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: slindomansilla(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 772682 --> http://bugzilla.opensuse.org/attachment.cgi?id=772682&action=edit shutdown-log-timed-out.txt Similar issue was found a long time ago on ArchLinux and Redhat: - https://bugs.archlinux.org/task/52249 - https://bugzilla.redhat.com/show_bug.cgi?id=1152185 My questions here are: - Why do we need this process running on liveCD? - If we don't need it, can we remove it from the liveCD? - If not, how can we avoid that users get that problem? System hung when shutting down (notice 2154.900545 -> 2244.901945): [ 2154.897657] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [ 2154.900537] systemd-journald[6847]: Received SIGTERM from PID 1 (systemd-shutdow). [ 2154.900545] systemd-journald[6847]: systemd-journald stopped as pid 6847 [ 2244.901945] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 2244.907601] systemd-shutdown[1]: Sending SIGKILL to PID 731 (lvmetad). System not hung when shutting down (notice 2012.262209 -> 2012.314146): [ 2012.259513] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [ 2012.262200] systemd-journald[6792]: Received SIGTERM from PID 1 (systemd-shutdow). [ 2012.262209] systemd-journald[6792]: systemd-journald stopped as pid 6792 [ 2012.314146] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 2012.317239] systemd-shutdown[1]: Unmounting file systems. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1096241] [opensuse][tumbleweed][20180603][liveCD/rescue] Shutdown takes too much time when lvmetad doesn't respond to SIGKILL
by bugzilla_noreply＠suse.com 19 Apr '21

19 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1096241 https://bugzilla.suse.com/show_bug.cgi?id=1096241#c53 --- Comment #53 from Oliver Kurz <okurz(a)suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: rescue https://openqa.opensuse.org/tests/1704382 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1164313] [Build 20200218] yast2 nfs-client fails, cannot start rpc-statd.service
by bugzilla_noreply＠suse.com 19 Apr '21

19 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1164313 https://bugzilla.suse.com/show_bug.cgi?id=1164313#c34 --- Comment #34 from Oliver Kurz <okurz(a)suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: yast2_nfs_v3_client https://openqa.opensuse.org/tests/1704370 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1063638] btrfs balance renders system unresponsive and eventually even kills WiFi when quota is enabled - review I/O scheduling parameters of btrfsmaintenance
by bugzilla_noreply＠suse.com 19 Apr '21

19 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1063638 https://bugzilla.suse.com/show_bug.cgi?id=1063638#c255 --- Comment #255 from Oliver Kurz <okurz(a)suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: upgrade_Leap_42.3_kde+system_performance https://openqa.opensuse.org/tests/1702563 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180312] [Build 20201222] rstudio uninstallable
by bugzilla_noreply＠suse.com 19 Apr '21

19 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1180312 https://bugzilla.suse.com/show_bug.cgi?id=1180312#c8 Dan ��erm��k <dcermak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Dan ��erm��k <dcermak(a)suse.com> --- This has been fixed with rstudio 1.4 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177923] [Build 20201019] openQA test fails in rstudio_desktop
by bugzilla_noreply＠suse.com 19 Apr '21

19 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1177923 https://bugzilla.suse.com/show_bug.cgi?id=1177923#c6 Dan ��erm��k <dcermak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Dan ��erm��k <dcermak(a)suse.com> --- This has been fixed a while ago. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184060] New: [Build 20210325] openQA test fails in audit2allow - libsepol.sepol_string_to_security_class: unrecognised class (null)
by bugzilla_noreply＠suse.com 19 Apr '21

19 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184060 Bug ID: 1184060 Summary: [Build 20210325] openQA test fails in audit2allow - libsepol.sepol_string_to_security_class: unrecognised class (null) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1681431/modules/audi t2allow/steps/7 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: jsegitz(a)suse.com Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de CC: llzhao(a)suse.com Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-selinux@64bit fails in [audit2allow](https://openqa.opensuse.org/tests/1681431/modules/audit2allow/… Looks like the relevant issue is "libsepol.sepol_string_to_security_class: unrecognised class (null)" Appears since the recent libselinux.so version bump Could possibly be a test issue (hence llzhao(a)suse.com in CC) but the unrecognised class warning makes me think its more likely a legitimate bug, hence the assignment. ## Test suite description Maintainer (Lily Zhao) llzhao(a)suse.com ## Reproducible Fails since (at least) Build [20210324](https://openqa.opensuse.org/tests/1679362) ## Expected result Last good: [20210321](https://openqa.opensuse.org/tests/1677286) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1184921] New: Please add this TLS patch from Trinity (if applicable)
by bugzilla_noreply＠suse.com 19 Apr '21

19 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184921 Bug ID: 1184921 Summary: Please add this TLS patch from Trinity (if applicable) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: anixx(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please add this patch which enables newer TLS: https://mirror.git.trinitydesktop.org/cgit/tdelibs/patch/?id=adb9d9d2b0bfbb… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1092425] Assertion failure in libclang on i586 (when building qtdoc)
by bugzilla_noreply＠suse.com 18 Apr '21

18 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1092425 http://bugzilla.opensuse.org/show_bug.cgi?id=1092425#c13 Aaron Puchert <aaronpuchert(a)alice-dsl.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aaronpuchert(a)alice-dsl.net --- Comment #13 from Aaron Puchert <aaronpuchert(a)alice-dsl.net> --- (In reply to Michal Srb from comment #4) > I don't know yet why it behaves differently on x86 and x86_64, perhaps it > has something to do with the body of the method, which is different > depending on the architecture. That I can answer: before https://build.opensuse.org/request/show/822399 we were accidentally building LLVM without -DNDEBUG on 32-bit architectures. But I can't say if that's a bug in Clang, it might also be how qtdoc is using it. If you can reproduce the failure with something like "clang -emit-pch" (that runs the same AST serialization), perhaps also -DQ_QDOC it should be worth looking at. Otherwise I suggest we close this bug, chances are that the code has changed so much that the issues today are totally different. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1178637] clazy crashes with libclang11/libLLVM11
by bugzilla_noreply＠suse.com 18 Apr '21

18 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1178637 http://bugzilla.opensuse.org/show_bug.cgi?id=1178637#c6 Aaron Puchert <aaronpuchert(a)alice-dsl.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |christophe(a)krop.fr Flags| |needinfo?(christophe(a)krop.f | |r) --- Comment #6 from Aaron Puchert <aaronpuchert(a)alice-dsl.net> --- Should be fixed, see comment 5. (In reply to Aaron Puchert from comment #3) > Clazy should probably be patched to invoke "clang-XX" > instead of "clang", which is a symlink managed by update-alternatives. You > can get the major version from one of these macros: > > /usr/include/clang/Basic/Version.inc:#define CLANG_VERSION_MAJOR 11 > /usr/include/llvm/Config/llvm-config.h:#define LLVM_VERSION_MAJOR 11 > > One of these headers is probably already included. > > I wonder why it doesn't already do that, the clang-XX executable is built > even in upstream, so it seems like it should be available everywhere. Do we still want to do this? Otherwise I'd suggest to close the bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0