April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1185542] 32 bit Tumbleweed failing to boot with the 5.12.0-1-pae kernel must revert to 5.11.16-1-pae kernel.
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1185542 Paul Graff <pj.opensuse(a)gmx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|64bit |i586 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193582] Gedit, Codecomment plugin broken
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193582 https://bugzilla.suse.com/show_bug.cgi?id=1193582#c2 Sebastian Wagner <sebix+novell.com(a)sebix.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED CC| |sebix+novell.com(a)sebix.at --- Comment #2 from Sebastian Wagner <sebix+novell.com(a)sebix.at> --- I believe this is fixed, as the request was merged and Leap 15.3 is out of support too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1220592] Installation of virtiofsd-1.10.1-3.1.x86_64 fails on TW snapshot 2024227
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220592 https://bugzilla.suse.com/show_bug.cgi?id=1220592#c32 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- CC| |martin.wilck(a)suse.com Status|RESOLVED |REOPENED --- Comment #32 from Martin Wilck <martin.wilck(a)suse.com> --- For me, the problem still occurs, apparently because I've set ZYPP_SINGLE_RPMTRANS=1. Before anyone asks, I know it's tech preview; I like the feature, and I have it enabled as sort of a "beta tester" to find issues with it, like I just did. While I can work around this easily, ZYPP_SINGLE_RPMTRANS has been around for 3 years. Quite a few people are waiting eagerly for it to leave tech preview state, and even become the default, on openSUSE. We should stop pushing workarounds for issues like this that are only effective if this variable is not set. I assume that replacing %pre with %pretrans in Ben's fix would do the trick. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222200] New: Plasma 6 System Tray does not display Qsynth icon.
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222200 Bug ID: 1222200 Summary: Plasma 6 System Tray does not display Qsynth icon. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: pj.opensuse(a)gmx.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Qsynth tray icon is now invisible in Plasma 6. Was visible in Plasma 5. Icon displays if opening an instance of VLC and then closing VLC. Qsynth icon is then displayed in System Tray. Thinkcentre-M57p:/usr/share/icons/hicolor/scalable/apps> find /usr/share/icons -name "*qsynth*" /usr/share/icons/hicolor/32x32/apps/org.rncbc.qsynth.png /usr/share/icons/hicolor/scalable/apps/org.rncbc.qsynth.svg /usr/share/icons/hicolor/scalable/apps/org.rncbc.qsynth-tray.svg /usr/share/icons/hicolor/scalable/apps/qsynth-tray.svg Thinkcentre-M57p:/usr/share/icons/hicolor/scalable/apps> -Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 https://bugzilla.suse.com/show_bug.cgi?id=1222186#c24 --- Comment #24 from T Adams <timothyadams(a)ymail.com> --- (In reply to robert spitzenpfeil from comment #23) > The problem is 2-fold. > > The changes in vboxdrv.sh should leave you with correct folder permissions > after boot. > > The changes to VBoxCreateUSBNode.sh take care of device node permissions. > > > IMO you need both. So, I should make the changes in: https://bugzilla.suse.com/attachment.cgi?id=873974&action=diff for vboxdrv.sh and also the changes in: https://bugzilla.suse.com/attachment.cgi?id=873963&action=diff for VBoxCreateUSBNode.sh. (Including the permission changes in lines 50 and 52) Is that correct? If so, I'll give it a try. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221361] /etc/profile.d/alljava.csh sets JAVA_HOME incorrectly
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221361 https://bugzilla.suse.com/show_bug.cgi?id=1221361#c9 --- Comment #9 from Ruediger Oertel <ro(a)suse.com> --- yes, but apparently not just discard stderr which is what I wanted to do when using command output to set a variable. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 https://bugzilla.suse.com/show_bug.cgi?id=1222186#c23 --- Comment #23 from robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> --- The problem is 2-fold. The changes in vboxdrv.sh should leave you with correct folder permissions after boot. The changes to VBoxCreateUSBNode.sh take care of device node permissions. IMO you need both. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221877] New: aarch64 read/access watchpoint not triggered with access > 8 bytes, and gdb hangs
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221877 Bug ID: 1221877 Summary: aarch64 read/access watchpoint not triggered with access > 8 bytes, and gdb hangs Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This is a bug to track two related upstream PRs, one for gdb and one for the kernel: - https://sourceware.org/bugzilla/show_bug.cgi?id=31486 "[gdb/tdep, aarch64] Hang when hitting access watchpoint on M1" - https://bugzilla.kernel.org/show_bug.cgi?id=218628 "Aarch64 inexact watchpoint address make SIGTRAP hard to interpret" Sofar I only managed to reproduce the problem on macbook M1, but it might also occur with new server hardware supporting SVE or the MOPS feature. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222098] tpm resource manager - tpm2_save-context failed with error 0x0901
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222098 https://bugzilla.suse.com/show_bug.cgi?id=1222098#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- FWIW, get_maintainers gives: Peter Huewe <peterhuewe(a)gmx.de> (maintainer:TPM DEVICE DRIVER) Jarkko Sakkinen <jarkko(a)kernel.org> (maintainer:TPM DEVICE DRIVER) Jason Gunthorpe <jgg(a)ziepe.ca> (reviewer:TPM DEVICE DRIVER) linux-integrity(a)vger.kernel.org (open list:TPM DEVICE DRIVER) linux-kernel(a)vger.kernel.org (open list) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222098] tpm resource manager - tpm2_save-context failed with error 0x0901
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222098 https://bugzilla.suse.com/show_bug.cgi?id=1222098#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- It's no longer a wild west as in 20 years ago, and there is no much reason to hesitate. It's really better you reporting it since you have the specific system and program to test with, and have better understanding around the TPM handling from user-space side. (Though, in the end it might be unchanged, as the issue could be a firmware issue; I thought the value TPM2_PT_CONTEXT_GAP_MAX is read from the system, not what the kernel defines?) When you reporting, feel free to put me (tiwai(a)suse.de) to Cc in case you need assistance from the distro kernel side. -- You are receiving this mail because: You are on the CC list for the bug.

1 0