July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222695] lensfun‑update‑data command does not work
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222695 https://bugzilla.suse.com/show_bug.cgi?id=1222695#c3 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(opendreas(a)gmail.c | |om) CC| |opendreas(a)gmail.com, | |pgajdos(a)suse.com --- Comment #3 from Petr Gajdos <pgajdos(a)suse.com> --- Yeah, more info would be beneficial to understand what issue you are facing. On Tubleweed and 15.5: as root: # lensfun-update-data Reading http://lensfun.sourceforge.net/db/versions.json … Reading http://wilson.bronger.org/lensfun-db/versions.json … Successfully updated the database in /var/lib/lensfun-updates/version_1. # as a user: $ lensfun-update-data Info: root privileges needed for updating the system database. Info: updating user DB in '/home/user/.local/share/lensfun/updates' Reading http://lensfun.sourceforge.net/db/versions.json … Reading http://wilson.bronger.org/lensfun-db/versions.json … Info: No newer database was found for last installed Lensfun. $ Just random thoughts without knowing much about lensfun: Is it new in 15.6 and wasn't present in 15.5? Some forgotten alias, somewhere? Do you have lensfun-data package installed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227457] Snapper error message after choosing System's Log in Yast via the shell
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227457 https://bugzilla.suse.com/show_bug.cgi?id=1227457#c7 --- Comment #7 from Alberto Planas Dominguez <aplanas(a)suse.com> --- Hi Sarah, what bootloader are you using? Is this a fresh install? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227457] Snapper error message after choosing System's Log in Yast via the shell
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227457 https://bugzilla.suse.com/show_bug.cgi?id=1227457#c6 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|rbrown(a)suse.com |aplanas(a)suse.com --- Comment #6 from Richard Brown <rbrown(a)suse.com> --- sdbootutil actual maintainer -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225063] [Firmware Bug]: CPU 0: APIC ID mismatch. CPUID: 0x0000 APIC: 0x0010
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225063 https://bugzilla.suse.com/show_bug.cgi?id=1225063#c6 --- Comment #6 from John Shand <jshand2013(a)gmail.com> --- (In reply to Takashi Iwai from comment #5) > The early 6.9.x kernel had some issues. Please retest with the latest 6.9.x > kernel. i'm afraid it still shows with this kernel: Linux johns-pc 6.9.7-1-default #1 SMP PREEMPT_DYNAMIC Fri Jun 28 05:50:47 UTC 2024 (a5efffa) x86_64 x86_64 x86_64 GNU/Linux i guess i'll wait and see if 6.9.8 will do the same -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227457] Snapper error message after choosing System's Log in Yast via the shell
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227457 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227457] Snapper error message after choosing System's Log in Yast via the shell
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227457 https://bugzilla.suse.com/show_bug.cgi?id=1227457#c5 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de Assignee|yast2-maintainers(a)suse.de |rbrown(a)suse.com Component|YaST2 |Other --- Comment #5 from Stefan Hundhammer <shundhammer(a)suse.com> --- -> sdbootutil-snapper maintainer. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227457] Snapper error message after choosing System's Log in Yast via the shell
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227457 https://bugzilla.suse.com/show_bug.cgi?id=1227457#c4 --- Comment #4 from Stefan Hundhammer <shundhammer(a)suse.com> --- As usual, please ALWAYS attach y2logs generated with the supplied 'save_y2logs' script. I am not going to reverse-engineer all that stuff that would be helpful here from just a lone y2logs file. It frustrates me to no end that I have to keep telling this even to people who have been working with the system for so many years. https://en.opensuse.org/openSUSE:Report_a_YaST_bug#I_attached_/var/log/YaST… In this case, I would have looked at the zypper history, the rpm-qa file and the storage setup in storage/ and storage-inst/. One suspicious thing here, though: >> y2-01-partitioner.log: 2022-04-09 17:18:11 <1> linux.fritz.box(3760) [Ruby] >> y2storage/storage_manager.rb(configure_snapper?):513 >> Not a fresh installation. Don't configure Snapper. >> >> y2-06-partitioner.log: 2022-06-09 13:57:16 <1> linux.fritz.box(11117) [Ruby] >> y2storage/storage_manager.rb(configure_snapper?):513 >> Not a fresh installation. Don't configure Snapper. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 1227457] Snapper error message after choosing System's Log in Yast via the shell
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227457 https://bugzilla.suse.com/show_bug.cgi?id=1227457#c3 --- Comment #3 from Stefan Hundhammer <shundhammer(a)suse.com> --- On my TW VM: >> [sh @ balrog-tw-dev] ~ 1 % ls -l /usr/lib/snapper/plugins >> >> total 8 >> -rwxr-xr-x 1 root root 7614 Jun 7 04:13 grub >> >> >> [sh @ balrog-tw-dev] ~ 2 % rpm -qf /usr/lib/snapper/plugins/grub >> >> grub2-snapper-plugin-2.12-20.1.noarch >> >> >> [sh @ balrog-tw-dev] ~ 3 % sudo zypper search "*snapper*" | grep plug >> >> i | grub2-snapper-plugin | Grub2's snapper plugin | package >> | python3-dnf-plugin-snapper | Snapper Plugin for DNF | package >> | sdbootutil-snapper | plugin script for snapper | package >> i | snapper-zypp-plugin | A zypp commit plugin for calling snapper | package >> >> >> [sh @ balrog-tw-dev] ~ 4 % osc maintainer -e sdbootutil-snapper >> >> Defined in project: devel:microos >> bugowner of sdbootutil-snapper : >> rbrown(a)suse.com >> >> maintainer of sdbootutil-snapper : >> lnussel(a)suse.com, kukuk(a)suse.com, rbrown(a)suse.com, fvogt(a)suse.com, dcermak(a)suse.com, - -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227457] Snapper error message after choosing System's Log in Yast via the shell
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227457 https://bugzilla.suse.com/show_bug.cgi?id=1227457#c2 --- Comment #2 from Stefan Hundhammer <shundhammer(a)suse.com> --- Whatever happened here, I am very sure it's not the fault of that YaST journal module. Rather, it's probably something that happened just before that, and calling any YaST module just made the problem visible: As you know, we are creating a pre-snapshot when starting any of them, and a post-snapshot when they are finished. This is done in the YaST startup script: https://github.com/yast/yast-yast2/blob/master/scripts/yast2#L187-L205 -- You are receiving this mail because: You are on the CC list for the bug.

1 0