May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1224364] New: btrfsmaintenance 0.5.1: openqa test failing at "btrfs scrub status"
by bugzilla_noreply＠suse.com 09 Jul '24

09 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1224364 Bug ID: 1224364 Summary: btrfsmaintenance 0.5.1: openqa test failing at "btrfs scrub status" 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: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, The SR#1172967 with the update to 0.5.1 fails when running: btrfs scrub status / | grep -e "Status:.*finished" openQA test in scenario opensuse-Staging:J-Staging-JeOS-for-kvm-and-xen-x86_64-jeos-filesystem@uefi-staging-virtio-2G fails in [btrfsmaintenance](https://openqa.opensuse.org/tests/4191091/modules/btrfsma… This is blocking the package to be accepted into Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1223413] New: [TRACKER] FTBFS due to boost 1.85
by bugzilla_noreply＠suse.com 09 Jul '24

09 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1223413 Bug ID: 1223413 Summary: [TRACKER] FTBFS due to boost 1.85 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: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- A non exhaustive list of packages failing to build directly because boost 1.85: * hugin https://bugzilla.opensuse.org/show_bug.cgi?id=1223377 (FIXED) * rstudio https://bugzilla.opensuse.org/show_bug.cgi?id=1223378 * znc https://bugzilla.opensuse.org/show_bug.cgi?id=1223381 * lucene++ SR https://build.opensuse.org/request/show/1170262 * uhd * FreeCAD * wt * sfcgal -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222156] New: After an upgrade the graphical interface no longer works
by bugzilla_noreply＠suse.com 09 Jul '24

09 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 Bug ID: 1222156 Summary: After an upgrade the graphical interface no longer works Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: rm.canella(a)gmail.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On my HP 255 G5 Notebook PC, following "zypper dup --no-allow-vendor-change" (openSUSE-20231218-0) the system no longer starts in graphics mode. - I did some checks and the problem seems to be on the "radeonsi_dri" driver; The following error message appears in the dmesg: [ 84.119680] gnome-shell[1557]: segfault at 40 ip 00007ff2ca32b98d sp 00007ffe59c27170 error 4 in radeonsi_dri.so[7ff2c9c91000+1476000] likely on CPU 1 (core 1, socket 0) - Doing an lspci the video card is: 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R3 Graphics] (rev 40) - And the following is the output of the zypper info kernel-firmware-radeon command: Information for package kernel-firmware-radeon: ------------------------------------------------- Repository : Main Repository (OSS) Name : kernel-firmware-radeon Version: 20240322-1.1 Arch : noarch Vendor: openSUSE Installed Size: 3.3 MiB Installed : Yes (automatically) Status: up-to-date Source package : kernel-firmware-20240322-1.1.src Upstream URL: https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/ Summary : Kernel firmware files for Radeon graphics driver Description: This package contains compressed kernel firmware files for Radeon graphics driver. -- You are receiving this mail because: You are on the CC list for the bug.

1 40

[Bug 1224536] New: Package dia does not build with gcc14 because of a call argument with an incompatible pointer type
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1224536 Bug ID: 1224536 Summary: Package dia does not build with gcc14 because of a call argument with an incompatible pointer type 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 fails to compile. This can be seen online at: https://build.opensuse.org/package/live_build_log/home:rguenther:plgrnd/dia… It can be reproduced locally with command: osc build --clean --alternative-project home:rguenther:nextgcc The error (that halts the build) is: [ 66s] custom_object.c: In function 'custom_setup_properties': [ 66s] custom_object.c:382:49: error: passing argument 1 of '(info->props + (sizetype)((long unsigned int)i * 88))->ops->get_data_size' from incompatible pointer type [-Wincompatible-pointer-types] [ 66s] 382 | size = info->props[i].ops->get_data_size (&info->props[i]); [ 66s] | ^~~~~~~~~~~~~~~ [ 66s] | | [ 66s] | PropDescription * {aka struct _PropDescription *} [ 66s] custom_object.c:382:49: note: expected 'Property *' {aka 'struct _Property *'} but argument is of type 'PropDescription *' {aka 'struct _PropDescription *'} -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1225772] New: Package bdfresize does not build with gcc14 because of old autoconf
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225772 Bug ID: 1225772 Summary: Package bdfresize does not build with gcc14 because of old autoconf 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 bdfresize 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 Since the last release appears to be from 2001, either using -std=gnu89 (but see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115310) or -fpermissive seems appropriate. The error (that halts the build) is: [ 11s] checking for gcc... gcc [ 11s] checking whether the C compiler (gcc -O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -g -flto=auto) works... no [ 11s] configure: error: installation or configuration problem: C compiler cannot create executables. ...most probably because main in a generated snippet misses a return type. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

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

08 Jul '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 5

[Bug 1217688] New: mariadb: a table is missing inserted entries from concurrent processes
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1217688 Bug ID: 1217688 Summary: mariadb: a table is missing inserted entries from concurrent processes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://jira.mariadb.org/browse/MDEV-32871 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: danilo.spinella(a)suse.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871082 --> https://bugzilla.suse.com/attachment.cgi?id=871082&action=edit db inserter With mariadb: 11.0.2, 11.1.2 and 11.1.3 (from server:database): From my c++ code, using connector-c, I do: SET autocommit=0 CREATE TABLE IF NOT EXISTS sources(id INTEGER AUTO_INCREMENT PRIMARY KEY, src VARCHAR(1024) NOT NULL UNIQUE) INSERT IGNORE INTO sources(src) VALUES (?) START TRANSACTION And then a lot of: INSERT IGNORE INTO sources(src) VALUES ('src-003431-00001') src is composed of pid and values from 0 to 49. So they are all unique. Finally, I do: COMMIT If I run 10 instances in parallel like: for aa in {1..10} ; do ./db & done ; wait I see: select count(id), substr(src,5,6) as sss from sources group by sss; +-----------+--------+ | count(id) | sss | +-----------+--------+ | 50 | 003430 | | 50 | 003431 | | 50 | 003432 | | 40 | 003433 | | 50 | 003434 | | 50 | 003435 | | 50 | 003436 | | 50 | 003437 | | 50 | 003438 | | 50 | 003439 | +-----------+--------+ I.e. Some of pids stored only last 40 values, numbers 0..9 are missing in the table: select src from sources where src like '%003433%' order by src ; +------------------+ | src | +------------------+ | src-003433-00010 | | src-003433-00011 | | src-003433-00012 | | src-003433-00013 | | src-003433-00014 | | src-003433-00015 | | src-003433-00016 | | src-003433-00017 | | src-003433-00018 | | src-003433-00019 | | src-003433-00020 | | src-003433-00021 | | src-003433-00022 | | src-003433-00023 | | src-003433-00024 | | src-003433-00025 | | src-003433-00026 | | src-003433-00027 | | src-003433-00028 | | src-003433-00029 | | src-003433-00030 | | src-003433-00031 | | src-003433-00032 | | src-003433-00033 | | src-003433-00034 | | src-003433-00035 | | src-003433-00036 | | src-003433-00037 | | src-003433-00038 | | src-003433-00039 | | src-003433-00040 | | src-003433-00041 | | src-003433-00042 | | src-003433-00043 | | src-003433-00044 | | src-003433-00045 | | src-003433-00046 | | src-003433-00047 | | src-003433-00048 | | src-003433-00049 | +------------------+ Is this a bug in my program (attached) or the db? If I look into the general log, I see the inserts which apparently did not get into the table: grep src-003433 /tmp/glog 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00000') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00000') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00000') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00000') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00000') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00001') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00002') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00003') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00004') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00005') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00006') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00007') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00008') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00009') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00010') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00010') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00011') 24 Execute INSERT IGNORE INTO sources(src) VALUES ('src-003433-00012') Note also the repeated inserts. They come from a deadlock, so I repeat the exec in a loop (see the code). Dockers with mariadb:latest (11.2.2) mariadb:11.1.3 mariadb:11.1.2 all run FINE too. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1223615] New: Nextcloud-desktop can't add multiple accounts
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1223615 Bug ID: 1223615 Summary: Nextcloud-desktop can't add multiple accounts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: karlggest(a)yahoo.es QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Seems since some Nextcloud-desktop versions app can't show add account option in the menu. Steps: 1. Start Nextcloud-desktop 2. Click on the app on system tray, main window appears. 3. Click on dropdown menu. Add accounts appears. 4. Add the first account. Complain all details and finish. 5. Go to steps 2, 3 and 4 again. Add accounts option does not appear I try app from standard repo and flatpak package. Both fails. Appimage from https://nextcloud.com/install/#install-clients works as expected. Extra: Another packages even in another distros fails in the same way: https://help.nextcloud.com/t/nextcloud-desktop-client-with-support-for-mult… https://help.nextcloud.com/t/desktop-clients-number-of-multiple-accounts/10… Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1225633] New: Migration from MicroOS Desktop to Aeon failed on none EFI system
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225633 Bug ID: 1225633 Summary: Migration from MicroOS Desktop to Aeon failed on none EFI system Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: vortex(a)z-ray.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875210 --> https://bugzilla.suse.com/attachment.cgi?id=875210&action=edit tik install log file Hey there, was about to migrate one of my MicroOS Desktop installs to Aeon using the Aeon installer image. After it had backed up the old home, installing the new system and moving the home directory back it failed with the error message: "Command /usr/sbin/efibootmgr -o FAILED" I am aware that Aeon does not support none EFI systems. Might it be possible to do a EFI check before installing everything and tell the user? The full log does confirm that EFI is not enabled. It was just my idiocy that I forgot to enable EFI on my old Laptop beforehand. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223455] New: Power mode does not enter power saver
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1223455 Bug ID: 1223455 Summary: Power mode does not enter power saver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: pocketfullofmarbles(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When the battery drops to 20% power-profiles-daemon should automatically enter the powersave mode but this expected behavior does not happen on tumbleweed (gnome), also tested in opensuse tumbleweed live image(gnome) encountered the same problem. Otherwise the gnome power profiles wtih power-profiles-daemon work as expected. My laptops hardware probes if it helps: https://linux-hardware.org/?computer=c3ac730fb235 -- You are receiving this mail because: You are on the CC list for the bug.

1 2