July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1227479] New: gnome-clocks timers crashes if GTK_THEME variable is not empty
by bugzilla_noreply＠suse.com 14 Aug '24

14 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1227479 Bug ID: 1227479 Summary: gnome-clocks timers crashes if GTK_THEME variable is not empty Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: hol.jimis(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On opensuse tubleweed I use Xorg and Awesome WM. Gnome is installed but I rarely use its session. On https://bugzilla.suse.com/show_bug.cgi?id=1210065 is reported why I removed xdg-desktop-portal-gnome from my system. I like dark theme but the three, most used by me, gnome packages as nautilus, gnome-calculator and gnome-clocks, perhaps evolution mail too, refused to apply dark mode even if it was set by tweaks, gconf or other means. The only way, to have dark mode in these, was to first log in gnome session, log out and finally log in awesome wm. Some unknown variable, set in gnome session, manage to pass in awesome wm session and the above three packages run in dark mode. On logging directly in Awesome wm, dark mode was impossible for these three apps. Either log in directly on awesomeWM, where dark mode does not apply, or log in AwesomeWM after log in and out of gnome-session, where dark mode applies, the variable GTK_THEME is empty. BUT upon entering a line of export GTK_THEME="Adwaita:dark"; in ~/.profile or ~/.zprofile for zsh, dark mode is applied always in these three apps. However, the setting of GTK_THEME variable cause the crash of the two timers, that gnome-clocks include, upon clicking on start timer icon. I removed the above offensive line from .profile file to have working timers in light mode and I hope that this bug? could be fixed and gnome-clocks will work in dark mode as gnome-calculator does. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1226825] New: podman erros with "configure storage: unknown option overlay.mountopt"
by bugzilla_noreply＠suse.com 14 Aug '24

14 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1226825 Bug ID: 1226825 Summary: podman erros with "configure storage: unknown option overlay.mountopt" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Using distrobox/podman containers on MicroOS and with the last snapshot of Tumbleweed I get this on any podman command I run: ERRO[0000] User-selected graph driver "overlay" overwritten by graph driver "btrfs" from database - delete libpod local files ("/var/lib/containers/storage") to resolve. May prevent use of images created by other tools Error: configure storage: unknown option overlay.mountopt ("overlay.mountopt=nodev,metacopy=on") Unfortunately, it also breaks my main working container (`distrobox --root`). mitmanek:~ $ cat /etc/os-release NAME="openSUSE MicroOS" # VERSION="20240621" ID="opensuse-microos" ID_LIKE="suse opensuse opensuse-tumbleweed microos sl-micro" VERSION_ID="20240621" PRETTY_NAME="openSUSE MicroOS" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:microos:20240621" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:MicroOS" LOGO="distributor-logo-MicroOS" mitmanek:~ $ -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1226122] New: TW installation leaves /boot empty
by bugzilla_noreply＠suse.com 13 Aug '24

13 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1226122 Bug ID: 1226122 Summary: TW installation leaves /boot empty Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: mario_bz(a)mgtech.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 875388 --> https://bugzilla.suse.com/attachment.cgi?id=875388&action=edit zypp log from installation Installing TW from June 7 image. I select not to install any boot manager because I use Refind on Mac. Note I have installed Opensuse and TW this way for 15 years on multiple macs, leaving Grub out. In all cases installation always worked fine and booted, the last fresh TW install 2 years ago is still good. I decided to do a clean install of TW to check on other problems I am having. However, although the kernel is placed in /usr/lib/modules, the/boot directory is left empty except for the kernel cleanup script. I tried: 1. Copying my working kernel from a TW to /boot and /usr/lib/modules. I was able to boot that kernel. While booted I did a force installation of the kernel in YAST, but again, nothing was put into /boot. 2. I reinstalled using both btrf which I normally use, and xfs to see if btrfs was the issue. No change. I searched for hours trying to find this issue and found someone had the same thing after updating, that was a couple of years ago and they just added symlinks. I my case, I could not do that because initrd modules were missing which are not symlinks. Since I cant find anyone having this issue recently, I am assuming it's related to the fact I selected not to install boot manager. At this point I can't get a new install working. Some people really need to install without a boot manager, Opensuse and TW made it easy. I assume it's not a design change since it would make no sense to leave /boot empty. If you want any logs, please let me know where they are, I could not find an installation log. I attached the zypp log I found. It does not have a reference to /boot anywhere. -- You are receiving this mail because: You are on the CC list for the bug.

1 48

[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 1228605] New: Freezed screen
by bugzilla_noreply＠suse.com 12 Aug '24

12 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228605 Bug ID: 1228605 Summary: Freezed screen Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: OES - Linux Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: monesi.manuel06(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The system with KDE freezes casually, it needs a reboot to work againg. It happens with a Dell Vostro 3520 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1225921] New: Package rubygem-hpricot does not build with gcc14 because of new errors
by bugzilla_noreply＠suse.com 12 Aug '24

12 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1225921 Bug ID: 1225921 Summary: Package rubygem-hpricot does not build with gcc14 because of new errors 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: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- GCC 14 newly by default treats as errors a number of situations which before were only warnings. For more information see https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571. Because of this, package rubygem-hpricot fails to compile. This can be seen online at: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… It can be reproduced locally with command: osc build --clean --alternative-project home:rguenther:nextgcc The corresponding Gentoo bug might be https://bugs.gentoo.org/884257 The (first) error (that halts the build) is: [ 7s] fast_xs.c: In function ‘fast_xs’: [ 7s] fast_xs.c:165:46: error: passing argument 3 of ‘rb_rescue’ from incompatible pointer type [-Wincompatible-pointer-types] [ 7s] 165 | array = rb_rescue(unpack_utf8, self, unpack_uchar, self); [ 7s] | ^~~~~~~~~~~~ [ 7s] | | [ 7s] | VALUE (*)(VALUE) {aka long unsigned int (*)(long unsigned int)} [ 7s] In file included from /usr/include/ruby-3.3.0/ruby/ruby.h:41, [ 7s] from /usr/include/ruby-3.3.0/ruby.h:38, [ 7s] from fast_xs.c:1: [ 7s] /usr/include/ruby-3.3.0/ruby/internal/iterator.h:364:62: note: expected ‘VALUE (*)(VALUE, VALUE)’ {aka ‘long unsigned int (*)(long unsigned int, long unsigned int)’} but argument is of type ‘VALUE (*)(VALUE)’ {aka ‘long unsigned int (*)(long unsigned int)’} [ 7s] 364 | VALUE rb_rescue(VALUE (*b_proc)(VALUE), VALUE data1, VALUE (*r_proc)(VALUE, VALUE), VALUE data2); [ 7s] | ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~ -- 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

[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