January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213470] timezone-java 2023c contains corrupt data for some timezones
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1213470 https://bugzilla.suse.com/show_bug.cgi?id=1213470#c9 --- Comment #9 from Martin Schreiner <martin.schreiner(a)suse.com> --- I've tested the approach you suggested, Andreas, and as you mentioned, it seems to solve the issue. I'm now looking into how we could use this tool during the build on OBS/IBS, especially the legal implications regarding licensing for Oracle's tzupdater. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219167] New: VUL-0: CVE-2024-0874: coredns: CD bit response is cached and served later
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219167 Bug ID: 1219167 Summary: VUL-0: CVE-2024-0874: coredns: CD bit response is cached and served later Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/392160/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: andrea.manzini(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: gianluca.gabrielli(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Coredns mishandling of CI bit: CD bit response is cached and served later What happened: If CD bit is set in query, it disables validation at remote server What you expected to happen: CD queries may pass, but the same answer must not be served to queries without CD bit set https://github.com/coredns/coredns/issues/6186 References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-0874 https://bugzilla.redhat.com/show_bug.cgi?id=2219234 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219177] New: YaST Edit Printer dialogue misaligned UI element scaling
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219177 Bug ID: 1219177 Summary: YaST Edit Printer dialogue misaligned UI element scaling Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: philipp.reichmuth(a)gmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 872185 --> https://bugzilla.suse.com/attachment.cgi?id=872185&action=edit Edit Printer dialog with lots of whitespace between the listboxes. The Edit Printer window (and related dialogues) in YaST exhibit strange resizing behaviour when the window is resized vertically. The upper and center list boxes resize with a percentage of the overall window, but the scale factors do not add to 100%. As a result, when you resize the window vertically, unused whitespace appears between the listboxes (see screenshots). As a side effect, when you have different printed installed, the listbox with the list of drivers can get quite crowded, because it does not make use of the available space in the window. How to reproduce: 1. Go to YaST (GUI version) → Printers, select a printer, click Edit 2. Resize the edit window vertically. Observed behaviour: The listboxes resize vertically, but less so than the window. Empty space appears between the listboxes and other UI elements. Expected behaviour: The listboxes should resize to fill the available whitespace. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1218948] kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 https://bugzilla.suse.com/show_bug.cgi?id=1218948#c37 --- Comment #37 from Johan Dot <jonte1(a)gmail.com> --- Hi! Sorry for late reply. Added "https://download.opensuse.org/repositories/Kernel:/SLE15-SP5/pool/" yesterday. Works fine to boot the server. Regards -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218979] qt6-creator cannot be installed
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218979 https://bugzilla.suse.com/show_bug.cgi?id=1218979#c7 --- Comment #7 from Olivier Tilloy <olivier.tilloy(a)suse.com> --- Why qt6-creator requires qt6-declarative-tools only when rpm-build is (to be) installed is unclear to me, but the problem itself lies with qt6-declarative-tools's dependencies (namely libQt6JsonRpc.so.6, which is provided by libQt6JsonRpc6). Would you mind filing a separate ticket for that issue (and sharing the link here)? I will take care of adding the missing dependencies. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211571] nmap non-OSI approved "Nmap Public Source License" NPSL
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1211571 https://bugzilla.suse.com/show_bug.cgi?id=1211571#c10 --- Comment #10 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- I changed it to "SUSE-NonFree" https://build.opensuse.org/request/show/1141454 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211571] nmap non-OSI approved "Nmap Public Source License" NPSL
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1211571 https://bugzilla.suse.com/show_bug.cgi?id=1211571#c9 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- CC| |lnussel(a)suse.com --- Comment #9 from Ludwig Nussel <lnussel(a)suse.com> --- THe package fails to build due to unknown license string. I think LicenseRef-NPSL-0.95 needs to be added to SPDX https://github.com/spdx/license-list-XML/pulls https://github.com/spdx/license-list-XML/blob/main/DOCS/license-inclusion-p… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219031] Multiple cross-arm-none-gcc13 bugs
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219031 https://bugzilla.suse.com/show_bug.cgi?id=1219031#c7 --- Comment #7 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1219031) was mentioned in https://build.opensuse.org/request/show/1141444 Factory / gcc13 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218492] New: [Build 20231228] FTBFS: tvm fails to build against not libSPIRV
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218492 Bug ID: 1218492 Summary: [Build 20231228] FTBFS: tvm fails to build against not libSPIRV Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3845146/modules/tvm/ steps/3 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Problem: nothing provides 'libSPIRV-Tools-2023.5~rc1.so()(64bit)' needed by the to be installed python311-tvm-0.13.0-1.2.x86_64 Solution 1: do not install tvmc-0.13.0-1.2.x86_64 Solution 2: break python311-tvm-0.13.0-1.2.x86_64 by ignoring some of its dependencies Source of evil is the build fail of tvm: https://build.opensuse.org/package/live_build_log/openSUSE:Factory/tvm/stan… openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_ai_ml@64bit fails in [tvm](https://openqa.opensuse.org/tests/3845146/modules/tvm/steps/3) ## Test suite description Test AI/ML software ## Reproducible Fails since (at least) Build [20231228](https://openqa.opensuse.org/tests/3842176) ## Expected result Last good: [20231226](https://openqa.opensuse.org/tests/3840037) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218170] New: osc buildhistory error if in a git directory
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218170 Bug ID: 1218170 Summary: osc buildhistory error if in a git directory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: marco.strigl(a)suse.com Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- "osc buildhistory" fails with an error / python backtrace (see below for the full error message) if you run it in a directory that contains a git repo. In my case this git repo was the AppArmor source code. I did not test what happens if you run "osc buildhistory" in a directory that contains the git repo of an OBS package - please test this yourself. osc buildhistory (at least with the 4 parameters syntax) should work without even looking at the current directory. cb@tux:~/apparmor/git master> osc buildhistory -l 5 home:cboltz apparmor openSUSE_Factory x86_64 Traceback (most recent call last): File "/usr/bin/osc", line 33, in <module> sys.exit(load_entry_point('osc==1.5.1', 'console_scripts', 'osc')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/site-packages/osc/babysitter.py", line 226, in main sys.exit(run(commandline.OscMainCommand())) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/site-packages/osc/babysitter.py", line 69, in run prg.main(argv) File "/usr/lib/python3.11/site-packages/osc/commandline.py", line 556, in main cmd.run(args) File "/usr/lib/python3.11/site-packages/osc/commandline.py", line 245, in run cmd.run(args) File "/usr/lib/python3.11/site-packages/osc/commandline.py", line 500, in run self.func(args.command, args, *args.positional_args) File "/usr/lib/python3.11/site-packages/osc/commandline.py", line 7519, in do_buildhistory project, package, repository, arch = pop_project_package_repository_arch_from_args(args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/site-packages/osc/commandline.py", line 817, in pop_project_package_repository_arch_from_args project, package = pop_project_package_from_args( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/site-packages/osc/commandline.py", line 705, in pop_project_package_from_args project = project_store.project ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/site-packages/osc/git_scm/store.py", line 79, in project raise RuntimeError(f"Couldn't map git branch '{branch}' to a project") RuntimeError: Couldn't map git branch 'master' to a project It works if I cd into a non-git directory: cb@tux:~/apparmor/git master> cd ~ cb@tux:~> osc buildhistory -l 5 home:cboltz apparmor openSUSE_Factory x86_64 TIME SRCMD5 VER-REL.BUILD# REV DURATION 2023-10-24 06:58:20 d18117ce59c416e52ba4454396c6e707 3.1.6-966.4 469 447 2023-10-30 03:48:35 d18117ce59c416e52ba4454396c6e707 3.1.6-966.5 469 2041 2023-11-05 22:02:11 d18117ce59c416e52ba4454396c6e707 3.1.6-966.6 469 450 2023-11-07 02:04:55 d18117ce59c416e52ba4454396c6e707 3.1.6-966.7 469 390 2023-11-08 18:28:44 f8aa056a23a410850e7f046bdedbfeee 3.1.6-970.1 471 378 -- You are receiving this mail because: You are on the CC list for the bug.

1 2