June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225526] Tumbleweed KDE install does not include terminus-bitmap fonts or set /etc/vconsole.conf properly on hiDPI systems
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225526 https://bugzilla.suse.com/show_bug.cgi?id=1225526#c9 --- Comment #9 from Franck Bui <fbui(a)suse.com> --- I'm not aware of such runtime support and until it happens it might make sense to init /etc/vconsole.conf so the fonts are at least readable by default after a fresh installation. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225899] New: VUL-0: CVE-2024-4540: python-python-keycloak: exposure of sensitive information in Pushed Authorization Requests (PAR) KC_RESTART cookie
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225899 Bug ID: 1225899 Summary: VUL-0: CVE-2024-4540: python-python-keycloak: exposure of sensitive information in Pushed Authorization Requests (PAR) KC_RESTART cookie Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/408512/ OS: Other Status: NEW Severity: Major 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: abergmann(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- A flaw was found in Keycloak in OAuth 2.0 Pushed Authorization Requests (PAR). Client-provided parameters were found to be included in plain text in the KC_RESTART cookie returned by the authorization server's HTTP response to a `request_uri` authorization request, possibly leading to an information disclosure vulnerability. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-4540 https://bugzilla.redhat.com/show_bug.cgi?id=2279303 https://www.cve.org/CVERecord?id=CVE-2024-4540 https://access.redhat.com/security/cve/CVE-2024-4540 https://access.redhat.com/errata/RHSA-2024:3566 https://access.redhat.com/errata/RHSA-2024:3567 https://access.redhat.com/errata/RHSA-2024:3568 https://access.redhat.com/errata/RHSA-2024:3570 https://access.redhat.com/errata/RHSA-2024:3572 https://access.redhat.com/errata/RHSA-2024:3573 https://access.redhat.com/errata/RHSA-2024:3574 https://access.redhat.com/errata/RHSA-2024:3575 https://access.redhat.com/errata/RHSA-2024:3576 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1224773] NVIDIA KMP: initrd not regenerated on transactional systems using systemd-boot like Aeon >= RC2
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Cannot install NVIDIA |NVIDIA KMP: initrd not |drivers in latest Aeon RC2 |regenerated on | |transactional systems using | |systemd-boot like Aeon >= | |RC2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224386] Please package systemd-resolved seperate from systemd-network
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224386 https://bugzilla.suse.com/show_bug.cgi?id=1224386#c4 --- Comment #4 from Richard Brown <rbrown(a)suse.com> --- (In reply to Franck Bui from comment #3) > (In reply to Richard Brown from comment #2) > > > > Then I'll have to deal with the bug reports > > Noted that you'll be the one who deal with systemd bugs on Aeon ;) I AM the one who deals first with ALL bugs on Aeon. I foolishly thought it was a good idea to make myself the default assignee for every category of that Aeon product. You'll only ever get systemd-on-Aeon bugs from me if it's clearly outside of my realm of fixing..then I hand that over to you - like for example, this bug :) > > and I dont want that, as on Aeon we will only support NetworkManager > > Then it's easy to close such bugs as "not supported". In a Tumbleweed-land where users are expected to mix & match what components are on their system, yes But on Aeon there's an expectation that I ONLY ship stuff that I support. So if I'm shipping stuff that I don't support, that's weird. And I'd rather avoid that..hence..this bug :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224386] Please package systemd-resolved seperate from systemd-network
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224386 https://bugzilla.suse.com/show_bug.cgi?id=1224386#c3 --- Comment #3 from Franck Bui <fbui(a)suse.com> --- (In reply to Richard Brown from comment #2) > > Then I'll have to deal with the bug reports Noted that you'll be the one who deal with systemd bugs on Aeon ;) > and I dont want that, as on Aeon we will only support NetworkManager Then it's easy to close such bugs as "not supported". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225804] New: [leap15.6][build 709.1][aarch64][sporadic] ksplashqml closed upexpectededly with disk image boot
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225804 Bug ID: 1225804 Summary: [leap15.6][build 709.1][aarch64][sporadic] ksplashqml closed upexpectededly with disk image boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: aarch64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: richard.fan(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875260 --> https://bugzilla.suse.com/attachment.cgi?id=875260&action=edit full journal log I can see this issue on aarch64 platform for several times in past week. and it is a sporadic one but I openQA automation job can reproduce this issue stably. Steps to reproduce the issue: 1. Use the latest kde image with build 709.1 to boot the system 2. The error can show up in console. >https://openqa.opensuse.org/tests/4243053#step/boot_to_desktop/44 [please see attached file as well] 3. Full journal log is attached as well. and paste some obviours logs below: >Jun 03 00:41:13.449248 susetest dbus-daemon[1338]: [session uid=1000 pid=1338] Activating service name='org.kde.KSplash' requested by ':1.9' (uid=1000 pid=1429 comm="/usr/bin/ksmserver ") >Jun 03 00:41:13.454078 susetest systemd[1195]: Started KDE Session Management Server. >Jun 03 00:41:13.471200 susetest dbus-daemon[1465]: writing oom_score_adj error: Permission denied >Jun 03 00:41:13.543010 susetest systemd[1195]: Starting KDE Plasma Workspace... >Jun 03 00:41:13.605699 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker" >Jun 03 00:41:13.619849 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate" >Jun 03 00:41:13.620252 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:325:58: unrecognized keysym "XF86CameraAccessEnable" >Jun 03 00:41:13.621923 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:326:58: unrecognized keysym "XF86CameraAccessDisable" >Jun 03 00:41:13.622184 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:327:58: unrecognized keysym "XF86CameraAccessToggle" >Jun 03 00:41:13.622511 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:357:58: unrecognized keysym "XF86NextElement" >Jun 03 00:41:13.622738 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:358:58: unrecognized keysym "XF86PreviousElement" >Jun 03 00:41:13.622958 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:359:58: unrecognized keysym "XF86AutopilotEngageToggle" >Jun 03 00:41:13.623235 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:360:58: unrecognized keysym "XF86MarkWaypoint" >Jun 03 00:41:13.623460 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:361:58: unrecognized keysym "XF86Sos" >Jun 03 00:41:13.623676 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:362:58: unrecognized keysym "XF86NavChart" >Jun 03 00:41:13.623907 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:363:58: unrecognized keysym "XF86FishingChart" >Jun 03 00:41:13.624127 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:364:58: unrecognized keysym "XF86SingleRangeRadar" >Jun 03 00:41:13.624358 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:365:58: unrecognized keysym "XF86DualRangeRadar" >Jun 03 00:41:13.624575 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:366:58: unrecognized keysym "XF86RadarOverlay" >Jun 03 00:41:13.624790 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:367:58: unrecognized keysym "XF86TraditionalSonar" >Jun 03 00:41:13.625006 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:368:58: unrecognized keysym "XF86ClearvuSonar" >Jun 03 00:41:13.625221 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:369:58: unrecognized keysym "XF86SidevuSonar" >Jun 03 00:41:13.625439 susetest kwin_x11[1432]: kwin_xkbcommon: XKB: inet:370:58: unrecognized keysym "XF86NavInfo" >Jun 03 00:41:13.715201 susetest kded5[1431]: org.kde.libkbolt: Failed to connect to Bolt manager DBus interface: >Jun 03 00:41:13.715902 susetest kded5[1431]: org.kde.bolt.kded: Couldn't connect to Bolt DBus daemon -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1225213] no sound on speakers, headphones work
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225213 https://bugzilla.suse.com/show_bug.cgi?id=1225213#c13 --- Comment #13 from Alfredo Cubitos <alfredocubitos(a)yahoo.com.mx> --- It seems to be fixed with Kernel 6.9.3-1-default. I made an update today and it works again :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208369] New "lo" connection
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1208369 https://bugzilla.suse.com/show_bug.cgi?id=1208369#c13 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |fvogt(a)suse.com Status|REOPENED |RESOLVED --- Comment #13 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Cosmin Tanczel from comment #12) > I mean it also shouldn't be viewable in the network manager list. NetworkManager intentionally allows configuration of loopback connections: https://github.com/NetworkManager/NetworkManager/commit/e8618f03d7d8735946a… > Additionally, the IP addresses, DNS, route and routing rules are also allowed to configure for the loopback connection profiles. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224386] Please package systemd-resolved seperate from systemd-network
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224386 https://bugzilla.suse.com/show_bug.cgi?id=1224386#c2 --- Comment #2 from Richard Brown <rbrown(a)suse.com> --- (In reply to Franck Bui from comment #1) > Just out of curiosity, why do you want to avoid it ? > > As long as systemd-networkd remains disabled, it shouldn't cause any > problems. > > Is it only to spare a few Mo on the disk ? Aeon typically doesn't want extra binaries and services lying around on the disk that we're not using There's always a chance my users will turn it on if its there Then I'll have to deal with the bug reports and I dont want that, as on Aeon we will only support NetworkManager -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224386] Please package systemd-resolved seperate from systemd-network
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224386 https://bugzilla.suse.com/show_bug.cgi?id=1224386#c1 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui(a)suse.com --- Comment #1 from Franck Bui <fbui(a)suse.com> --- Just out of curiosity, why do you want to avoid it ? As long as systemd-networkd remains disabled, it shouldn't cause any problems. Is it only to spare a few Mo on the disk ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0