August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1210672] [Build 20230419][Tumbleweed-MicroOS] [SElinux]failed to disable 'chronyd' service due to selinux denied
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1210672 https://bugzilla.suse.com/show_bug.cgi?id=1210672#c8 Johannes Segitz <jsegitz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED --- Comment #8 from Johannes Segitz <jsegitz(a)suse.com> --- Fix already in policy for a year -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228388] [Build 20240728] openQA test fails in kdump_and_crash
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228388 https://bugzilla.suse.com/show_bug.cgi?id=1228388#c4 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|ptesarik(a)suse.com |jslaby(a)suse.com --- Comment #4 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #3) > With the current head of crash, the error is different: > # crash vmcore /usr/lib/modules/6.10.2-2.g65a34e2-default/vmlinux.xz > ... > crash: page excluded: kernel virtual address: ffff9075c042cb90 type: > "xa_node.slots[off]" So this is fixed in makedumpfile: https://github.com/makedumpfile/makedumpfile/commit/bad2a7c4fa75d37a4157844… Pushing... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228621] [Build 9.32] openSUSE agama live installer iso failed to boot for dracut report error and entered emergency mode
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228621 https://bugzilla.suse.com/show_bug.cgi?id=1228621#c4 --- Comment #4 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- (In reply to Lemon Li from comment #3) > Thanks, the first blank caused by the character limit by 3270. I added the > 'rd.debug' to boot parameters, please check the log : > https://openqa.opensuse.org/tests/4372048#step/bootloader_start/30 Thanks, but you also replaced `root=live:...` with `install=...` on the kernel command line, so now the livenet module is not being used and the part of the code throwing a syntax error is not being reached. https://openqa.opensuse.org/tests/4372048#step/bootloader_start/21 ``` '[ 0.110206][ T0] Kernel command line: install=ftp://10.150.1.11/agama-inst', 'aller-openSUSE.s390x-9.0.0-openSUSE-Build9. 34 ', ' ip=10.150.1.152::10.150.1.254:24:ope', 'nqanet.opensuse.org:enca00:none cio_ignore=all,!condev,!0.0.0150 nam', 'eserver=10.150.1.11 sshd=1 VNC=1 rd.zdev=qeth,0.0.0A00:0.0.0A01:0.0.0', 'A02,layer2=0,portno=0 rd.debug HostIP=10.150.1.153/24 rd.zdev=dasd,', '0.0.0150 VNCPassword=nots3cr3t sshpassword=nots3cr3t hostname=o3zvm', '003 Hostname=o3zvm004 ', ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228177] New: openblas: records build machine CPU type
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228177 Bug ID: 1228177 Summary: openblas: records build machine CPU type Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: eich(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, (sponsored by the NLnet NGI0 fund), I found that our openblas binaries record the build machine CPU type in openblas.pc: --- old//usr/lib64/openblas-serial/pkgconfig/openblas.pc +++ new//usr/lib64/openblas-serial/pkgconfig/openblas.pc @@ -3,7 +3,7 @@ libnamesuffix= libsuffix= includedir=/usr/include/openblas -openblas_config= USE_64BITINT= DYNAMIC_ARCH=1 DYNAMIC_OLDER= NO_CBLAS= NO_LAPACK= NO_LAPACKE= NO_AFFINITY=1 USE_OPENMP=0 HASWELL MAX_THREADS=64 +openblas_config= USE_64BITINT= DYNAMIC_ARCH=1 DYNAMIC_OLDER= NO_CBLAS= NO_LAPACK= NO_LAPACKE= NO_AFFINITY=1 USE_OPENMP=0 UNKNOWN MAX_THREADS=64 version=0.3.27 extralib=-lm -lgfortran -lm -lgfortran Name: openblas -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1228691] New: YaST2 cannot display Chinese characters properly.
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228691 Bug ID: 1228691 Summary: YaST2 cannot display Chinese characters properly. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: poplar.cubic(a)gmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- When installing openSUSE Tumbleweed on a UEFI-booted device and selecting a language, Chinese, Japanese, and other CJK characters are displayed as garbled characters. This problem can be alleviated by editing the installed grub boot entry, adding lang=zh_CN to the end of the linux line, and then pressing Ctrl + X to make YaST2 display Chinese normally. The above issues do not affect devices booted using legacy BIOS and Leap ISO. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1212963] AUDIT-0: review of selinux policy for kanidm-unixd tools and clients
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1212963 https://bugzilla.suse.com/show_bug.cgi?id=1212963#c5 William Brown <william.brown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(william.brown@sus | |e.com) | --- Comment #5 from William Brown <william.brown(a)suse.com> --- (In reply to Johannes Segitz from comment #4) > so that has been going on for a while ... > > William, did you have a chance to test the latest state I build for you in > my repos? I would like to get this in our main policy ASAP Sorry for the late response. I did try it and it mostly seemed to work. I say we merge and then refine as we go :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228245] Tumbleweed: rng-tools.service start fails with unrecognized option '--fill-watermark=3700'
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228245 https://bugzilla.suse.com/show_bug.cgi?id=1228245#c3 --- Comment #3 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1228245) was mentioned in https://build.opensuse.org/request/show/1190829 Factory / rng-tools -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202444] Please, update eclipse-swt
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1202444 https://bugzilla.suse.com/show_bug.cgi?id=1202444#c2 Saulo Moraes <saulo.a.moraes(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |saulo.a.moraes(a)gmail.com Priority|P5 - None |P4 - Low --- Comment #2 from Saulo Moraes <saulo.a.moraes(a)gmail.com> --- I can confirm it still a problem, the eclipse-swt is not working properly as it is missing deps. SWT depends from 'libgthread-2.0.so' that is not been installed with eclipse-swt, and it is causing the problem, unfortunately the error output is not clear. Currently eclipse-swt is useless without correct deps, and most of people are probably installing 'libgthread' as a dep from other packages... Reference for the fix: https://forums.opensuse.org/t/latest-eclipse-crashing-in-opensuse-tumblewee… LOGS: !SESSION 2024-07-31 20:37:46.460 ----------------------------------------------- eclipse.buildId=4.32.0.20240606-1231 java.version=21.0.3 java.vendor=Eclipse Adoptium BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product !ENTRY ch.qos.logback.classic 1 0 2024-07-31 20:37:49.706 !MESSAGE Activated before the state location was initialized. Retry after the state location is initialized. !ENTRY org.eclipse.osgi 4 0 2024-07-31 20:37:50.162 !MESSAGE Application error !STACK 1 java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: no swt-pi4-gtk-4965r11 in java.library.path: /usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib no swt-pi4-gtk in java.library.path: /usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib no swt-pi4 in java.library.path: /usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib Can't load library: /home/saulo/.swt/lib/linux/x86_64/libswt-pi4-gtk-4965r11.so Can't load library: /home/saulo/.swt/lib/linux/x86_64/libswt-pi4-gtk.so Can't load library: /home/saulo/.swt/lib/linux/x86_64/libswt-pi4.so at org.eclipse.swt.internal.Library.loadLibrary(Library.java:345) at org.eclipse.swt.internal.Library.loadLibrary(Library.java:254) at org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:97) at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:209) at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:155) at org.eclipse.swt.widgets.Display.<clinit>(Display.java:170) at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:721) at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:185) at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:182) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:208) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:143) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:109) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:439) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:271) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:668) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:605) at org.eclipse.equinox.launcher.Main.run(Main.java:1481) at org.eclipse.equinox.launcher.Main.main(Main.java:1454) -- You are receiving this mail because: You are on the CC list for the bug.

1 0