April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1221510] New: plasma6-systemmonitor appearance issues of grid view
by bugzilla_noreply＠suse.com 15 May '24

15 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221510 Bug ID: 1221510 Summary: plasma6-systemmonitor appearance issues of grid view Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: R_Nik_C(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Sorry, it would be better if I just show pictures. * And another bug... in edit page mode, "discard changes" crush application. (1) This is Plasma 6 https://paste.opensuse.org/pastes/55c2f98a1ec6 (2) This is Plasma 5 https://paste.opensuse.org/pastes/b4809957569c It should be obvious now what I mean (grid view issues). -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217750] New: Nonfunctional brightness keys on Lenovo Slim 7 16" AMD
by bugzilla_noreply＠suse.com 15 May '24

15 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217750 Bug ID: 1217750 Summary: Nonfunctional brightness keys on Lenovo Slim 7 16" AMD Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: variable_valuables761(a)simplelogin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871117 --> https://bugzilla.suse.com/attachment.cgi?id=871117&action=edit Output of "brightnessctl -l" for Lenovo 16ARH7 It seems the brightness keys (Fn+F5,Fn+F6) do not work in the latest Tumbleweed KDE snapshot on the Lenovo Slim 7 16" AMD, 16ARH7, 82UX0001US (and this same model is called Yoga outside the United States). It seems the internal display's brightness values are bugged and show up as 0 and "0 (-2147483648%)" in brightnessctl rather than something within the expected range. I've attached the output of "brightnessctl -l", which shows the display and some of the keyboard/charging LEDs on the laptop. Glad to provide any other logs that could be helpful. Hope this is the right place to report this. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1217840] New: rpmlint does not check anymore for packages built without distro %{optflags}
by bugzilla_noreply＠suse.com 15 May '24

15 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217840 Bug ID: 1217840 Summary: rpmlint does not check anymore for packages built without distro %{optflags} Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: dimstar(a)opensuse.org, dmueller(a)suse.com, fvogt(a)suse.com Target Milestone: --- Found By: --- Blocker: --- At some point, rpmlint checked for packages built without distro %{optflags}. This is not the case anymore. It was added upstream in https://github.com/rpm-software-management/rpmlint/issues/341 So, this should be a matter of setting MandatoryOptflags to the right settings? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221250] New: glibc-locale-base missing locale() provides
by bugzilla_noreply＠suse.com 15 May '24

15 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221250 Bug ID: 1221250 Summary: glibc-locale-base missing locale() provides Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, the glibc-locale package ships with "Provide"s for the different locales it ships: ``` $ rpm -q --provides glibc-locale|head glibc-locale = 2.38-6.1 glibc-locale(x86-64) = 2.38-6.1 locale(glibc:aa_DJ) locale(glibc:aa_DJ.utf8) locale(glibc:aa_ER) locale(glibc:aa_ER@saaho) locale(glibc:aa_ET) locale(glibc:af_ZA) locale(glibc:af_ZA.utf8) locale(glibc:agr_PE) ``` There are two locales which are shipped in glibc-locale-base - en_US.utf8 and C.utf8. Upon packaging something which requires one of them, I noticed that glibc-locale-base is not shipping any `locale()` "Provide"s. ``` $ rpm -q --provides glibc-locale-base glibc-locale-base = 2.38-6.1 glibc-locale-base(x86-64) = 2.38-6.1 libCNS.so()(64bit) libGB.so()(64bit) libISOIR165.so()(64bit) libJIS.so()(64bit) libJISX0213.so()(64bit) libKSC.so()(64bit) ``` I would expect glibc-locale-base to Provide `locale(glibc:C.utf8)` and `locale(glibc:en_US.utf8)` - both to have providers for all locales in the distribution and to make packaging easier. Unfortunately I could not figure out how the "Provide"s in glibc.spec are generated myself, hence I am opening this report instead. Cheers, Georg -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1223086] New: consider integrity checking in source services mandatory
by bugzilla_noreply＠suse.com 15 May '24

15 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223086 Bug ID: 1223086 Summary: consider integrity checking in source services mandatory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: jzerebecki(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Not sure if this is the right component/product... I have previously asked this similarly via mail, so trying here to not let it drop off the table again: Can we agree to consider the following as security bugs?: In scope: Any source services available in Factory, when no explicit argument like "insecure" is enabled (so a program can find and count them, an exhaustive list of those exception labels will be later defined in source_validator). If a bug is found that makes the output not reproducible or verification of downloads is not cryptographically secure, it is categorised as a security bug to be fixed. Out of scope, for now: How those services are used in packages. For larger context see: https://github.com/openSUSE/obs-service-source_validator/issues/134 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219943] New: Certificate error while fetching from https://debuginfod.opensuse.org
by bugzilla_noreply＠suse.com 15 May '24

15 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219943 Bug ID: 1219943 Summary: Certificate error while fetching from https://debuginfod.opensuse.org Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: jimis(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Certificate error while fetching from https://debuginfod.opensuse.org Sorry about setting the component to "other" but I couldn't find a suitable one, I was searching for something like "infrastructure" or "administration". -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1223504] New: transactional_update cannot deal with new table look of snapper
by bugzilla_noreply＠suse.com 15 May '24

15 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223504 Bug ID: 1223504 Summary: transactional_update cannot deal with new table look of snapper Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: aschnell(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- See https://build.opensuse.org/request/show/1169010. snapper uses unicode symbols for the table lines now. The code in transactional_update cannot deal with that: https://github.com/openSUSE/transactional-update/blob/master/sbin/transacti… transactional_update should use the CSV or JSON output of snapper instead. CSV is partly used already: https://github.com/openSUSE/transactional-update/blob/master/systemd/prepar… -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1218579] New: cargo_vendor serice fail
by bugzilla_noreply＠suse.com 15 May '24

15 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1218579 Bug ID: 1218579 Summary: cargo_vendor serice fail Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: All Status: NEW Severity: Major Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: werwolf131313(a)gmail.com QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 871679 --> https://bugzilla.suse.com/attachment.cgi?id=871679&action=edit local cargo_vendor cargo_vendor work in local `osc service ra`, but failed in OBS. error: > Files could not be expanded: service error: 400 remote error: cargo_vendor service parameter "srctar" is not defined (http://obs-gateway:5153/sourceupdate/home:Werwolf2517/Alfis?timeout=7200) less info > service daemon error: > 400 remote error: cargo_vendor service parameter "srctar" is not defined (http://obs-gateway:5153/sourceupdate/home:Werwolf2517/Alfis?timeout=7200) i try src, srctar, srcdir. in my local machine all works, but in OBS always i get this error For a long time I thought I was doing something wrong, but now I'm sure it's not me. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1223400] New: VUL-0: CVE-2024-22391: gdcm: heap-based buffer overflow in the LookupTable:SetLUT functionality
by bugzilla_noreply＠suse.com 14 May '24

14 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223400 Bug ID: 1223400 Summary: VUL-0: CVE-2024-22391: gdcm: heap-based buffer overflow in the LookupTable:SetLUT functionality Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/403163/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: axel.braun(a)gmx.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- A heap-based buffer overflow vulnerability exists in the LookupTable::SetLUT functionality of Mathieu Malaterre Grassroot DICOM 3.0.23. A specially crafted malformed file can lead to memory corruption. An attacker can provide a malicious file to trigger this vulnerability. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-22391 https://www.cve.org/CVERecord?id=CVE-2024-22391 https://talosintelligence.com/vulnerability_reports/TALOS-2024-1924 https://www.talosintelligence.com/vulnerability_reports/TALOS-2024-1924 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223401] New: VUL-0: CVE-2024-25569: gdcm: out-of-bounds read in the RAWCodec:DecodeBytes functionality
by bugzilla_noreply＠suse.com 14 May '24

14 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223401 Bug ID: 1223401 Summary: VUL-0: CVE-2024-25569: gdcm: out-of-bounds read in the RAWCodec:DecodeBytes functionality Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/403164/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: axel.braun(a)gmx.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- An out-of-bounds read vulnerability exists in the RAWCodec::DecodeBytes functionality of Mathieu Malaterre Grassroot DICOM 3.0.23. A specially crafted DICOM file can lead to an out-of-bounds read. An attacker can provide a malicious file to trigger this vulnerability. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25569 https://www.cve.org/CVERecord?id=CVE-2024-25569 https://talosintelligence.com/vulnerability_reports/TALOS-2024-1944 https://www.talosintelligence.com/vulnerability_reports/TALOS-2024-1944 -- You are receiving this mail because: You are on the CC list for the bug.

1 2