February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1207928] Rust 1.67 breaks rusticl build in Mesa:drivers (rust upstream fix available in git)
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207928 https://bugzilla.suse.com/show_bug.cgi?id=1207928#c12 --- Comment #12 from Stefan Dirsch <sndirsch(a)suse.com> --- Thanks. I agree. 3rd option would be to add the required patches to fix the issue. But I'm afraid cherry-picking them isn't trivial. Also they may need additional patches before you can apply them ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208003] Support EFI 32/64 bit mixed mode (Was: installation images do not support 32-bit EFI)
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208003 https://bugzilla.suse.com/show_bug.cgi?id=1208003#c17 --- Comment #17 from Steffen Winterfeldt <snwint(a)suse.com> --- Yes, that's also how I tested the isos. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204085] spice-vdagentd 0.22.1 doesn't work properly on guest
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1204085 https://bugzilla.suse.com/show_bug.cgi?id=1204085#c6 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |fvogt(a)suse.com, | |paolo.perego(a)suse.com Resolution|FIXED |--- Flags| |needinfo?(paolo.perego@suse | |.com) --- Comment #6 from Fabian Vogt <fvogt(a)suse.com> --- The service is meant to be started by a udev rule, which works fine here. Maybe you actually hit https://bugs.kde.org/show_bug.cgi?id=455992? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207295] bpftrace: SIGSEGV on almost any simple program
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207295 http://bugzilla.opensuse.org/show_bug.cgi?id=1207295#c2 Shung-Hsi Yu <shung-hsi.yu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #2 from Shung-Hsi Yu <shung-hsi.yu(a)suse.com> --- Sorry for the late response and thanks to Jiri for looking into this. This issue was indeed the switch to LLVM 15. Since LLVM 15, opaque pointer[1] becomes the default, resulting in getNonOpaquePointerElementType() returning NULL and causing segfault. I'm updating bpftrace to v0.17 which properly supports opaque pointers[1] to fix this. 1: https://llvm.org/docs/OpaquePointers.html 2: https://github.com/iovisor/bpftrace/pull/2385 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206421] libvulkan_intel-32bit isn't installed automatically with wine
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1206421 https://bugzilla.suse.com/show_bug.cgi?id=1206421#c4 --- Comment #4 from Marcus Meissner <meissner(a)suse.com> --- can i install this on all systems or are there problems? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208052] Duplicate binaries: crash / crash-trace
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208052 https://bugzilla.suse.com/show_bug.cgi?id=1208052#c1 David Mair <dmair(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|jeffm(a)suse.com |dmair(a)suse.com --- Comment #1 from David Mair <dmair(a)suse.com> --- I probably caused so I��ll correct it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207837] amdgpu: externals displays don't work when booting with plugged in docking station
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207837 https://bugzilla.suse.com/show_bug.cgi?id=1207837#c4 --- Comment #4 from Jiri Belka <jiri.belka(a)suse.com> --- After a wake from suspend, the external monitors still do not work (although they were working before the suspend itself). I will upload logs later. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207962] [SELinux] systemd-timesyncd cannot start due to missing permissions for /run/systemd (/var/run/systemd)
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207962 https://bugzilla.suse.com/show_bug.cgi?id=1207962#c6 --- Comment #6 from Johannes Segitz <jsegitz(a)suse.com> --- yes, of course. In a root console: zypper ar -p 80 https://download.opensuse.org/repositories/home:/jsegitz:/branches:/securit… ( this adds the repository to your system ) zypper ref ( you're asked to accept the repository key. It's enough to accept it temporary, as you can remove the repo later on) zypper install selinux-policy-targeted ( that will either directly present you the option to switch to the policy in my repository or it will show you the command to force the install) after that just reboot and the issues should be gone. Happy testing :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207390] [Build 20230121] yast2 rmt: 'open firewall' is grayed out
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207390 Joaqu�n Rivera <jeriveramoya(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeriveramoya(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207948] Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic
by bugzilla_noreply＠suse.com 09 Feb '23

09 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207948 https://bugzilla.suse.com/show_bug.cgi?id=1207948#c14 --- Comment #14 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Martin Jambor from comment #9) > > Does pstore store anything to efi afterall? > > I tried following > https://blogs.oracle.com/linux/post/pstore-linux-kernel-persistent-storage- > file-system > > I got as far as "cat /sys/module/pstore/parameters/backend" resulting > in "efi" but no file ever appeared in /sys/fs/pstore Weird. It would be also some /sys/firmware/efi/efivars/[Dd]ump*. But apparently, nothing is logged. Is the service running: systemctl status systemd-pstore.service ? > > Do you have kdump set up? > > I don't think so. So no, unless it is somehow on default. It should be a matter of zypper in kdump systemctl enable kdump Add something like crashkernel=192M to the kernel commandline. Reboot systemctl status kdump /sys/kernel/kexec_loaded should return 1. /boot/initrd-kdump should exist crash it by s2disk /var/crash should contain a folder after a crash. The blinking LED should not happen, the kdump kernel should be loaded instead. Thinking about it, it probably won't work. The resume kernel+initrd probably didn't manage to load kdump yet at this phase. Or maybe it jumped to the suspended kernel already and the suspended kernel crashes. In which case it could work. (In reply to Martin Jambor from comment #12) > (In reply to Jiri Slaby from comment #6) > > Yeah and I also asked you about: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/ > > Documentation/power/basic-pm-debugging.rst > > > > What last step (from [freezer, devices, ...]) does not expose the crash? > > None of them exposes it - even "core" returns fine without any > problems - except for "none" which of course results in the panic. Which means the BIOS does something weird during suspend. Or kernel does something weird during resume. > Funny thing, when triggering the suspend with > > echo platform > /sys/power/disk > echo disk > /sys/power/state > > (as opposed to "systemctl hibernate") the virtual console echo works > at the end of the unsuccessful resuming from disk. I.e. I can see the > letters I type - but there is no reaction from bash or anything, the > next bash prompt is not displayed either - until the panic when > everything stops... is it perhaps some watchdog that is triggering it? Another note: klog.service makes tty10 the console. Can you comment out the whole line containing /usr/bin/setlogcons in /usr/lib/systemd/system/klog.service? And also ignore_loglevel or loglevel=7 kernel parameters could help to show something (added on top of no_console_suspend). -- You are receiving this mail because: You are on the CC list for the bug.

1 0