July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225861] Package libyui does not build with gcc14
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225861 https://bugzilla.suse.com/show_bug.cgi?id=1225861#c2 --- Comment #2 from Stefan Hundhammer <shundhammer(a)suse.com> --- https://github.com/libyui/libyui/blob/master/libyui/src/TreeItem.h#L49 > 33 /** > 34 * Template class for tree items that can handle tree children in a > 35 * generic way - firstChild(), next() and parent(). Each item stores one value > 36 * of type 'PAYLOAD'. > 37 * > 38 * Class 'PAYLOAD' needs to provide operator=(). > 39 **/ > 40 template<class PAYLOAD> class TreeItem > 41 { > 42 public: > 43 > 44 /** > 45 * Constructor. Creates a new tree item with value "val" and inserts it > 46 * ( without maintaining any meaningful sort order! ) into the children list > 47 * of "parent". > 48 **/ > 49 TreeItem<PAYLOAD> ( const PAYLOAD & val, > 50 TreeItem<PAYLOAD> * parent = 0 ) > 51 : _value( val ) > 52 , _parent( parent ) > 53 , _next(0) > 54 , _firstChild(0) > 55 { > 56 if ( _parent ) > 57 _parent->addChild( this ); > 58 } > 59 > 60 What on earth is it complaining about now? What did they introduce now to make a developer's life even harder? > TreeItem.h:49:23: note: remove the ‘< >’ ?!???? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1220668] New: kamoso fails to show any UI (on GNOME system)
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1220668 Bug ID: 1220668 Summary: kamoso fails to show any UI (on GNOME system) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting kamoso via the command line I see QQmlApplicationEngine failed to load component qrc:/qml/Main.qml:154:22: Type ImagesView unavailable qrc:/qml/ImagesView.qml:13:1: module "org.kde.purpose" is not installed in the console and then ... nothing, until I stop it via <Ctrl>-<C>. This is kamoso-23.08.4-1.2.x86_64 on current Tumbleweed with a GNOME desktop. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1227345] Kernel 6.9 (MicroOS): a single cpu core is available.
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227345 https://bugzilla.suse.com/show_bug.cgi?id=1227345#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- IIRC, there were relevant bugs in the early 6.9.x kernels, and it's been fixed in the recent 6.9.x release (around 6.9.4). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227346] New: VUL-0: CVE-2019-25211: ollama: parseWildcardRules in Gin-Gonic CORS mishandles a wildcard at the end of an origin string
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227346 Bug ID: 1227346 Summary: VUL-0: CVE-2019-25211: ollama: parseWildcardRules in Gin-Gonic CORS mishandles a wildcard at the end of an origin string Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/412410/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: andrea.mattiazzo(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- parseWildcardRules in Gin-Gonic CORS middleware before 1.6.0 mishandles a wildcard at the end of an origin string, e.g., https://example.community/* is allowed when the intention is that only https://example.com/* should be allowed, and http://localhost.example.com/* is allowed when the intention is that only http://localhost/* should be allowed. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-25211 https://www.cve.org/CVERecord?id=CVE-2019-25211 https://github.com/gin-contrib/cors/commit/27b723a473efd80d5a498fa9f5933c80… https://github.com/gin-contrib/cors/compare/v1.5.0...v1.6.0 https://github.com/gin-contrib/cors/pull/106 https://github.com/gin-contrib/cors/pull/57 https://github.com/gin-contrib/cors/releases/tag/v1.6.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1226426] zypper refresh - GLib-CRITICAL assertion 'str != NULL' failed errors
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226426 https://bugzilla.suse.com/show_bug.cgi?id=1226426#c6 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Michael Andres <ma(a)suse.com> --- closing it -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225697] openSUSE Leap 15.6 i915 driver problems
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225697 https://bugzilla.suse.com/show_bug.cgi?id=1225697#c16 --- Comment #16 from Lo Da <sidewinderx(a)libero.it> --- (In reply to Stefan Dirsch from comment #15) > > OpenGL renderer string: i915 (chipset: G33) > > So i915 driver is available. > > --- > libEGL warning: DRI2: failed to open i915 (search paths /usr/lib64/dri) > libEGL warning: DRI2: failed to open swrast (search paths /usr/lib64/dri) > libEGL warning: DRI2: failed to open i915 (search paths /usr/lib64/dri) > libEGL warning: DRI2: failed to open swrast (search paths /usr/lib64/dri) > Could not initialize GLX > Aborted (core dumped) > --- > > So did you install Mesa-dri package meanwhile are things are just working > now? The Mesa-dri package has always been present and all the problems already described have remained the same. As already said in version 15.4 there are no such problems -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207940] [Build 20230205] openssl-3: tpm unable to enable public key encoding
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1207940 Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|otto.hollmann(a)suse.com |pmonrealgonzalez(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223336] openssl-3: variations in openssl-3-debugsource
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1223336 Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|otto.hollmann(a)suse.com |pmonrealgonzalez(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210313] Conflict resolution between openssl and libressl
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1210313 Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|otto.hollmann(a)suse.com |pmonrealgonzalez(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209053] openssl 3 should fail on certain hash algorithms on FIPS
by bugzilla_noreply＠suse.com 03 Jul '24

03 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1209053 Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|otto.hollmann(a)suse.com |pmonrealgonzalez(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0