April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222187] Cooling fans don't spins up on rx580
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222187 https://bugzilla.suse.com/show_bug.cgi?id=1222187#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(artem.ivanov@synt | |labs.com) CC| |artem.ivanov(a)syntlabs.com, | |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Exactly which version was your good-working kernel? If it's a regression, we need to narrow down the range. Please give the dmesg outputs from both good and bad-working kernels, as well as hwinfo outputs from both. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222193] New: blueman-sendto: ctivation via systemd failed for unit 'dbus-org.bluez.obex.service': Unit dbus-org.bluez.obex.service not found.
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222193 Bug ID: 1222193 Summary: blueman-sendto: ctivation via systemd failed for unit 'dbus-org.bluez.obex.service': Unit dbus-org.bluez.obex.service not found. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873954 --> https://bugzilla.suse.com/attachment.cgi?id=873954&action=edit var-log-zypp-history.txt.xz A fresh install of Leap 15.6 RC1 is capable of pairing with a phone. But it fails to send (and perhaps also receive) files: blueman-sendto[26154]: gi.repository.GLib.Error: g-io-error-quark: Fehler beim Aufruf von StartServiceByName für org.bluez.obex: Unit dbus-org.bluez.obex.service not found. (36) This is when selecting "Send file" in the "blueman-manger" application. I think this is supposed to work out of the box. Attached is the list of installed packages during the "default XFCE" installation. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222194] kubo ipfs tries to start before the network appears and fails with an error
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

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

1 0

[Bug 1221224] New: java-21-openjdk build-time race
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221224 Bug ID: 1221224 Summary: java-21-openjdk build-time race Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: fstrba(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1102408 Target Milestone: --- Found By: --- Blocker: --- Created attachment 873384 --> https://bugzilla.suse.com/attachment.cgi?id=873384&action=edit diff from build-compare While working on reproducible builds for openSUSE, I found that our java-21-openjdk binaries vary between 1-core and 4-core builds. https://rb.zq1.de/compare.factory-20240228/diffs/java-21-openjdk-compare.out has the diff (also attached) There may be additional issues from ASLR that I am still investigating. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c28 --- Comment #28 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- I get a 404 for that link. fwiw: If i remember correctly i disabled the touchpad that years ago in the bios. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222183] pcr-oracle fails to parse LOADER_CONF_EVENT_TAG_ID
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

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

1 0

[Bug 1222201] New: When booting with only a serial console, boot messages are not displayed.
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222201 Bug ID: 1222201 Summary: When booting with only a serial console, boot messages are not displayed. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: forgotten_u0-bnvADNc(a)user.net Reporter: william.brown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Booting TW micro with a serial console only such as: virt-install --connect=qemu:///system -n microtest.suse.firstyear.id.au --import --boot uefi --osinfo opensusetumbleweed --virt-type kvm --hvm --machine q35 --cpu host-passthrough --graphics none --serial pty --console pty,target_type=virtio --autoconsole text --network=bridge=net_20,model=virtio --rng /dev/urandom --tpm backend.type=emulator,backend.version=2.0,model=tpm-tis --vcpu 2 --memory 2048 --security type=dynamic --disk path=/mnt/libvirt/nvme/microtest.suse.firstyear.id.au.qcow2,bus=virtio,cache=none,sparse=no No output will be displayed on the serial console during init (but grub and tty will display) The kernel cmdline should be adjusted to show output on both consoles. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187545] AutoYaST does not validate the general/storage/proposal section
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1187545 https://bugzilla.suse.com/show_bug.cgi?id=1187545#c5 --- Comment #5 from Imobach Gonzalez Sosa <igonzalezsosa(a)suse.com> --- This is a validation problem but the profile should work. You can workaround the issue by disabling the validation temporarily. See https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-autoyast-creat…. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222152] Slowdowns in terminal emulators under GNOME X.org with binary nvidia driver
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222152 https://bugzilla.suse.com/show_bug.cgi?id=1222152#c2 Alynx Zhou <alynx.zhou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou(a)suse.com --- Comment #2 from Alynx Zhou <alynx.zhou(a)suse.com> --- This sounds really like this upstream issue: https://gitlab.gnome.org/GNOME/mutter/-/issues/3384 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219917] rasdaemon is missing dmidecode dependency on ppc64le
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219917 https://bugzilla.suse.com/show_bug.cgi?id=1219917#c8 --- Comment #8 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From sthoufee(a)in.ibm.com 2024-04-01 01:08 EDT------- We got following response from RAS Developement team. RAS team has no plans to own or support this tool. rasdaemon is specific to x86 platform and may not work on ppc64 at all. Powerpc has its own RAS tools which are shipped through following packages and available at https://github.com/power-ras/ ppc64-diag lsvpd servicelog rasdeamon mostly deals with MCE logs. On Power, for memory errors, predictive error analysis is done by pHyp/PRD as similar to rasdaemon on x86 platform. pHyp then delivers these predictive errors to linux as RTAS events which captured by rtas_errd daemon and logs into servicelog as serviceabile events (Call home event). We should check with SuSE on purpose of this tool on ppc64 and why do they think this will work on ppc64. Do we really need this tool on ppc64 ? Who is going to own/support this on ppc64 ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0