May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1177153] Yast2 gpmc won't launch
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1177153 https://bugzilla.suse.com/show_bug.cgi?id=1177153#c9 Jonathan Rivrain <jrivrain(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #9 from Jonathan Rivrain <jrivrain(a)suse.com> --- Yast2-gpmc does not appear to be shipped in leap 15.5 anymore. Verified with 1.5.x, see comment #8. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221361] New: /etc/profile.d/alljava.csh sets JAVA_HOME incorrectly
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221361 Bug ID: 1221361 Summary: /etc/profile.d/alljava.csh sets JAVA_HOME incorrectly Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: pkeller(a)globalphasing.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- /etc/profile.d/alljava.csh contains the following assignment: setenv JAVA_HOME $ALTERNATIVES_JAVAC_LINK:h:h setenv JAVA_HOME $JAVA_HOME/bin This is clearly incorrect, and makes some Java applications fail to start. Looking at the corresponding Bourne-shell file for comparison, the second of these two assignments is obviously intended to be: setenv JAVA_BINDIR $JAVA_HOME/bin -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1202351] dracut: remove mkinitrd wrapper
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1202351 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guillaume.gardet(a)arm.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225608] [Build 20240528] podman fails stopping containers
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225608 https://bugzilla.suse.com/show_bug.cgi?id=1225608#c7 --- Comment #7 from Dan Čermák <dcermak(a)suse.com> --- (In reply to Christian Boltz from comment #6) > The workaround SR was accepted. > > Dan, do you have an idea when the updated profile from > https://github.com/containers/common/pull/2004 will reach Tumbleweed so that > I can re-enable the podman, runc and crun profiles? The PR is part of podman 5.1.0: https://build.opensuse.org/request/show/1177691 buildah is another consumer, where it has been fixed in version 1.36 (already in Factory). I think a few other projects bundle c/common as well (e.g. skopeo), but they _shouldn't_ be actually running containers. So I hope it is fine to re-enable the profiles -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225608] New: [Build 20240528] podman fails stopping containers
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225608 Bug ID: 1225608 Summary: [Build 20240528] podman fails stopping containers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4231922/modules/imag e_podman/steps/135 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation [33mWARN[0m[0010] StopSignal SIGTERM failed to stop container refreshed in 10 seconds, resorting to SIGKILL Error: cannot remove container 0ad926609982c5d30942986803f1c16b5f9efdbd362c13d9a68d4bb62b5d3783 as it could not be stopped: given PID did not die within timeout 7wkFv-125- openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-containers_image@64bit fails in [image_podman](https://openqa.opensuse.org/tests/4231922/modules/image_podma… ## Test suite description Maintainer: dheidler. Extra tests about CLI software in container module 2023-08-10/dimstar: added QEMURAM=2048 (boo#1212824) ## Reproducible Fails since (at least) Build [20240527](https://openqa.opensuse.org/tests/4226902) ## Expected result Last good: [20240524](https://openqa.opensuse.org/tests/4221615) (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 8

[Bug 1225729] Updating from tumbleweed 20240418 makes overall graphics performance worse on amdgpu
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225729 https://bugzilla.suse.com/show_bug.cgi?id=1225729#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com Flags| |needinfo?(piotrus3g(a)gmail.c | |om) --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- Please try booting the older kernel first and check whether performance is back to the previous level. If not, please try downgrading Mesa, or rollback to the old snapshot and try upgrading mesa. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223152] New: Package openssl-3 built with gcc14 does not pass its testsuite and the build therefore fails
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223152 Bug ID: 1223152 Summary: Package openssl-3 built with gcc14 does not pass its testsuite and the build therefore fails 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: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de CC: otto.hollmann(a)suse.com, rguenther(a)suse.com Blocks: 1220574 Target Milestone: --- Found By: --- Blocker: --- Package openssl-3, when built with with gcc14, spins infinitely (probably) in its testsuite and the build therefore fails: https://build.opensuse.org/package/live_build_log/home:rguenther:plgrnd/ope… This can be reproduced locally with: oosc build --clean --alternative-project home:rguenther:nextgcc The failure may be a genuine miscompilation, it goes away when LTO is disabled or when we disable identical code folding (ICF) using: %global optflags %{optflags} -fno-ipa-icf I have also tried disabling strict aliasing in a similar fashion, but that did not work. On the other hand, the issue seems to be brought in by our patches, I could reproduce the issue outside of an osc chroot when I applied all the patches from the package too but the issue did not reproduce when I did not. Unfortunately I was not quite able to pin it to a single patch, partly because that part of the spec file is somewhat complicated, partly probably because I quickly confused myself. It would be nice to figure out what exactly is going on and runs differently with gcc14 and its ICF. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225709] tik mounts the wrong path onto usb sticks installations
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225709 https://bugzilla.suse.com/show_bug.cgi?id=1225709#c5 --- Comment #5 from Martin Abele <happymab.dev(a)outlook.com> --- I can see in the code where it happens. I guess it would be possible to use another character as delimiter to fix the issue if the decision is to allow USB connected devices. Allowing USB devices like external SSD's would make testing the things a lot easier for people like me who have only one laptop with one hard drive. But testing is not the goal of Aeon. Aeon should be idiot-proof. An elegant solution could be to allow USB devices for testing by a configuration entry or when debug is set. If this is easy enough to implement. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225406] New: One KDE system tray entry is an empty space without an entry until a new entry appears
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225406 Bug ID: 1225406 Summary: One KDE system tray entry is an empty space without an entry until a new entry appears Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: piotrus3g(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: openSUSE Tumbleweed 20240524 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.1-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82SG System Version: IdeaPad 5 15ABA7 Issue description: After logging in to Plasma, system tray has blank space between the entries and the show hidden icons arrow button. It looks like it's reserved space for one entry, but there is no entry and right clicking on it shows the same options as for right clicking the show hidden icons arrow. When some new entry appears (clipboard entry for example), the blank space disappears and it looks properly. When the new entry disappears, the blank space doesn't appear again. The problem returns in every new Plasma session. Additional information: The issue happens only on one of my tumbleweed systems. It also doesn't appear on Wayland on the problematic system. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1225709] tik mounts the wrong path onto usb sticks installations
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225709 https://bugzilla.suse.com/show_bug.cgi?id=1225709#c3 Martin Abele <happymab.dev(a)outlook.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |happymab.dev(a)outlook.com --- Comment #3 from Martin Abele <happymab.dev(a)outlook.com> --- Created attachment 875244 --> https://bugzilla.suse.com/attachment.cgi?id=875244&action=edit tik.log of installation atempt on USB-SSD I had an SSD with Aeon RC1 installed and tried to migrate to RC2. The installation failed. The log is attached. It seems to be the same issue with using ":" as a delimiter to slice lsblk output. -- You are receiving this mail because: You are on the CC list for the bug.

1 0