March 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1221770] New: installation problem for package trousers on leap 15.6 beta
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221770 Bug ID: 1221770 Summary: installation problem for package trousers on leap 15.6 beta Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- While I was testing Leap 15.6 beta (630.1-boot) I saw this error in /var/log/zypp history: # 2024-03-15 00:17:14 trousers-0.3.15-150600.7.1.x86_64.rpm installed ok # Additional rpm output: # Group 'mail' not found. Creating the user mailbox file with 0600 mode. # /var/tmp/rpm-tmp.pxRHp2: line 24: /usr/bin/udevadm: No such file or directory # 2024-03-15 00:17:14|install|trousers|0.3.15-150600.7.1|x86_64||openSUSE-Leap-15.6-1|6462c0eebacd6db401e9c14dbcd79d22e914197ef0716fa9bef3a3476715d8c69bdf65b0b5fbc3a43c42be70277bf3f3d00881c6b6fd41bba174b8c77b8941f5| A similar problem was fixed in tumbleweed with SR#1135798 For Leap 15.6 and 15.5 the change in the spec file should be: Requires(pre): pwdutils +Requires(pre): coreutils +Requires(post): udev BuildRoot: %{_tmppath}/%{name}-%{version}-build -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1220820] New: problem with sshfs on leap 15.6 beta
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1220820 Bug ID: 1220820 Summary: problem with sshfs on leap 15.6 beta Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I was testing Leap 15.6 beta and I had a close encounter with boo#1215574. Please update sshfs to version 3.7.4a If interested, I can provide a command sequence that can reproduces the bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217260] New: slib build failed in %post
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217260 Bug ID: 1217260 Summary: slib build failed in %post Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello slib does not build on Leap 15.6. This should be fixed before Beta (Feb 2023). https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.6 Build log from Leap 15.6 https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… [ 26s] ERROR: In procedure open-file: [ 26s] In procedure open-file: No such file or directory: "/usr/share/guile/site/2.2/slibcat" [ 26s] ... running 50-check-binary-kernel-log [ 26s] ... running 50-check-core-files [ 26s] ... checking for core files [ 26s] ... running 50-check-debuginfo [ 26s] ... testing for empty debuginfo packages [ 26s] ... running 50-check-filelist [ 26s] ... checking filelist [ 26s] ... running 50-check-gconf-scriptlets [ 26s] ... testing GConf scriptlet presence [ 26s] ... running 50-check-installtest [ 26s] ... testing for pre/postinstall scripts that are not idempotent [ 27s] Backtrace: [ 27s] 12 (apply-smob/1 #<catch-closure 5638290ba180>) [ 27s] In ice-9/boot-9.scm: [ 27s] 705:2 11 (call-with-prompt ("prompt") #<procedure 5638290d38c0 ?> ?) [ 27s] In ice-9/eval.scm: [ 27s] 619:8 10 (_ #(#(#<directory (guile-user) 563829187140>))) [ 27s] In ice-9/command-line.scm: [ 27s] 181:18 9 (_ #<input: string 563829192a80>) [ 27s] In unknown file: [ 27s] 8 (eval (require (quote new-catalog)) #<directory (guile-?>) [ 27s] In /usr/share/slib/require.scm: [ 27s] 145:16 7 (slib:require new-catalog) [ 27s] 79:15 6 (catalog:get new-catalog) [ 27s] In /usr/share/slib/guile-2.init: [ 27s] 257:4 5 (with-load-pathname _ _) [ 27s] In ice-9/boot-9.scm: [ 27s] 2312:4 4 (save-module-excursion #<procedure 563829261990 at ice-?>) [ 27s] 3832:12 3 (_) [ 27s] In /usr/share/slib/mklibcat.scm: [ 27s] 22:2 2 (_) [ 27s] In ice-9/ports.scm: [ 27s] 461:11 1 (call-with-output-file "/usr/share/guile/site/2.2/slib?" ?) [ 27s] In unknown file: [ 27s] 0 (open-file "/usr/share/guile/site/2.2/slibcat" "w" # #f) [ 27s] [ 27s] ERROR: In procedure open-file: [ 27s] In procedure open-file: No such file or directory: "/usr/share/guile/site/2.2/slibcat" [ 27s] postinstall script of slib-3b7-bp156.2.2.noarch.rpm failed -- You are receiving this mail because: You are on the CC list for the bug.

1 3

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

02 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 4

[Bug 1213148] New: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213148 Bug ID: 1213148 Summary: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: catice567(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since kernel 6.2, my Tumbleweed refuses to boot because of intel isp. Ubuntu had this problem but they fixed it by disabling atomisp. I have a request to the openSUSE kernel maintainers: Can you please disable atomisp in your kernel, especially since this will affect Leap later on next year? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1215323] New: [trackerbug] docker 24.0.6-ce update
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1215323 Bug ID: 1215323 Summary: [trackerbug] docker 24.0.6-ce update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: asarai(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- - Update to Docker 24.0.6-ce. See upstream changelong online at <https://docs.docker.com/engine/release-notes/24.0/#2406>. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213500] New: [trackerbug] docker 24.0.4-ce update
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213500 Bug ID: 1213500 Summary: [trackerbug] docker 24.0.4-ce update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: asarai(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- - Update to Docker 24.0.4-ce. See upstream changelog online at <https://docs.docker.com/engine/release-notes/24.0/#2404>. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1217350] New: Some Electron-based applications are unable to detect dark mode
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217350 Bug ID: 1217350 Summary: Some Electron-based applications are unable to detect dark mode Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: ars2swim(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 870861 --> https://bugzilla.suse.com/attachment.cgi?id=870861&action=edit Visual Studio Code, though preconfigured by default with a dark theme, has a light titlebar, suggesting that Electron detects a light theme in the system. Some Electron-based applications are unable to detect that the system is running with a dark theme, despite dark mode being the default configuration for openSUSE Aeon. This can lead to a lack of UI consistency. I noticed this primarily in apps like Visual Studio Code and Signal. It's worth pointing out that this doesn't occur on every Electron app (namely, the Webcord Flatpak is able to handle theming just fine). I'll also point out that this isn't necessarily an issue with the apps alone or GNOME, because the aforementioned apps--whether packaged as a Flatpak, tarball, or run within a distrobox--do correctly use a dark theme on Ubuntu 23.10. I'm not an expert on SELinux, but it is my best guess as to why this is happening. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213055] New: locale problems in the default distrobox configuration
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213055 Bug ID: 1213055 Summary: locale problems in the default distrobox configuration Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: All OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Distrobox Assignee: rbrown(a)suse.com Reporter: shadenk30011(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Build Identifier: When creating a new container using "distrobox-create" the container fails to display directory names properly. For example the directory named "Stažené" shows up as "'Sta'$'\305\276''en'$'\303\251'" when using ls. Reproducible: Always Steps to Reproduce: 1. Use the czech locale 2. Create a directory inside the home that uses one of the offending symbols 3. Create a new distrobox container and run "ls" Actual Results: Directory name isn't properly displayed. Expected Results: Directory name is properly displayed. A workaround is to install the "glibc-locale" package. This can be automated by adding 'container_additional_packages="glibc-locale"' into the distrobox configuration. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222089] New: open-vm-tools 12.4.0 has been released - please rebase
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222089 Bug ID: 1222089 Summary: open-vm-tools 12.4.0 has been released - please rebase Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: john.wolfe(a)broadcom.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- open-vm-tools 12.4.0 was released on March 21, 2024. There are no new features in the open-vm-tools 12.4.0 release. This is primarily a maintenance release that addresses a single critical problem: For complete details, see: https://github.com/vmware/open-vm-tools/releases/tag/stable-12.4.0 Release Notes are available at: https://github.com/vmware/open-vm-tools/blob/stable-12.4.0/ReleaseNotes.md The granular changes that have gone into the 12.4.0 release are in the ChangeLog at: https://github.com/vmware/open-vm-tools/blob/stable-12.4.0/open-vm-tools/Ch… -- You are receiving this mail because: You are on the CC list for the bug.

1 4