April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[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 1221684] New: GCC 14: enchant-1 package fails
by bugzilla_noreply＠suse.com 13 Aug '24

13 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1221684 Bug ID: 1221684 Summary: GCC 14: enchant-1 package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building enchant-1 with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to (exhaustive list of errors): enchant.c: In function ‘enchant_dict_suggest’: enchant.c:991:87: error: passing argument 4 of ‘enchant_pwl_suggest’ from incompatible pointer type [-Wincompatible-pointer-types] 991 | pwl_suggs = enchant_pwl_suggest(session->personal, word, len, dict_suggs, &n_pwl_suggs); | ^~~~~~~~~~ | | | char ** pwl.c: In function ‘enchant_pwl_suggest’: pwl.c:739:41: error: passing argument 1 of ‘best_distance’ from incompatible pointer type [-Wincompatible-pointer-types] 739 | max_dist = suggs? best_distance(suggs, word, len) : ENCHANT_PWL_MAX_ERRORS; | ^~~~~ | | | const char * const* pwl.c:701:33: note: expected ‘char **’ but argument is of type ‘const char * const*’ 701 | static int best_distance(char** suggs, const char *const word, size_t len) | ~~~~~~~^~~~~ In file included from enchant.c:43: pwl.h:51:63: note: expected ‘const char * const* const’ but argument is of type ‘char **’ 51 | size_t len, const char*const*const suggs, size_t* out_n_suggs); | ~~~~~~~~~~~~~~~~~~~~~~~^~~~~ See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221685] New: GCC 14: gdl package fails
by bugzilla_noreply＠suse.com 13 Aug '24

13 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1221685 Bug ID: 1221685 Summary: GCC 14: gdl package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building gdl with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to (exhaustive list of errors): gdl-dock-item.c: In function ‘gdl_dock_item_class_init’: gdl-dock-item.c:358:44: error: passing argument 1 of ‘gdl_dock_object_class_set_is_compound’ from incompatible pointer type [-Wincompatible-pointer-types] 358 | gdl_dock_object_class_set_is_compound (object_class, FALSE); | ^~~~~~~~~~~~ | | | GObjectClass * {aka struct _GObjectClass *} In file included from gdl-dock.h:26, from gdl-dock-item.c:38: ../gdl/gdl-dock-object.h:354:74: note: expected ‘GdlDockObjectClass *’ {aka ‘struct _GdlDockObjectClass *’} but argument is of type ‘GObjectClass *’ {aka ‘struct _GObjectClass *’} 354 | void gdl_dock_object_class_set_is_compound (GdlDockObjectClass *object_class, | ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~ gdl-dock-item.c: In function ‘gdl_dock_item_set_property’: gdl-dock-item.c:747:36: error: initialization of ‘GObject *’ {aka ‘struct _GObject *’} from incompatible pointer type ‘GtkWidget *’ {aka ‘struct _GtkWidget *’} [-Wincompatible-pointer-types] 747 | GObject * parent = gtk_widget_get_parent (GTK_WIDGET (item)); | ^~~~~~~~~~~~~~~~~~~~~ gdl-dock-layout.c: In function ‘gdl_dock_layout_set_master’: gdl-dock-layout.c:623:30: error: assignment to ‘GdlDockMaster *’ {aka ‘struct _GdlDockMaster *’} from incompatible pointer type ‘GObject *’ {aka ‘struct _GObject *’} [-Wincompatible-pointer-types] 623 | layout->priv->master = g_object_ref (master); | ^ gdl-dock-bar.c: In function ‘gdl_dock_bar_set_master’: gdl-dock-bar.c:428:31: error: assignment to ‘GdlDockMaster *’ {aka ‘struct _GdlDockMaster *’} from incompatible pointer type ‘GObject *’ {aka ‘struct _GObject *’} [-Wincompatible-pointer-types] 428 | dockbar->priv->master = g_object_ref (master); | ^ See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[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

[Bug 1218579] New: cargo_vendor serice fail
by bugzilla_noreply＠suse.com 11 Aug '24

11 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1218579 Bug ID: 1218579 Summary: cargo_vendor serice fail Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: All Status: NEW Severity: Major Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: werwolf131313(a)gmail.com QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 871679 --> https://bugzilla.suse.com/attachment.cgi?id=871679&action=edit local cargo_vendor cargo_vendor work in local `osc service ra`, but failed in OBS. error: > Files could not be expanded: service error: 400 remote error: cargo_vendor service parameter "srctar" is not defined (http://obs-gateway:5153/sourceupdate/home:Werwolf2517/Alfis?timeout=7200) less info > service daemon error: > 400 remote error: cargo_vendor service parameter "srctar" is not defined (http://obs-gateway:5153/sourceupdate/home:Werwolf2517/Alfis?timeout=7200) i try src, srctar, srcdir. in my local machine all works, but in OBS always i get this error For a long time I thought I was doing something wrong, but now I'm sure it's not me. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1222505] New: ckermit: cannot create lock file in /var/lock
by bugzilla_noreply＠suse.com 09 Aug '24

09 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1222505 Bug ID: 1222505 Summary: ckermit: cannot create lock file in /var/lock Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ceggers(a)arri.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Kermit needs to create a lock file for the used serial port (e.g. /dev/ttyUSB0) under /var/lock (symlink to /run/lock). Until Leap 15.5, that directory was owned by group "lock", so it was sufficient to add the current user to the "lock" group. But now the directory is owned by group "root", so using the "lock" group is not sufficient anymore. Reproducible: Always Steps to Reproduce: 1. Add current user to "dialout" group (and create re-login after that). 2. Ensure that step 1. was successful (e.g. by using the "id" command). 3. kermit -l /dev/ttyUSB0 Actual Results: Kermit gives an error "can't open device". Using "set line /dev/ttyUSB0" in kermit's interactive mode gives a more precise error message: "Sorry, write access to UUCP lockfile directory denied." Expected Results: kermit should have created the lock file and open /dev/ttyUSB0 A workaround is to change the group of /run/lock to "dialout" (and to add the current user to this group). But this change is lost after every reboot. Possibly related to https://bugzilla.opensuse.org/show_bug.cgi?id=624290 ("ckermit from contrib repository does not use lockdev, so cannot write to /var/lock"). The packet installed is: $ rpm -q ckermit --info Name : ckermit Version : 9.0.302 Release : 150000.3.3.1 Architecture: x86_64 Install Date: Mo 08 Apr 2024 09:44:42 CEST Group : Hardware/Modem Size : 2621762 License : BSD-3-Clause Signature : RSA/SHA256, Fr 01 Apr 2022 13:39:36 CEST, Key ID 70af9e8139db7c82 Source RPM : ckermit-9.0.302-150000.3.3.1.src.rpm Build Date : Fr 01 Apr 2022 13:39:14 CEST Build Host : goat10 Relocations : (not relocatable) Packager : https://www.suse.com/ Vendor : SUSE LLC <https://www.suse.com/> URL : http://www.kermitproject.org/ Summary : A Combined Serial and Network Communication Software Package Description : C-Kermit is a combined serial and network communication software package offering a consistent, medium-independent, and cross-platform approach to connection establishment, terminal sessions, file transfer, character-set translation, and automation of communication tasks. Distribution: SUSE Linux Enterprise 15 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213495] New: Mariadb: InnoDB: Unable to find charset-collation for X
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1213495 Bug ID: 1213495 Summary: Mariadb: InnoDB: Unable to find charset-collation for X Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: suse(a)rettich.bayern QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There is an upstream bug in Mariadb 11.0.2 (currently distributed in Tumbleweed): https://jira.mariadb.org/browse/MDEV-31443 The bug prevents Mariadb to successfully upgrade from 10 to 11 on database that contains older tables. Can you upgrade the package in the Tumbleweed repository to 11.0.3? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1214053] New: Wrong Permissions for Package xmrig-6.18.1-bp155.1.8.x86_64.rpm (Download Error)
by bugzilla_noreply＠suse.com 07 Aug '24

07 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1214053 Bug ID: 1214053 Summary: Wrong Permissions for Package xmrig-6.18.1-bp155.1.8.x86_64.rpm (Download Error) Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: stephan.kreuz(a)bwi.de QA Contact: packagehub-bugs(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Sine 07/01/23 (not sure when problem occure first Time) I get Permission denied for Package xmrig-6.18.1-bp155.1.8.x86_64.rpm from suse-packagehub-15-sp5-backports-pool-x86_64(-sap). Please verify that the correct Permisions set for that Package. kind regards Stephan -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1217488] New: pynfs CID* tests fails: OP_SETCLIENTID should return NFS4_OK, instead got NFS4ERR_DELAY
by bugzilla_noreply＠suse.com 06 Aug '24

06 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1217488 Bug ID: 1217488 Summary: pynfs CID* tests fails: OP_SETCLIENTID should return NFS4_OK, instead got NFS4ERR_DELAY Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Filesystems Assignee: nfbrown(a)suse.com Reporter: petr.vorel(a)suse.com QA Contact: petr.vorel(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Although we start due #1217128 testing via cdmackay/pynfs.git, which has fix for "nfs4lib.BadCompoundRes: operation OP_SETCLIENTID should return NFS4_OK [1], instead got NFS4ERR_DELAY", we still get 9 tests failing with this error on Tumbleweed. Any idea what could be wrong now? O I can ask Calum Mackay on linux-nfs if you're busy with more important stuff. [1] https://git.linux-nfs.org/?p=cdmackay/pynfs.git;a=commit;h=0d4d3fd0bb7a6386… -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1223435] New: Get "nothing provides 'python3-packaging >= 20.9' needed by the to be installed azure-cli-core-2.36.0-150200.9.3.2.noarch" error messsage during updates
by bugzilla_noreply＠suse.com 05 Aug '24

05 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1223435 Bug ID: 1223435 Summary: Get "nothing provides 'python3-packaging >= 20.9' needed by the to be installed azure-cli-core-2.36.0-150200.9.3.2.noarch" error messsage during updates Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cloud:Tools Assignee: public-cloud-maintainers(a)suse.de Reporter: kvanderveer(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874524 --> https://bugzilla.suse.com/attachment.cgi?id=874524&action=edit Error from the UI When I run the update from KDE UI in the system tray, I get the following error: nothing provides 'python3-packaging >= 20.9' needed by the to be installed azure-cli-core-2.36.0-150200.9.3.2.noarch I've poked around, and tried a recommendation to install the azure-cli from CloudTools. I've got the 2.17.1 version of the azure-cli. When I ran the install, I got: Reading installed packages... There is an update candidate for 'azure-cli' from vendor 'obs://build.opensuse.org/Cloud', while the current vendor is 'SUSE LLC <https://www.suse.com/>'. Use 'zypper install azure-cli-2.59.0-144.4.noarch' to install this candidate. Resolving package dependencies... Problem: 1: nothing provides 'python3-packaging >= 20.9' needed by the to be installed azure-cli-2.36.0-150200.9.3.2.noarch Solution 1: do not install azure-cli-2.36.0-150200.9.3.2.noarch Solution 2: break azure-cli-2.36.0-150200.9.3.2.noarch by ignoring some of its dependencies I just canceled out. But I did try to install the 2.59.0 version, and essentially got the same thing. -- You are receiving this mail because: You are on the CC list for the bug.

1 11