May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 1222343] New: protobuf linking issue
by bugzilla_noreply＠suse.com 06 Jul '24

06 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222343 Bug ID: 1222343 Summary: protobuf linking issue 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: Development Assignee: screening-team-bugs(a)suse.de Reporter: jonaski(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recently, I'm getting several linking errors while building strawberry on leap. Full log can be seen on https://build.opensuse.org/package/show/multimedia:apps/strawberry This happened a few weeks ago, and it seem to be the same issue on both Leap 15.5 and 15.6, it is not an issue on Tumbleweed or any other linux distribution (Fedora, Debian and Ubuntu builds fine). I suspect an issue with the protobuf library on Leap. From the build log: [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: CMakeFiles/strawberry-tagreader.dir/tagreaderworker.cpp.o: in function `google::protobuf::internal::ArenaStringPtr::SetBytes(void const*, unsigned long, google::protobuf::Arena*)': [ 76s] /usr/include/google/protobuf/arenastring.h:495:(.text+0x44e): undefined reference to `google::protobuf::internal::ArenaStringPtr::Set(absl::lts_20240116::string_view, google::protobuf::Arena*)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadertaglib.cpp.o): in function `google::protobuf::internal::ArenaStringPtr::Set(char const*, unsigned long, google::protobuf::Arena*)': [ 76s] /usr/include/google/protobuf/arenastring.h:470:(.text+0x9935): undefined reference to `google::protobuf::internal::ArenaStringPtr::Set(absl::lts_20240116::string_view, google::protobuf::Arena*)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: /usr/include/google/protobuf/arenastring.h:470:(.text+0x9976): undefined reference to `google::protobuf::internal::ArenaStringPtr::Set(absl::lts_20240116::string_view, google::protobuf::Arena*)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::SongMetadata::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:2565:(.text+0x1886): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::IsMediaFileRequest::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:2769:(.text+0x18a6): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::IsMediaFileResponse::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:3007:(.text+0x18c6): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::ReadFileRequest::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:3211:(.text+0x18e6): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::ReadFileResponse::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:3463:(.text+0x1906): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o):/home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:3939: more undefined references to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' follow [ 76s] collect2: error: ld returned 1 exit status -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1220190] New: AUDIT: drkonqi6
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1220190 Bug ID: 1220190 Summary: AUDIT: drkonqi6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- drkonqi is the crash handler for KDE applications. drkonqi6 will coexist in openSUSE for a while and needs to be reviewed: [ 93s] drkonqi6.x86_64: E: dbus-file-unauthorized (Badness: 10000) /usr/share/dbus-1/system.d/org.kde.drkonqi.conf (sha256 file digest default filter:233b3b98de2fc6b780c1eb9c3ab9b9f99b1949dfab951cababd7c5a717b8ee16 shell filter:233b3b98de2fc6b780c1eb9c3ab9b9f99b1949dfab951cababd7c5a717b8ee16 xml filter:3326c5271c6321c5b3a703d187443eef260d54aa7347bc8f05d9090a153a04bd) [ 93s] drkonqi6.x86_64: E: dbus-file-unauthorized (Badness: 10000) /usr/share/dbus-1/system-services/org.kde.drkonqi.service (sha256 file digest default filter:b99a6dc5943df0e641616dc4be3122fdd1d1b1c418df298c56008b50c5fb2b08 shell filter:b6f2a505903e2d8874d7da96a197944ab4a11f351f3db80ffeeec86d9eefd79a xml filter:<failed-to-calculate>) Package sources: https://build.opensuse.org/package/show/KDE:Frameworks/drkonqi6 -- You are receiving this mail because: You are on the CC list for the bug.

1 29

[Bug 1222446] New: cups-filters should require /usr/bin/pdftops
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222446 Bug ID: 1222446 Summary: cups-filters should require /usr/bin/pdftops Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: brunopitrus(a)hotmail.com QA Contact: jsmeix(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I was getting mysterious “Filter failed“ errors when trying to print. Enabling debug output from CUPS revealed that it was due to `/usr/lib/cups/filter/pdftops` trying to execute `pdftops` which is in the `poppler-tools` package which i did not have installed. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1217309] New: [RPi4] rebootmgr does not reboot the system
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1217309 Bug ID: 1217309 Summary: [RPi4] rebootmgr does not reboot the system Classification: openSUSE Product: openSUSE Leap Micro Version: 5.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Transactional Update Assignee: lubos.kocman(a)suse.com Reporter: mbrugger(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When trying to reboot the system, system services is shut down but no reboot happens. That leaves the system in a state without networking. > printi:~ # rebootmgrctl get-strategy > Reboot strategy: best-effort > printi:~ # rebootmgrctl get-window > Maintenance window is set to *-*-* 03:30:00, lasting 01h30m. > printi:~ # rebootmgrctl is-active > RebootMgr is active journalctl output can be found here: https://paste.opensuse.org/pastes/c0c9f158cadd Interestingly running > rebootmgrctl reboot now does actually reboot the system. -- You are receiving this mail because: You are on the CC list for the bug.

1 20