November 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1217312] New: Google websites do not work in Firefox
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1217312 Bug ID: 1217312 Summary: Google websites do not work in Firefox 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: bart.vanassche+novell(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since more than a year, multiple Google websites, e.g. Google Search, Google Docs and Gmail, do not work well with the Firefox software included with openSUSE Tumbleweed. It often happens that loading one of these websites stalls. Logging in to a Google account doesn't work at all. I don't see this issue if I download Firefox binaries from the Mozilla website and load my existing profile (firefox/firefox -profileManager). Does this perhaps mean that there is a problem with changes made to the Firefox software that is available from openSUSE? Tumbleweed version: $ rpm -qf /etc/issue.net openSUSE-release-20231117-2596.1.x86_64 Firefox versions: $ rpm -q MozillaFirefox MozillaFirefox-119.0.1-1.1.x86_64 Binary downloaded from the Mozilla website: firefox-119.0.1.tar.bz2 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1216393] New: Electron/Chromium can't render h264 in webrtc
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1216393 Bug ID: 1216393 Summary: Electron/Chromium can't render h264 in webrtc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bjorn.bidar(a)thaodan.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- * Description: When trying to stream WebRTC with h264 in Electron/Chromium the screen stays black even thou OpenH264 is correctly installed. * How to reproduce: 1. Open Chromium 2. Open https://mozilla.github.io/webrtc-landing/pc_test_no_h264.html 3. Click test ** Another option is to use: https://mozilla.github.io/webrtc-landing/pc_test.html 1. Tick require h264 2. Start the video, wait 3. The message now should be "No H264 found in the offer!!!" * Background and reason for the bug: openSUSE builds both Chromium and Electron in a way that h264 isn't compiled into both packages but loaded using the Openh264 provided by openSUSE but blessed by Cisco. However Chromium has to use some of the openh264 to build even thou it's not used during runtime. The gyp option `rtc_use_h264` has be set to true and third_party/openh264 has to be included in the tarball (already the case in the upstream third_party/openh264 tarball). This is due webrtc using openh264 headers in third_party/webrtc/modules/video_coding/codecs/h264/h264_encoder_impl.cc -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216895] New: VUL-0: CVE-2023-47272: Roundcube 1.5.x before 1.5.6 and 1.6.x before 1.6.5 allows XSS via a Content-Type or Content-Disposition header (used for attachment preview or download).
by bugzilla_noreply＠suse.com 21 Aug '24

21 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1216895 Bug ID: 1216895 Summary: VUL-0: CVE-2023-47272: Roundcube 1.5.x before 1.5.6 and 1.6.x before 1.6.5 allows XSS via a Content-Type or Content-Disposition header (used for attachment preview or download). Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/384151/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: aj(a)ajaissle.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: stoyan.manolov(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Roundcube 1.5.x before 1.5.6 and 1.6.x before 1.6.5 allows XSS via a Content-Type or Content-Disposition header (used for attachment preview or download). References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-47272 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1217083] New: snapshot 20231107 --> 20231108 boot fails
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1217083 Bug ID: 1217083 Summary: snapshot 20231107 --> 20231108 boot fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: roeland.jansen(a)sue.nl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recently I updated 23031107 to 20231108 on two laptops running legacy boot. Both hang some time at console plymouth stuff. dracut then comes up with the inability to find /dev/system/root. It ends up in the dracut emergency shell. in the shell, lvm pvscan will report no physical volumes. It also happens on a virtual machine. (also not UEFI). If I try to recover with an usb stick, no partitions are shown. If I show "all", the installed system is being identified als unknown, architecture unknown. (and yes it's a 64 bit TW stick). I could not recover them anymore. Also, on one of the laptops, grub does not show windosws anmore, the other does. I luckily have a snapshot on my work vm so I can revert back. The following packages are updated when this happens. alsa alsa-devel code kernel-firmware-all kernel-firmware-amdgpu kernel-firmware-ath10k kernel-firmware-ath11k kernel-firmware-atheros kernel-firmware-bluetooth kernel-firmware-bnx2 kernel-firmware-brcm kernel-firmware-chelsio kernel-firmware-dpaa2 kernel-firmware-i915 kernel-firmware-intel kernel-firmware-iwlwifi kernel-firmware-liquidio kernel-firmware-marvell kernel-firmware-media kernel-firmware-mediatek kernel-firmware-mellanox kernel-firmware-mwifiex kernel-firmware-network kernel-firmware-nfp kernel-firmware-nvidia kernel-firmware-platform kernel-firmware-prestera kernel-firmware-qcom kernel-firmware-qlogic kernel-firmware-radeon kernel-firmware-realtek kernel-firmware-serial kernel-firmware-sound kernel-firmware-ti kernel-firmware-ueagle kernel-firmware-usb-network libasound2 libatopology2 libbrotli-devel libbrotlicommon1 libbrotlicommon1-x86-64-v3 libbrotlidec1 libbrotlidec1-x86-64-v3 libbrotlienc1 libbrotlienc1-x86-64-v3 libbytesize-lang libbytesize1 libgusb2 libnghttp2-14 libsqlite3-0 libsqlite3-0-x86-64-v3 libsvn_auth_kwallet-1-0 libxxhash0 openSUSE-release openSUSE-release-appliance-custom openSUSE-release-ftp sqlite3-devel sqlite3-tcl subversion subversion-bash-completion subversion-perl sysuser-shadow ucode-amd wmctrl I tried by mounting in rescue, created a new grub.cfg where osprober does not show windows anymore. The interesting part is that dracut -f will as last line shows "adding boot menu entry for UEFI firmware settings" Basically I will end up in reinstalling windows and linux on both laptops. (in legacy boot) If needed, I can install the non-kernel parts and see what package eventualy triggers this. -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1216717] New: suse-module-tools: 60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-0/queue/scheduler}, ignoring: No such file or directory
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1216717 Bug ID: 1216717 Summary: suse-module-tools: 60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-0/queue/scheduler}, ignoring: No such file or directory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: martin.wilck(a)suse.com Reporter: antonio.feijoo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Just in case this wasn't reported yet, this error is logged in the journal of a Tumbleweed system with crypto_LUKS devices: Oct 30 15:46:46 localhost (udev-worker)[724]: dm-0: /usr/lib/udev/rules.d/60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-0/queue/scheduler}, ignoring: No such file or directory Oct 30 15:46:48 localhost (udev-worker)[723]: dm-1: /usr/lib/udev/rules.d/60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-1/queue/scheduler}, ignoring: No such file or directory # uname -r 6.5.9-1-default # find /sys/devices -name "queue" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue /sys/devices/virtual/block/dm-1/queue /sys/devices/virtual/block/dm-0/queue # find /sys/devices -name "scheduler" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue/scheduler /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue/scheduler Not happening in systems with a similar setup using previous kernel versions: - ALP Dolomite Build6.8 localhost:~ # uname -r 6.4.11-1-default localhost:~ # find /sys/devices -name "queue" /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue /sys/devices/virtual/block/dm-0/queue localhost:~ # find /sys/devices -name "scheduler" /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue/scheduler /sys/devices/virtual/block/dm-0/queue/scheduler - Leap 15.5 # uname -r 5.14.21-150500.53-default # find /sys/devices -name "queue" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue /sys/devices/virtual/block/dm-0/queue # find /sys/devices -name "scheduler" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue/scheduler /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue/scheduler /sys/devices/virtual/block/dm-0/queue/scheduler I don't know if it's a kernel bug or if the udev rule needs to be adjusted. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1215586] New: guestfs regression: non functional network due to missing sysconfig-netconfig
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1215586 Bug ID: 1215586 Summary: guestfs regression: non functional network due to missing sysconfig-netconfig Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- At some point in the past, virt-builder and other tools had proper networking with-in the appliance. This still works by luck in SLE15, but it broke in Tumbleweed. The reason is the transformation of appliance/packagelist.in into /usr/lib64/guestfs/supermin.d/packages. During build the packagelist is passed to supermin, which writes the packages file. In case a package is unavailable during build, it will be missing from the packages file. Also 'systemd' is transformed into 'systemd-mini' (which is not really an issue because other packages require 'systemd'). In case of networking: if the host does not have 'dhcp-client' installed, the network will not start inside the appliance. Once dhcp-client gets installed, it will be put into the appliance. But the dhcp-client scripts expect a functional /sbin/netconfig, which is provided by sysconfig-netconfig. That package is listed in packagelist.in, but will not be written to packages because it is not in BuildRequires. I think most packages from packagelist.in are "lost" during build because they are not in BuildRequires, or because nothing requires them. It feels wrong to put each and every binary which is potentially called by guestfsd into BuildRequires. Instead the "packages" file should be overwritten manually with the list of packages which may be used, if it is installed on the host. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1216355] New: Packman Discord package upgrade lockout defeat inoperative.
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1216355 Bug ID: 1216355 Summary: Packman Discord package upgrade lockout defeat inoperative. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: rskunath(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There is a script in the Packman Discord srpm package (0.0.31-1699.98.pm.1) that is supposed to defeat the upgrade check that Discord does when they release a new version. This pops up a box to grab a deb or a tarball to update outside the Suse system. This script that is in the rpm spec file apparently has not worked for a while. I don't know if it can work, but it is in there and inoperative. The idea according to the script is to bypass the update check lockout and give the package maintainer time to update the Discord package without locking users out of Discord until that is done. This is a very good idea. In the last few Discord update cycles the box pops up and at that point you can't start Discord until the new package is released by the package maintainer. I did see a while ago a forum post about bumping the JSON file revision number by one version to get around this manually: (/usr/lib64/discord/resources and edit the build_info.json file) This appears to work but it's a kludge and the script is a better and a more appropriate way to do this if doing it is still possible. I'm just passing along the discovery and hoping defeating the lockout is still possible. I use Discord daily on the Suse Discord and users getting locked out is disconcerting. Thanks in advance. -- 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 16 Aug '24

16 Aug '24

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 2

[Bug 1217032] New: VUL-0: scamper: TCP packet parsing buffer overflow via large TCP fast open cookie
by bugzilla_noreply＠suse.com 13 Aug '24

13 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1217032 Bug ID: 1217032 Summary: VUL-0: scamper: TCP packet parsing buffer overflow via large TCP fast open cookie Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: sebix+novell.com(a)sebix.at Reporter: carlos.lopez(a)suse.com QA Contact: security-team(a)suse.de CC: dmueller(a)suse.com Target Milestone: --- Found By: --- Blocker: --- [scamper-announce] scamper-cvs-20230614d Matthew Luckie mjl at luckie.org.nz Mon Oct 9 10:37:01 PDT 2023 Previous message (by thread): [scamper-announce] scamper-cvs-20230614c Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] https://www.caida.org/catalog/software/scamper/code/scamper-cvs-20230614d.t… SHA256 (scamper-cvs-20230614d.tar.gz) = 54423b64a0b68aafa903d9260c2bff5c16f3cca44997e0e830d17296f6f03a59 SIZE (scamper-cvs-20230614d.tar.gz) = 2214467 scamper: * fix buffer overflow when parsing TCP packets where the sender includes a TCP fast open cookie larger than 16 bytes. References: https://mailman.caida.org/pipermail/scamper-announce/2023-October/000037.ht… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213154] New: openSUSE/mariadb container stops with non-zero exit code when calling podman stop
by bugzilla_noreply＠suse.com 12 Aug '24

12 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1213154 Bug ID: 1213154 Summary: openSUSE/mariadb container stops with non-zero exit code when calling podman stop Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: khanich.opensource(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Steps to reproduce: 1. Start a container, for testing: podman run --detach --env MYSQL_ROOT_PASSWORD=p --name mariadb registry.opensuse.org/opensuse/mariadb:latest 2. wait until initialized 3. Stop the container: podman stop mariadb 4. Check the exit code: podman ls -a; Exited (143) 5. Look at logs: podman logs mariadb example output: -------------------------------------------------------------------------------- Session terminated, killing shell...2023-07-08 22:55:08 0 [Note] mysqld (initiated by: unknown): Normal shutdown 2023-07-08 22:55:08 0 [Note] InnoDB: FTS optimize thread exiting. 2023-07-08 22:55:08 0 [Note] InnoDB: Starting shutdown... 2023-07-08 22:55:08 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool 2023-07-08 22:55:08 0 [Note] InnoDB: Buffer pool(s) dump completed at 230708 22:55:08 2023-07-08 22:55:08 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2023-07-08 22:55:08 0 [Note] InnoDB: Shutdown completed; log sequence number 46456; transaction id 15 2023-07-08 22:55:08 0 [Note] mysqld: Shutdown complete ...killed. -------------------------------------------------------------------------------- This causes trouble when using the image with a systemd service unit since systemd is going to interpret this as a failed unit. The official image from Docker Hub does not experience this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 4