March 2024 - openSUSE Bugs - openSUSE Mailing Lists

[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 31 May '24

31 May '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 5

[Bug 1220571] New: [META] Packages failing because GCC 14+ treats some warnings as errors
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1220571 Bug ID: 1220571 Summary: [META] Packages failing because GCC 14+ treats some warnings as errors Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: mjambor(a)suse.com Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- GCC 14 treats the following situations, which were only warnings before, as errors: -Werror=implicit-int -Werror=implicit-function-declaration -Werror=declaration-missing-parameter-type -Werror=return-mismatch -Werror=int-conversion -Werror=incompatible-pointer-types More details about all of these cases together with the most common ways of addressing them and some associated pitfalls is available at https://gcc.gnu.org/gcc-14/porting_to.html For the record, clang has taken a similar step since clang 16, see for example https://www.redhat.com/en/blog/new-warnings-and-errors-clang-16 The preferred method of dealing with these issues is of course fixing the code. Other distributions have shared patches from their porting efforts on relevant upstream mailing lists and bug trackers, Gentoo and RedHat are perhaps most active in this regard, so you can have a look at what they did for their packages at: - https://bugs.gentoo.org/showdependencytree.cgi?id=870412&hide_resolved=0 - https://gitlab.com/fweimer-rh/fedora-modernc/ In case there is for some reason not possible to fix the code, or at least to fix it in time for adoption of GCC 14, it is possible to turn these back to warnings by adding to the compiler options one of the following: -std=gnu89, -std=c89, or -fpermissive. (Especially if you use -fpermissive as a temporary workaround with intention to fix the underlying issues later, I'd suggest leaving the particular bug opened until it is done so.) -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1221683] New: GCC 14: certmonger package fails
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221683 Bug ID: 1221683 Summary: GCC 14: certmonger package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ngompa13(a)gmail.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building certmonger with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to (exhaustive list of errors): tdbusm.c: In function ‘cm_tdbusm_get_vn’: tdbusm.c:244:28: error: assignment to ‘long int’ from ‘int64_t *’ {aka ‘long int *’} makes integer from pointer without a cast [-Wint-conversion] 244 | *n = i64; | ^ util-o.c: In function ‘util_public_EVP_PKEY_dup’: util-o.c:593:40: error: passing argument 2 of ‘util_EVP_PKEY_dup’ from incompatible pointer type [-Wincompatible-pointer-types] 593 | return util_EVP_PKEY_dup(pkey, i2d_PublicKey, d2i_PublicKey); | ^~~~~~~~~~~~~ | | | int (*)(const EVP_PKEY *, unsigned char **) {aka int (*)(const struct evp_pkey_st *, unsigned char **)} util-o.c:554:25: note: expected ‘int (*)(EVP_PKEY *, unsigned char **)’ {aka ‘int (*)(struct evp_pkey_st *, unsigned char **)’} but argument is of type ‘int (*)(const EVP_PKEY *, unsigned char **)’ {aka ‘int (*)(const struct evp_pkey_st *, unsigned char **)’} 554 | int (*i2d)(EVP_PKEY *, unsigned char **), | ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ util-o.c: In function ‘util_private_EVP_PKEY_dup’: util-o.c:599:40: error: passing argument 2 of ‘util_EVP_PKEY_dup’ from incompatible pointer type [-Wincompatible-pointer-types] 599 | return util_EVP_PKEY_dup(pkey, i2d_PrivateKey, d2i_PrivateKey); | ^~~~~~~~~~~~~~ | | | int (*)(const EVP_PKEY *, unsigned char **) {aka int (*)(const struct evp_pkey_st *, unsigned char **)} 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 1221685] New: GCC 14: gdl package fails
by bugzilla_noreply＠suse.com 31 May '24

31 May '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 1

[Bug 1220481] New: GCC 14: gamin package fails
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1220481 Bug ID: 1220481 Summary: GCC 14: gamin package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jengelh(a)inai.de, mjambor(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Building gamin with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: gam_listener.c: In function ‘gam_listener_free_subscription’: gam_listener.c:101:39: error: implicit declaration of function ‘gam_exclude_check’; did you mean ‘gam_error_check’? [-Wimplicit-function-declaration] 101 | if (gam_inotify_is_running() && (!gam_exclude_check(path))) { | ^~~~~~~~~~~~~~~~~ | gam_error_check gam_node.c: In function ‘gam_node_emit_event’: gam_node.c:375:9: error: implicit declaration of function ‘gam_server_emit_event’; did you mean ‘gam_node_emit_event’? [-Wimplicit-function-declaration] 375 | gam_server_emit_event(gam_node_get_path(node), is_dir_node, event, subs, 0); | ^~~~~~~~~~~~~~~~~~~~~ | gam_node_emit_event gam_server.c: In function ‘gam_init_subscriptions’: gam_server.c:167:13: error: implicit declaration of function ‘gam_poll_basic_init’; did you mean ‘gam_poll_generic_init’? [-Wimplicit-function-declaration] 167 | if (gam_poll_basic_init()) { | ^~~~~~~~~~~~~~~~~~~ | gam_poll_generic_init gam_inotify.c: In function ‘gam_inotify_init’: gam_inotify.c:145:9: error: implicit declaration of function ‘gam_poll_basic_init’ [-Wimplicit-function-declaration] 145 | gam_poll_basic_init (); | ^~~~~~~~~~~~~~~~~~~ gam_connection.c: In function ‘gam_connection_request’: gam_connection.c:402:49: error: implicit declaration of function ‘gam_exclude_check’; did you mean ‘gam_error_check’? [-Wimplicit-function-declaration] 402 | if ((gam_inotify_is_running()) && (!gam_exclude_check(path))) { | ^~~~~~~~~~~~~~~~~ | gam_error_check Builds with: Index: gamin.spec_dir/gamin-0.1.10/server/gam_listener.c =================================================================== --- gamin.spec_dir.orig/gamin-0.1.10/server/gam_listener.c +++ gamin.spec_dir/gamin-0.1.10/server/gam_listener.c @@ -27,6 +27,7 @@ #include "gam_pidname.h" #ifdef ENABLE_INOTIFY #include "gam_inotify.h" +#include "gam_excludes.h" #endif //#define GAM_LISTENER_VERBOSE Index: gamin.spec_dir/gamin-0.1.10/server/gam_node.c =================================================================== --- gamin.spec_dir.orig/gamin-0.1.10/server/gam_node.c +++ gamin.spec_dir/gamin-0.1.10/server/gam_node.c @@ -23,6 +23,7 @@ #include "gam_event.h" #include "gam_node.h" #include "gam_error.h" +#include "gam_server.h" /** * Create a new node Index: gamin.spec_dir/gamin-0.1.10/server/gam_server.c =================================================================== --- gamin.spec_dir.orig/gamin-0.1.10/server/gam_server.c +++ gamin.spec_dir/gamin-0.1.10/server/gam_server.c @@ -33,6 +33,7 @@ #include "gam_channel.h" #include "gam_subscription.h" #include "gam_poll_generic.h" +#include "gam_poll_basic.h" #ifdef ENABLE_INOTIFY #include "gam_inotify.h" #endif Index: gamin.spec_dir/gamin-0.1.10/server/gam_connection.c =================================================================== --- gamin.spec_dir.orig/gamin-0.1.10/server/gam_connection.c +++ gamin.spec_dir/gamin-0.1.10/server/gam_connection.c @@ -17,6 +17,7 @@ #endif #ifdef ENABLE_INOTIFY #include "gam_inotify.h" +#include "gam_excludes.h" #endif #include "fam.h" Index: gamin.spec_dir/gamin-0.1.10/server/gam_inotify.c =================================================================== --- gamin.spec_dir.orig/gamin-0.1.10/server/gam_inotify.c +++ gamin.spec_dir/gamin-0.1.10/server/gam_inotify.c @@ -30,6 +30,7 @@ #include "gam_server.h" #include "gam_subscription.h" #include "gam_inotify.h" +#include "gam_poll_basic.h" /* Transforms a inotify event to a gamin event. */ static GaminEventType -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1220476] New: GCC 14: freeipmi package fails
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1220476 Bug ID: 1220476 Summary: GCC 14: freeipmi package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kkaempf(a)suse.com, mjambor(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Building freeipmi with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: sel/ipmi-sel-string-supermicro-x10dimm-common.c: In function ‘sel_string_output_supermicro_x10dimm_event_data2_event_data3’: sel/ipmi-sel-string-supermicro-x10dimm-common.c:87:14: error: implicit declaration of function ‘sel_string_output_supermicro_dimm_event_data2_event_data3’; did you mean ‘sel_string_output_supermicro_x10dimm_event_data2_event_data3’? [-Wimplicit-function-declaration] 87 | if ((ret = sel_string_output_supermicro_dimm_event_data2_event_data3 (ctx, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | sel_string_output_supermicro_x10dimm_event_data2_event_data3 ipmi-sensors-oem-intel.c: In function ‘ipmi_sensors_oem_intel_output_oem_record’: ipmi-sensors-oem-intel.c:98:18: error: implicit declaration of function ‘ipmi_sensors_oem_intel_s2600wp_output_oem_record’; did you mean ‘ipmi_sensors_oem_intel_s2600jf_output_oem_record’? [-Wimplicit-function-declaration] 98 | if ((ret = ipmi_sensors_oem_intel_s2600wp_output_oem_record (state_data, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ipmi_sensors_oem_intel_s2600jf_output_oem_record Builds with: Index: freeipmi.spec_dir/freeipmi-1.6.14/libfreeipmi/sel/ipmi-sel-string-supermicro-common.h =================================================================== --- freeipmi.spec_dir.orig/freeipmi-1.6.14/libfreeipmi/sel/ipmi-sel-string-supermicro-common.h +++ freeipmi.spec_dir/freeipmi-1.6.14/libfreeipmi/sel/ipmi-sel-string-supermicro-common.h @@ -38,5 +38,14 @@ int sel_string_output_supermicro_overhea unsigned int flags, unsigned int *wlen, struct ipmi_sel_system_event_record_data *system_event_record_data); +int sel_string_output_supermicro_dimm_event_data2_event_data3 (ipmi_sel_ctx_t ctx, + struct ipmi_sel_entry *sel_entry, + uint8_t sel_record_type, + char *buf, + unsigned int buflen, + unsigned int flags, + unsigned int *wlen, + struct ipmi_sel_system_event_record_data *system_event_record_data, + int *oem_rv); #endif /* IPMI_SEL_STRING_SUPERMICRO_COMMON_H */ Index: freeipmi.spec_dir/freeipmi-1.6.14/ipmi-sensors/ipmi-sensors-oem-intel.c =================================================================== --- freeipmi.spec_dir.orig/freeipmi-1.6.14/ipmi-sensors/ipmi-sensors-oem-intel.c +++ freeipmi.spec_dir/freeipmi-1.6.14/ipmi-sensors/ipmi-sensors-oem-intel.c @@ -34,6 +34,7 @@ #include "ipmi-sensors-oem-intel.h" #include "ipmi-sensors-oem-intel-s5500wb.h" #include "ipmi-sensors-oem-intel-s2600jf.h" +#include "ipmi-sensors-oem-intel-s2600wp.h" #include "ipmi-sensors-oem-intel-quanta-qssc-s4r.h" #include "ipmi-sensors-oem-intel-node-manager.h" -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1221682] New: GCC 14: autofs package fails
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221682 Bug ID: 1221682 Summary: GCC 14: autofs package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Filesystems Assignee: kernel-fs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ddiss(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building autofs with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to (exhaustive list of errors): cyrus-sasl.c:112:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincompatible-pointer-types] 112 | { SASL_CB_USER, &getuser_func, NULL }, | ^ cyrus-sasl.c:112:25: note: (near initialization for ‘callbacks[0].proc’) cyrus-sasl.c:113:29: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincompatible-pointer-types] 113 | { SASL_CB_AUTHNAME, &getuser_func, NULL }, | ^ cyrus-sasl.c:113:29: note: (near initialization for ‘callbacks[1].proc’) cyrus-sasl.c:114:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(sasl_conn_t *, void *, int, sasl_secret_t **)’ {aka ‘int (*)(struct sasl_conn *, void *, int, struct sasl_secret **)’} [-Wincompatible-pointer-types] 114 | { SASL_CB_PASS, &getpass_func, NULL }, | ^ cyrus-sasl.c:114:25: note: (near initialization for ‘callbacks[2].proc’) cyrus-sasl.c:119:24: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char *)’ [-Wincompatible-pointer-types] 119 | { SASL_CB_LOG, &sasl_log_func, NULL }, | ^ cyrus-sasl.c:119:24: note: (near initialization for ‘debug_callbacks[0].proc’) cyrus-sasl.c:120:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincompatible-pointer-types] 120 | { SASL_CB_USER, &getuser_func, NULL }, | ^ cyrus-sasl.c:120:25: note: (near initialization for ‘debug_callbacks[1].proc’) cyrus-sasl.c:121:29: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincompatible-pointer-types] 121 | { SASL_CB_AUTHNAME, &getuser_func, NULL }, | ^ cyrus-sasl.c:121:29: note: (near initialization for ‘debug_callbacks[2].proc’) cyrus-sasl.c:122:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(sasl_conn_t *, void *, int, sasl_secret_t **)’ {aka ‘int (*)(struct sasl_conn *, void *, int, struct sasl_secret **)’} [-Wincompatible-pointer-types] 122 | { SASL_CB_PASS, &getpass_func, NULL }, | ^ cyrus-sasl.c:122:25: note: (near initialization for ‘debug_callbacks[3].proc’) ./autofs-5.1.9/config.log: conftest.c: In function 'main': ./autofs-5.1.9/config.log: conftest.c:58:47: error: passing argument 4 of 'ldap_parse_page_control' from incompatible pointer type [-Wincompatible-pointer-types] ./autofs-5.1.9/config.log: 58 | ret = ldap_parse_page_control(ld,clp,ct,c); ./autofs-5.1.9/config.log: | ^ ./autofs-5.1.9/config.log: | | ./autofs-5.1.9/config.log: | struct berval * ./autofs-5.1.9/config.log: In file included from /usr/include/lber_types.h:24, ./autofs-5.1.9/config.log: from /usr/include/lber.h:29, ./autofs-5.1.9/config.log: from /usr/include/ldap.h:30, ./autofs-5.1.9/config.log: from conftest.c:49: ./autofs-5.1.9/config.log: /usr/include/ldap.h:2155:25: note: expected 'struct berval **' but argument is of type 'struct berval *' ./autofs-5.1.9/config.log: 2155 | ldap_parse_page_control LDAP_P(( ./autofs-5.1.9/config.log: | ^~~~~~ Fixing configure may not be necessary to build the package, but it might be an indication that the package will be misconfigured. See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1213915] New: Kernel panic - illegal instruction (4) at 7fffb6a4f874 nip 7fffb6a4f874 lr 7fffb6a4380c code 1 in ld64.so.2
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213915 Bug ID: 1213915 Summary: Kernel panic - illegal instruction (4) at 7fffb6a4f874 nip 7fffb6a4f874 lr 7fffb6a4380c code 1 in ld64.so.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jrivrain(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868604 --> https://bugzilla.suse.com/attachment.cgi?id=868604&action=edit serial output All ppc64 Tumbleweed tests in Openqa are failing right now with a kernel panic. All the workers are on power8 cpus, this does not happen on a qemu emulated power9 cpu. Example of failing test: https://openqa.opensuse.org/tests/3476697 See attached serial output. -- You are receiving this mail because: You are on the CC list for the bug.

1 30

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

31 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 5

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

30 May '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 7