October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1228797] New: python3-schema and python3-daemon not available with sle-module-pythons
by bugzilla_noreply＠suse.com 06 Mar '25

06 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1228797 Bug ID: 1228797 Summary: python3-schema and python3-daemon not available with sle-module-pythons Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: egotthold(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am attempting to build cobbler-tftp here [1]. This is failing due to two dependencies not being enabled for sle-module-pythons. I would desire that sle15allpythons is used so the package builds for both 3.6 and 3.11. Both versions in Leap are available at the moment with 3.6 and are compatible with it. [1]: https://build.opensuse.org/package/show/systemsmanagement:cobbler:release34… -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1218120] New: jetty-artifact-remote-resources: reproducible builds issue
by bugzilla_noreply＠suse.com 06 Mar '25

06 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1218120 Bug ID: 1218120 Summary: jetty-artifact-remote-resources: reproducible builds issue Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: fstrba(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, I found that our jetty-artifact-remote-resources varies from filesystem-readdir-order. It probably needs an extra sort somewhere. example diff is --- old//usr/share/java/jetty-artifact-remote-resources/jetty-artifact-remote-resources.jar/META-INF/maven/remote-resources.xml +++ new//usr/share/java/jetty-artifact-remote-resources/jetty-artifact-remote-resources.jar/META-INF/maven/remote-resources.xml @@ -3,9 +3,9 @@ xmlns="http://maven.apache.org/remote-resources/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <remoteResources> - <remoteResource>about.html</remoteResource> - <remoteResource>META-INF/LICENSE</remoteResource> <remoteResource>META-INF/NOTICE.txt</remoteResource> + <remoteResource>META-INF/LICENSE</remoteResource> + <remoteResource>about.html</remoteResource> </remoteResources> <sourceEncoding>UTF-8</sourceEncoding> </remoteResourcesBundle> jetty-distribution-remote-resources is also affected. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1229122] New: go1.23 release tracking
by bugzilla_noreply＠suse.com 05 Mar '25

05 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1229122 Bug ID: 1229122 Summary: go1.23 release tracking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- go1.23 (expected August 2024) is a major release of Go. Minor releases of go1.23.x will be provided through August 2025. This issue tracks go1.23.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1231134] New: [Build 39.1] openQA test fails in boot_agama Agama Leap installer on ppc64le
by bugzilla_noreply＠suse.com 03 Mar '25

03 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1231134 Bug ID: 1231134 Summary: [Build 39.1] openQA test fails in boot_agama Agama Leap installer on ppc64le Classification: openSUSE Product: openSUSE Distribution Version: Leap 16.0 Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: jose.fernandez1(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877660 --> https://bugzilla.suse.com/attachment.cgi?id=877660&action=edit screenshot of the issue ## Observation openQA test in scenario opensuse-16.0-agama-installer-Leap-ppc64le-agama_default@ppc64le fails in [boot_agama](https://openqa.opensuse.org/tests/4522313/modules/boot_agama/st… ## Test suite description This test deploy and boot Agama-installer ISO, after that it performs an automatic system installation with default configuration. ## Reproducible Fails since (at least) Build [38.4](https://openqa.opensuse.org/tests/4511095) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64le&distri=opensu… Please see the attached screenshot of the issue, thanks. Additional information, https://openqa.opensuse.org/tests/4522313 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1228081] New: "systemd-cryptsetup-generator[2606]: Assertion 'i->idx > 0' failed at src/basic/hashmap.c" messages spewed on tty when systemd is updated
by bugzilla_noreply＠suse.com 03 Mar '25

03 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1228081 Bug ID: 1228081 Summary: "systemd-cryptsetup-generator[2606]: Assertion 'i->idx > 0' failed at src/basic/hashmap.c" messages spewed on tty when systemd is updated Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876103 --> https://bugzilla.suse.com/attachment.cgi?id=876103&action=edit selectively trimmed zypper up typescript session plus dmesg tail Initial summary: "systemd-cryptsetup-generator[2606]: Assertion 'i->idx > 0' failed at src/basic/hashmap.c" messages spewed on tty when systemd is updated The summary messages have occurred on the tty running zypper up on each recent zypper up of each of my 15.6 installations that included updates to systemd* packages. They are logged in dmesg tail attached, following typescript log of login/zypper up session. Running kernel for the attachment generation was 6.4.0-150600.21.3. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219137] New: qemu user space builds broken with kernel 6.7
by bugzilla_noreply＠suse.com 03 Mar '25

03 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1219137 Bug ID: 1219137 Summary: qemu user space builds broken with kernel 6.7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: schwab(a)suse.de QA Contact: qa-bugs(a)suse.de CC: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Since commit 1c5976ef0f7a the kernel deregisters all binfmt_misc handler when the binfmt_misc filesystem is unmounted. The build script has this: # RPM specific post checks are in /usr/lib/build/checks if test -n "$RPMS" -a -d "$BUILD_ROOT/usr/lib/build/checks" ; then # workaround for broken 13.1 check scripts which umount /proc if test -n "$RUNNING_IN_VM" -a "$BUILD_ROOT" = / ; then umount -n $BUILD_ROOT/proc/sys/fs/binfmt_misc 2>/dev/null fi This means that after this point the emulation no longer works. [ 272s] ... checking for files with abuild user/group [ 272s] /.build/build: line 1922: /bin/env: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error [ 272s] /.build/build: line 1926: /bin/rpm: cannot execute binary file: Exec format error According to the commit, this should be reported as a regression so that this behaviour is reverted for the initial binfmt_misc mount. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1212954] New: amdgpu: Monitor displaying wrong resolution
by bugzilla_noreply＠suse.com 03 Mar '25

03 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1212954 Bug ID: 1212954 Summary: amdgpu: Monitor displaying wrong resolution Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: holgi(a)suse.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867944 --> https://bugzilla.suse.com/attachment.cgi?id=867944&action=edit IMG_20230703_164538751_HDR.jpg Having a 4K monitor (SAMSUNG LU28R55) attached to the docking station of my ThinkPad via HDMI I can easily 1:1 mirror the screen output of the laptop and the monitor with openSUSE Leap 15.4. Doing the same with openSUSE Leap 15.5 will result in monitor displaying a resolution 1980x2160 instead of the set 1980x1080. Using a 4x different screen (Philips) is working fine. Photo of monitor attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 30

[Bug 1224995] New: Native Firefox package on Plasma Wayland runs the KDE File Picker under XWayland, not respecting HDPI scaling
by bugzilla_noreply＠suse.com 03 Mar '25

03 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1224995 Bug ID: 1224995 Summary: Native Firefox package on Plasma Wayland runs the KDE File Picker under XWayland, not respecting HDPI scaling Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: radicalite(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875025 --> https://bugzilla.suse.com/attachment.cgi?id=875025&action=edit Filepicker comparsion between Native Firefox on TW and Flatpak Firefox When using the file picker from the native Firefox package, the file picker runs in XWayland, this isn't noticeable on non HiDPI displays unless there's a HiDPI display connected, or are simply using a HiDPI screen as the only screen, then this becomes instantly noticeable. This behaviour isn't consistent with applications from the rest of the system (moving aside VLC, but the app itself runs entirely under XWayland by default...), as they run the file picker under Wayland, following the correct scaling setting. the Firefox flatpak also runs the file picker under Wayland correctly (via Portal). This behaviour also doesn't happen with the native Firefox package on TWGNOME, running the GTK file picker under Wayland with respect to scaling, so I assume this happens from the OpenSUSE KDE patches added to Firefox? Install is a fresh TWKDE install. Comparison in image Operating System: openSUSE Tumbleweed 20240520 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: Wayland Processors: 4 × Intel® Core™ i5-6267U CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® Iris® Graphics 550 Manufacturer: Apple Inc. Product Name: MacBookPro13,2 System Version: 1.0 Display config is 2560x1600@175%@60hz (Built-in Screen) set to left 1920x1080@100%@120hz (Acer Technologies VG242Y) set to right, set as primary display. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214189] New: vdpauinfo segfaults and coredumps
by bugzilla_noreply＠suse.com 02 Mar '25

02 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1214189 Bug ID: 1214189 Summary: vdpauinfo segfaults and coredumps Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: carlos.e.r(a)opensuse.org QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868762 --> https://bugzilla.suse.com/attachment.cgi?id=868762&action=edit tar file with the strace files Derives from Bug 1210427 Machine is a Lenovo Laptop, Lenovo L14 Gen3 that I bought this year. Laicolasse:~/tmp/2 # strace --output=vdpauinfo.strace --follow-forks --output-separately vdpauinfo display: :0.0 screen: 0 API version: 1 Information string: G3DVL VDPAU Driver Shared Library version 1.0 Video surface: name width height types ------------------------------------------- 420 16384 16384 NV12 YV12 422 16384 16384 UYVY YUYV 444 16384 16384 Y8U8V8A8 V8U8Y8A8 Decoder capabilities: name level macbs width height ---------------------------------------------------- MPEG1 --- not supported --- MPEG2_SIMPLE 3 65536 4096 4096 MPEG2_MAIN 3 65536 4096 4096 H264_BASELINE --- not supported --- H264_MAIN --- not supported --- H264_HIGH --- not supported --- VC1_SIMPLE --- not supported --- VC1_MAIN --- not supported --- VC1_ADVANCED --- not supported --- MPEG4_PART2_SP 3 65536 4096 4096 MPEG4_PART2_ASP 5 65536 4096 4096 DIVX4_QMOBILE --- not supported --- DIVX4_MOBILE --- not supported --- DIVX4_HOME_THEATER --- not supported --- DIVX4_HD_1080P --- not supported --- DIVX5_QMOBILE --- not supported --- DIVX5_MOBILE --- not supported --- DIVX5_HOME_THEATER --- not supported --- DIVX5_HD_1080P --- not supported --- H264_CONSTRAINED_BASELINE --- not supported --- H264_EXTENDED --- not supported --- H264_PROGRESSIVE_HIGH --- not supported --- H264_CONSTRAINED_HIGH --- not supported --- H264_HIGH_444_PREDICTIVE --- not supported --- HEVC_MAIN --- not supported --- HEVC_MAIN_10 --- not supported --- HEVC_MAIN_STILL --- not supported --- HEVC_MAIN_12 --- not supported --- HEVC_MAIN_444 --- not supported --- Output surface: name width height nat types ---------------------------------------------------- B8G8R8A8 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 I8A8 R8G8B8A8 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 I8A8 R10G10B10A2 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 I8A8 B10G10R10A2 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 I8A8 Bitmap surface: name width height ------------------------------ B8G8R8A8 16384 16384 R8G8B8A8 16384 16384 R10G10B10A2 16384 16384 B10G10R10A2 16384 16384 A8 16384 16384 Video mixer: feature name sup ------------------------------------ DEINTERLACE_TEMPORAL y DEINTERLACE_TEMPORAL_SPATIAL - INVERSE_TELECINE - NOISE_REDUCTION y SHARPNESS y LUMA_KEY y HIGH QUALITY SCALING - L1 y HIGH QUALITY SCALING - L2 - HIGH QUALITY SCALING - L3 - HIGH QUALITY SCALING - L4 - HIGH QUALITY SCALING - L5 - HIGH QUALITY SCALING - L6 - HIGH QUALITY SCALING - L7 - HIGH QUALITY SCALING - L8 - HIGH QUALITY SCALING - L9 - parameter name sup min max ----------------------------------------------------- VIDEO_SURFACE_WIDTH y 48 4096 VIDEO_SURFACE_HEIGHT y 48 4096 CHROMA_TYPE y LAYERS y 0 4 attribute name sup min max ----------------------------------------------------- BACKGROUND_COLOR y CSC_MATRIX y NOISE_REDUCTION_LEVEL y 0.00 1.00 SHARPNESS_LEVEL y -1.00 1.00 LUMA_KEY_MIN_LUMA y LUMA_KEY_MAX_LUMA y Segmentation fault (core dumped) Laicolasse:~/tmp/2 # ls vdpauinfo.strace.6031 vdpauinfo.strace.6035 vdpauinfo.strace.6039 vdpauinfo.strace.6043 vdpauinfo.strace.6032 vdpauinfo.strace.6036 vdpauinfo.strace.6040 vdpauinfo.strace.6044 vdpauinfo.strace.6033 vdpauinfo.strace.6037 vdpauinfo.strace.6041 vdpauinfo.strace.6045 vdpauinfo.strace.6034 vdpauinfo.strace.6038 vdpauinfo.strace.6042 Laicolasse:~/tmp/2 # I will attach the trace files in a tar. Laicolasse:~ # coredumpctl TIME PID UID GID SIG COREFILE EXE SIZE Fri 2023-08-11 12:48:59 CEST 6031 0 0 SIGSEGV present /usr/bin/vdpauinfo 2.0M Fri 2023-08-11 12:48:59 CEST 6028 0 0 SIGSEGV none /usr/bin/strace n/a Laicolasse:~ # So relevant file should be vdpauinfo.strace.6031 Laicolasse:~ # inxi -SGaz System: Kernel: 5.14.21-150500.55.12-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.12-default root=UUID=858cc569-e2ae-4d12-adf6-3a06ade8281c security=apparmor no_console_suspend splash=silent resume=/dev/disk/by-label/Swap preempt=full quiet mitigations=auto Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.34 info: xfce4-panel wm: xfwm v: 4.18.0 dm: 1: GDM v: 41.3 2: SDDM note: stopped Distro: openSUSE Leap 15.5 Graphics: Device-1: AMD Barcelo vendor: Lenovo driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 07:00.0 chip-ID: 1002:15e7 class-ID: 0300 temp: 46.0 C Device-2: Luxvisions Innotech Integrated RGB Camera type: USB driver: uvcvideo bus-ID: 3-3.2:4 chip-ID: 30c9:0050 class-ID: fe01 serial: <filter> Display: server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.5 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93") Monitor-1: eDP-1 mapped: eDP model: AU Optronics 0x639c built: 2021 res: 1920x1080 hz: 60 dpi: 158 gamma: 1.2 size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9 modes: max: 1920x1080 min: 640x480 API: OpenGL v: 4.6 Mesa 22.3.5 renderer: AMD Radeon Graphics (renoir LLVM 15.0.7 DRM 3.49 5.14.21-150500.55.12-default) direct render: Yes Laicolasse:~ # -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1227316] New: gettext-runtime: msgcat fails on certain files
by bugzilla_noreply＠suse.com 01 Mar '25

01 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1227316 Bug ID: 1227316 Summary: gettext-runtime: msgcat fails on certain files Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Basesystem Assignee: sbrabec(a)suse.com Reporter: sbrabec(a)suse.com QA Contact: qa-bugs(a)suse.de CC: christian.voegl(a)suse.com, mmachova(a)suse.com Target Milestone: --- Found By: --- Blocker: --- While trying to concatenate two po files, I got: msgcat: memory exhausted Debugging in gdb, I realized that one of the failing po files has a non standard header that contains extra empty line: msgid "" msgstr "" "Project-Id-Version: @PACKAGE@\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2021-09-16 17:13+0200\n" "PO-Revision-Date: 2005-07-29 15:37+0530\n" "Last-Translator: Priyavert Sharma<priyavert.sharma(a)agreeya.com>\n" "Language-Team: AgreeYa Solutions <linux_team(a)agreeya.com>\n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n!=1);\n" "\n" The bug is triggered in msgl-header.c: message_list_header_list() while (*h != '\0') { char *enh = strchr (h, ':'); enh++; char * msgid = (char *)XNMALLOC (((enh - h) + 1), char); If the line does not contain ":", then enh is zero, and (enh - h) + 1 is evaluated to an absurd number. This is not an upstream bug. The smart header merge feature is introduced by: 0002-msgcat-Merge-headers-when-use-first.patch -- You are receiving this mail because: You are on the CC list for the bug.

1 10