September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1202215] llvm14 fails with glibc 2.36
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202215 http://bugzilla.opensuse.org/show_bug.cgi?id=1202215#c5 --- Comment #5 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1202215) was mentioned in https://build.opensuse.org/request/show/1001714 Factory / llvm13 https://build.opensuse.org/request/show/1001715 Factory / llvm12 https://build.opensuse.org/request/show/1001716 Factory / llvm11 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199909] NXP i.MX8MQ-EVK not able to recognize eMMC
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199909 https://bugzilla.suse.com/show_bug.cgi?id=1199909#c31 Matthias Brugger <mbrugger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(lubos.kocman@suse | |.com) --- Comment #31 from Matthias Brugger <mbrugger(a)suse.com> --- Lubos, can we take this issue into account when you take a decission on the quarterly update of the Leap 15.4 installer? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200919] [Kunpeng 920] Wrong enumerated PMU nodes crashes kernel
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1200919 https://bugzilla.suse.com/show_bug.cgi?id=1200919#c28 Matthias Brugger <mbrugger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #28 from Matthias Brugger <mbrugger(a)suse.com> --- this needs to be fixed in FW. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203027] No way of setting mount points for btrfs subvolumes in YaST
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203027 https://bugzilla.suse.com/show_bug.cgi?id=1203027#c6 --- Comment #6 from Richard Brown <rbrown(a)suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #4) > With the current implementation of libstorage-ng, the mount point of a > subvolume is always auto-calculated from the mount point of the file-system > and the path of the subvolume. Am I totally mis-remembering stuff but isn't there a general over-arching philosophy with YaST that when there is something auto-calculated or auto-decided by YaST, there should be some way of correcting any mistakes/unwanted decisions made there? Isn't that why the Installation Summary screen lets you review everything YaST is doing before the install starts? The fact that YaST is auto-calculating mount points for subvolumes and not giving users a chance to correct any mistakes and/or set mount points for any additional subvolumes sure still feels like a bug to me that runs counter to how we typically do everything else in YaST... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1196882] [pinephone] Installer takes a lot of time to provide feedback
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

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

1 0

[Bug 1203027] No way of setting mount points for btrfs subvolumes in YaST
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203027 https://bugzilla.suse.com/show_bug.cgi?id=1203027#c5 --- Comment #5 from Arvin Schnell <aschnell(a)suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #4) > With the current implementation of libstorage-ng, the mount point of a > subvolume is always auto-calculated from the mount point of the file-system > and the path of the subvolume. AFAIS there is not such a limitation in libstorage-ng. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1047852] New: knotify_libjack audio kcrash on pthread_key_create() at ../common/JackError.cpp:88
by bugzilla_noreply＠novell.com 07 Sep '22

07 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1047852 Bug ID: 1047852 Summary: knotify_libjack audio kcrash on pthread_key_create() at ../common/JackError.cpp:88 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE3 Assignee: anixx(a)opensuse.org Reporter: drankinatty(a)suddenlinkmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 731684 --> http://bugzilla.opensuse.org/attachment.cgi?id=731684&action=edit knotify_libjack wdebug kcrash file (the 6 is just the 6th one I saved) A knotify/libjack.so.0 crash will regularly occur once during a session. It may take a day or two for the bug to appear, but on access to sound theme sound (no one in particular, e.g. dialog-open, minimize, etc.) a kcrash report appears and the desktop sounds no longer play until you restart the desktop. This time it took 2 days 5:29 minutes under heavy use to occur. It is strangely random when it happens, but very consistent that it *will* happen. This is not new and has been around at least since 13.1 (it may go back to 11.4). I have experiences this on two separate laptops with 13.1 and Leap 42.2. (I really think it was there in 11.4, but I'm far too old to remember) I have attached a wdebug.kcrash that details the error. -- You are receiving this mail because: You are on the CC list for the bug.

2 33

[Bug 1202169] libwebkit2gtk3: Eclipse crashes webkit_web_context_get_default()
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202169 https://bugzilla.suse.com/show_bug.cgi?id=1202169#c18 --- Comment #18 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2022:3136-1: An update that solves one vulnerability and has one errata is now available. Category: security (important) Bug References: 1202169,1202807 CVE References: CVE-2022-32893 JIRA References: Sources used: SUSE OpenStack Cloud Crowbar 9 (src): webkit2gtk3-2.36.7-2.110.1 SUSE OpenStack Cloud 9 (src): webkit2gtk3-2.36.7-2.110.1 SUSE Linux Enterprise Software Development Kit 12-SP5 (src): webkit2gtk3-2.36.7-2.110.1 SUSE Linux Enterprise Server for SAP 12-SP4 (src): webkit2gtk3-2.36.7-2.110.1 SUSE Linux Enterprise Server 12-SP5 (src): webkit2gtk3-2.36.7-2.110.1 SUSE Linux Enterprise Server 12-SP4-LTSS (src): webkit2gtk3-2.36.7-2.110.1 SUSE Linux Enterprise Server 12-SP3-BCL (src): webkit2gtk3-2.36.7-2.110.1 SUSE Linux Enterprise Server 12-SP2-BCL (src): webkit2gtk3-2.36.7-2.110.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203027] No way of setting mount points for btrfs subvolumes in YaST
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203027 Arvin Schnell <aschnell(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 1191507] VUL-0: CVE-2021-41133: flatpak: Sandbox bypass via recent VFS-manipulating syscalls
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1191507 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0