November 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1204710] New: LD_DEBUG=bindings provides no useful output on TW
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204710 Bug ID: 1204710 Summary: LD_DEBUG=bindings provides no useful output on TW 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: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- LD_DEBUG=bindings provides almost no useful output on Tumbleweed: # rpm -q glibc glibc-2.36-5.1.x86_64 # LD_DEBUG=bindings /bin/ls 19916: 19916: calling init: /lib64/ld-linux-x86-64.so.2 19916: 19916: 19916: calling init: /lib64/libc.so.6 19916: 19916: 19916: calling init: /lib64/libpcre2-8.so.0 19916: 19916: 19916: calling init: /lib64/libcap.so.2 19916: 19916: 19916: calling init: /lib64/libselinux.so.1 19916: 19916: 19916: initialize program: /bin/ls 19916: 19916: 19916: transferring control: /bin/ls 19916: lib64 sbin usr On Leap 15.3, I get lots of useful binding information instead: # LD_DEBUG=bindings /bin/ls 1149: binding file linux-vdso.so.1 [0] to linux-vdso.so.1 [0]: normal symbol `__vdso_clock_gettime' [LINUX_2.6] 1149: binding file linux-vdso.so.1 [0] to linux-vdso.so.1 [0]: normal symbol `__vdso_gettimeofday' [LINUX_2.6] 1149: binding file linux-vdso.so.1 [0] to linux-vdso.so.1 [0]: normal symbol `__vdso_time' [LINUX_2.6] 1149: binding file linux-vdso.so.1 [0] to linux-vdso.so.1 [0]: normal symbol `__vdso_getcpu' [LINUX_2.6] 1149: binding file linux-vdso.so.1 [0] to linux-vdso.so.1 [0]: normal symbol `__vdso_clock_getres' [LINUX_2.6] ... -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1204313] chronyd not ready when target time-sync.target is reached
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204313 https://bugzilla.suse.com/show_bug.cgi?id=1204313#c2 --- Comment #2 from Axel Braun <axel.braun(a)gmx.de> --- I found chrony-wait.service in between, which should fix it as well. Close the bug as WFM? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200616] Returning from SMM crashes 64bit KVM guest kernel
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1200616 https://bugzilla.suse.com/show_bug.cgi?id=1200616#c12 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #12 from Jiri Slaby <jslaby(a)suse.com> --- Merged to upstream as: 055f37f8 KVM: x86: emulator: update the emulation mode after rsm d087e0f7 KVM: x86: emulator: introduce emulator_recalc_and_set_mode So I pushed it to stable. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204324] hostapd won't start 5GHz network as AP since 15.4. 2.4GHz is OK, using Ath9k
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204324 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |cfamullaconrad(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204930] opencv: Segmentation fault
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204930 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |stefan.bruens(a)rwth-aachen.d | |e -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204360] Fix determination for canonical path of “/boot/grub2” (by a distribution upgrade)
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204360 https://bugzilla.suse.com/show_bug.cgi?id=1204360#c1 Michael Chang <mchang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mchang(a)suse.com, | |systemd-maintainers(a)suse.de Flags| |needinfo?(systemd-maintaine | |rs(a)suse.de) --- Comment #1 from Michael Chang <mchang(a)suse.com> --- (In reply to Markus Elfring from comment #0) > Created attachment 862208 [details] > error logs as background information for another questionable software > upgrade attempt > > I came along the need to try another software repair out by the means of the > image ��openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20221013-Media.iso��. > > I could configure my software repositories then. > The screen ��Installation Settings�� was finally presented with the following > hint after a promising automatic software package selection. > > �� > Booting > > Analysing your system�� > > > The following information was displayed by a dialogue box. > ��YaST2 <2> > > Error > > Execution of command "[["/usr/bin/grub2-editenv", "list"]]" failed. > Exit code: 1 > Error output: /usr/bin/grub2-editenv: error: failed to get canonical path of > `/boot/grub2'. > �� It seems /boot is a separate partition > $["file":"/boot", "freq":0, "mntops":"data=ordered,noauto,comment=systemd.automount", "passno":2, "spec":"UUID=075b6893-1e36-4e57-bdc6-b261a110fe08", "vfstype":"ext3"] ... but didn't get mounted rightfully due to systemd.automount units missing? > 2022-10-16 18:55:52 <3> linux.fritz.box(4165) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Unit boot.mount does not exist, proceeding anyway. > 2022-10-16 18:55:52 <3> linux.fritz.box(4165) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Unit home.mount does not exist, proceeding anyway. > 2022-10-16 18:55:52 <3> linux.fritz.box(4165) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Created symlink /run/systemd/system/boot.mount �� /dev/null. > 2022-10-16 18:55:52 <3> linux.fritz.box(4165) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Created symlink /run/systemd/system/home.mount �� /dev/null. > 2022-10-16 18:55:52 <3> linux.fritz.box(4165) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Created symlink /run/systemd/system/tmp.mount �� /dev/null. > 2022-10-16 18:55:52 <3> linux.fritz.box(4165) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Created symlink /run/systemd/system/var-lib-nfs-rpc_pipefs.mount > If so that would lead to any unspecified error IMHO. > > > See also information from previous clarification attempts: > * 2022-10-15 > Fixing components related to software snapshot ��20221013�� > > https://forums.opensuse.org/showthread.php/576670-Fixing-components-related- > to-software-snapshot-%E2%80%9C20221013%E2%80%9D > > * 2021-06-17 > Execution failure for ��grub2-editenv�� (from snapshot 20210615?) > https://bugzilla.opensuse.org/show_bug.cgi?id=1187471#c2 This was a different problem of missing command grub2-editenv itself which seem to have been fixed as the issue got reported upon executing it. > > * 2020-10-21 > [Build 20201020] openQA test fails in await_install: grub2-install fails > for i386-pc > https://bugzilla.opensuse.org/show_bug.cgi?id=1177956 This was fixed already. I have changed it's resolution accordingly. > > > How will the chances evolve to fix the affected software components? As a start we can check with systemd-maintainers to get better understanding the consequence of missing automount unit file mentioned above. Hi Fabian or Thomas, Would you please help to clarify on that ? Thanks in advanced. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204931] sypder-lang should be recommended and not required by spyer
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204931 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |code(a)bnavigator.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202950] Offline Upgrade to 15.4 stops before starting installer
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1202950 https://bugzilla.suse.com/show_bug.cgi?id=1202950#c14 --- Comment #14 from Lukas Ocilka <locilka(a)suse.com> --- And BTW, my feeling is that this is probably not connected with YaST itself, but rather with the videocard driver, Kernel or something like that so maybe we are not the best team for debugging the problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204943] xterm segfaults, probably
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204943 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |meissner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202950] Offline Upgrade to 15.4 stops before starting installer
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1202950 https://bugzilla.suse.com/show_bug.cgi?id=1202950#c13 --- Comment #13 from Lukas Ocilka <locilka(a)suse.com> --- Logs show that the Installer has been started, and it has been started in text mode as requested. Nothing really suspicious for the first sight, except "FAT-fs (sdf1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck." in 'messages' which IMO should not be causing this behavior. There's one more thing you could do if you had more computers: try installing/updating the system using ssh: https://en.opensuse.org/SDB:Linuxrc#p_ssh (search for "ssh" option) # use ssh and set ssh password ssh=1 sshpassword=foobar123 when the installation system boots, it tells you the IP to connect to remotely and you just run `yast` to start it. In that case, the display is not used for YaST and it might work. You may also try to look around using another ssh connection. -- You are receiving this mail because: You are on the CC list for the bug.

1 0