May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225689] New: Error message received from tik with mount system call failed.
by bugzilla_noreply＠suse.com 01 Jun '24

01 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225689 Bug ID: 1225689 Summary: Error message received from tik with mount system call failed. Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: tony.neely(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0 Build Identifier: [tik][20240531-02:01:04][LOG] [START] /usr/bin/tik [/usr/lib/tik/modules/pre/10-welcome][20240531-02:01:04][LOG] [START] /usr/lib/tik/modules/pre//usr/lib/tik/modules/pre/10-welcome [/usr/lib/tik/modules/pre/10-welcome][20240531-02:01:24][LOG] [zenity][0][] --info --ok-label=Install Now --no-wrap --width=300 --height=300 --icon=distributor-logo-Aeon-symbolic --title= --text=<big>Welcome to openSUSE Aeon</big>\n\nPlease press <b>Install Now</b> to continue [/usr/lib/tik/modules/pre/10-welcome][20240531-02:01:24][LOG] [STOP] /usr/lib/tik/modules/pre//usr/lib/tik/modules/pre/10-welcome [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:24][LOG] [START] /usr/lib/tik/modules/pre//usr/lib/tik/modules/pre/20-mig [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:32][LOG] [pkexec][0] /usr/bin/mkdir -p /var/lib/tik/mig [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] [zenity][0][nvme-Samsung_SSD_970_EVO_Plus_250GB_S4P3NF0M605653V] --list --column=Disk --column=Size --width=1000 --height=340 --title=Select A Disk --text=Select the disk to install the operating system to. <b>Make sure any important documents and files have been backed up.</b>\n ata-Samsung_SSD_860_EVO_1TB_S3Z8NY0M767057P 931.5G nvme-Samsung_SSD_970_EVO_Plus_250GB_S4P3NF0M605653V 232.9G [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] [pkexec][0] /usr/bin/mkdir -p /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] [pkexec][0] /usr/bin/mount -o compress=zstd:1 /dev/disk/by-id/nvme-eui.0025385691b29275-part2 /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] [probe_partitions] /dev/disk/by-id/nvme-eui.0025385691b29275-part2 found [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] Legacy Aeon Install FOUND [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][LOG] [pkexec][0] /usr/bin/umount /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][LOG] [pkexec][0] /usr/bin/rmdir /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][LOG] [pkexec][0] /usr/bin/mkdir /var/lib/tik/mig/mnt mount: /var/lib/tik/mig/mnt: mount system call failed: No such file or directory. dmesg(1) may have more information after failed mount system call. [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][LOG] [pkexec][32] /usr/bin/mount -o compress=zstd:1,subvol=/@/home /dev/disk/by-id/nvme-eui.0025385691b29275-part2 /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][ERROR] Command <tt>/usr/bin/mount -o compress=zstd:1,subvol=/@/home /dev/disk/by-id/nvme-eui.0025385691b29275-part2 /var/lib/tik/mig/mnt</tt> FAILED [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:54][LOG] [zenity][0][] --error --text Command <tt>/usr/bin/mount -o compress=zstd:1,subvol=/@/home /dev/disk/by-id/nvme-eui.0025385691b29275-part2 /var/lib/tik/mig/mnt</tt> FAILED [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:54][LOG] [STOP][1] /usr/bin/tik Reproducible: Always Actual Results: System notified me of error and shut down. I have an existing Aeon install, with a separate drive (BTRFS formatted) for my /home. Easy enough to setup with old installer. Chose system drive (not /home drive) for the install. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1225779] New: gtest.pc injects a bogus include directory which breaks libstdc++ headers
by bugzilla_noreply＠suse.com 01 Jun '24

01 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225779 Bug ID: 1225779 Summary: gtest.pc injects a bogus include directory which breaks libstdc++ headers Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- > pkg-config --cflags gtest -DGTEST_HAS_PTHREAD=1 -lpthread -I/usr/lib64/pkgconfig/../../include The `-I` is changed to `-isystem` by a downstream build system (Google Ninja) When calling g++-13 with this flag on a file which includes `<cstdlib>`, i'm getting a confusing build error: In file included from ../../v8/include/v8.h:21, from ../../third_party/electron_node/src/node.h:79, from ../../third_party/electron_node/src/api/async_resource.cc:1: /usr/include/c++/13/cstdlib:79:15: fatal error: stdlib.h: No such file or directory 79 | #include_next <stdlib.h> | ^~~~~~~~~~ This is gtest-1.10.0-1.10.x86_64 The problem happens on both 15.5 and 15.6, does not happen on Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[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 1217979] package xfsprogs: error while installing libhandle1
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217979 https://bugzilla.suse.com/show_bug.cgi?id=1217979#c25 --- Comment #25 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2024:1887-1: An update that has five fixes can now be installed. Category: recommended (moderate) Bug References: 1192014, 1216717, 1217979, 1223278, 1224320 Maintenance Incident: [SUSE:Maintenance:34011](https://smelt.suse.de/incident/34011/) Sources used: openSUSE Leap 15.6 (src): suse-module-tools-15.6.9-150600.3.3.3 Basesystem Module 15-SP6 (src): suse-module-tools-15.6.9-150600.3.3.3 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192014] provide admin option to NOT automatically REbuild initrds for previously installed kernels
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1192014 https://bugzilla.suse.com/show_bug.cgi?id=1192014#c25 --- Comment #25 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2024:1887-1: An update that has five fixes can now be installed. Category: recommended (moderate) Bug References: 1192014, 1216717, 1217979, 1223278, 1224320 Maintenance Incident: [SUSE:Maintenance:34011](https://smelt.suse.de/incident/34011/) Sources used: openSUSE Leap 15.6 (src): suse-module-tools-15.6.9-150600.3.3.3 Basesystem Module 15-SP6 (src): suse-module-tools-15.6.9-150600.3.3.3 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225778] New: Package ibus does not build with gcc14 because of uses of incompatible pointer types
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225778 Bug ID: 1225778 Summary: Package ibus does not build with gcc14 because of uses of incompatible pointer types 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: 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 ibus 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 Fedora seems to have decided to avoid the new errors, see https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/i/ibus.md?ref_… The issue seems to be related to vala, so we should probably consider using -fpermissive - at least for now - too. The error (that halts the build) is: [ 329s] emojierapp.c: In function ‘emoji_application_save_selected_string’: [ 329s] emojierapp.c:306:60: error: passing argument 3 of ‘g_settings_set_strv’ from incompatible pointer type [-Wincompatible-pointer-types] [ 329s] 306 | g_settings_set_strv (_tmp11_, "favorites", _tmp12_); [ 329s] | ^~~~~~~ [ 329s] | | [ 329s] | gchar ** {aka char **} [ 329s] In file included from /usr/include/glib-2.0/gio/gio.h:137, [ 329s] from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:28, [ 329s] from /usr/include/gtk-3.0/gdk/gdk.h:32, [ 329s] from /usr/include/gtk-3.0/gtk/gtk.h:30, [ 329s] from emojierapp.c:30: [ 329s] /usr/include/glib-2.0/gio/gsettings.h:191:94: note: expected ‘const gchar * const*’ {aka ‘const char * const*’} but argument is of type ‘gchar **’ {aka ‘char **’} [ 329s] 191 | const gchar *const *value); [ 329s] | ~~~~~~~~~~~~~~~~~~~~^~~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 1225777] New: Package hplip does not build with gcc14 because of new errors
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225777 Bug ID: 1225777 Summary: Package hplip 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: Printing Assignee: jsmeix(a)suse.com Reporter: mjambor(a)suse.com QA Contact: jsmeix(a)suse.com 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 hplip 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 Fedora dealt with these issues as described at https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/h/hplip.md?ref… We seem to need at least https://bugs.launchpad.net/hplip/+bug/1997875 and https://bugs.launchpad.net/hplip/+bug/2048780 The error (that halts the build) is: [ 31s] prnt/hpps/pserror.c: In function ‘message’: [ 31s] prnt/hpps/pserror.c:27:10: error: type defaults to ‘int’ in declaration of ‘column’ [-Wimplicit-int] [ 31s] 27 | static column = 0 ; /* current screen column for message wrap */ [ 31s] | ^~~~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224773] Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c23 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(rbrown(a)suse.com) |needinfo?(iforster(a)suse.com | |) CC| |iforster(a)suse.com --- Comment #23 from Richard Brown <rbrown(a)suse.com> --- I don’t have a clue, the transactional-update maintainer might -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224773] Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c22 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown(a)suse.com Flags| |needinfo?(rbrown(a)suse.com) --- Comment #22 from Stefan Dirsch <sndirsch(a)suse.com> --- Re'adding Richard. He might be able to help here. I think he has much more background about such systems and Aeon in particular. Richard, we need to figure out why blacklisting nouveau driver doesn't work on Aeon. Do you have a clue? We have a modprobe.d snippet /usr/lib/modprobe.d/nvidia-default.conf with content blacklist nouveau This is now also in initrd. But it doesn't help. nouveau driver is still loaded during boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 0