August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1227418] New: [Build 20240704] openQA test fails in journal_check
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227418 Bug ID: 1227418 Summary: [Build 20240704] openQA test fails in journal_check Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4320773/modules/jour nal_check/steps/21 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: forgotten_u0-bnvADNc(a)user.net Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Every once in a while, I can see things like this in the journal: Jul 05 04:38:43.198898 localhost.localdomain systemd-coredump[3116]: Resource limits disable core dumping for process 3113 (boot-plugin). Jul 05 04:38:43.199870 localhost.localdomain systemd-coredump[3116]: Process 3113 (boot-plugin) of user 0 terminated abnormally without generating a coredump. I'm fully aware that this bug report is missing all relevant information, but the coredump being limited by resources makes it really hard to extract more info from openQA Hopefully you can find similar crashes in some other systems too openQA test in scenario microos-Tumbleweed-MicroOS-Image-x86_64-microos2microosnext@64bit fails in [journal_check](https://openqa.opensuse.org/tests/4320773/modules/journal_ch… ## Test suite description Boot from the latest published MicroOS image and transactional-update dup to snapshot under test. Make sure to use %BUILD% in the URL and file name to force a redownload for new builds. ## Reproducible Fails since (at least) Build [20240704](https://openqa.opensuse.org/tests/4319742) ## Expected result Last good: [20240703](https://openqa.opensuse.org/tests/4317737) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227878] New: econf_readDirs crashes if one of the paths is NULL
by bugzilla_noreply＠suse.com 22 Oct '24

22 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227878 Bug ID: 1227878 Summary: econf_readDirs crashes if one of the paths is NULL Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: schubi(a)suse.com Reporter: sbrabec(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- If util-linux is configured with a plain ./configure, agetty crashes. The reason is simple: If ./configure is called without --with-vendordir=DIR on a system with libeconf, econf_readDirs is called with dist_conf_dir=0x0. And the code does not check for it before calling strdup(). Reading the code, the same is apparently valid for etc_conf_dir. And there are more occurrences of unsanitized strdup() calls on directory names. (gdb) bt #0 __strlen_evex () at ../sysdeps/x86_64/multiarch/strlen-evex-base.S:81 #1 0x00007f06d54aa752 in __GI___strdup (s=s@entry=0x0) at strdup.c:41 #2 0x00007f06d56fa26b in econf_readDirs (comment=0x41260f "#", delim=0x412601 "= \t", config_suffix=0x412605 "defs", config_name=0x412537 "login", etc_conf_dir=0x41260a "/etc", dist_conf_dir=0x0, result=0x41b630 <file>) at ../lib/libeconf.c:510 #3 econf_readDirs (result=result@entry=0x41b630 <file>, dist_conf_dir=dist_conf_dir@entry=0x0, etc_conf_dir=etc_conf_dir@entry=0x41260a "/etc", config_name=config_name@entry=0x412537 "login", config_suffix=config_suffix@entry=0x412605 "defs", delim=delim@entry=0x412601 "= \t", comment=0x41260f "#") at ../lib/libeconf.c:495 #4 0x0000000000409a18 in load_defaults () at lib/logindefs.c:257 #5 0x0000000000409cb5 in getlogindefs_bool (name=name@entry=0x41241a "LOGIN_PLAIN_PROMPT", dflt=dflt@entry=0) at lib/logindefs.c:326 #6 0x0000000000406b11 in main (argc=<optimized out>, argv=<optimized out>) at term-utils/agetty.c:490 (gdb) up #1 0x00007f06d54aa752 in __GI___strdup (s=s@entry=0x0) at strdup.c:41 41 size_t len = strlen (s) + 1; (gdb) up #2 0x00007f06d56fa26b in econf_readDirs (comment=0x41260f "#", delim=0x412601 "= \t", config_suffix=0x412605 "defs", config_name=0x412537 "login", etc_conf_dir=0x41260a "/etc", dist_conf_dir=0x0, result=0x41b630 <file>) at ../lib/libeconf.c:510 510 (*result)->parse_dirs[0] = strdup(dist_conf_dir); (gdb) l 505 return ret; 506 507 (*result)->parse_dirs_count = 2; 508 (*result)->parse_dirs = calloc((*result)->parse_dirs_count+1, sizeof(char *)); 509 (*result)->parse_dirs[(*result)->parse_dirs_count] = NULL; 510 (*result)->parse_dirs[0] = strdup(dist_conf_dir); 511 (*result)->parse_dirs[1] = strdup(etc_conf_dir); 512 513 return readConfigWithCallback(result, 514 config_name, (gdb) p dist_conf_dir $1 = 0x0 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1223436] New: cannot login without password set
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1223436 Bug ID: 1223436 Summary: cannot login without password set Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After updating a Tumbleweed VM without any password set either on the user account, or on root, it has locked me out — i can login neither from SDDM, nor from the kernel console. The previous update of that machine was about a month ago (after the lzma backdoor rebuild). -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1229757] New: Package conflict in libsemanage (shadow) update
by bugzilla_noreply＠suse.com 21 Oct '24

21 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229757 Bug ID: 1229757 Summary: Package conflict in libsemanage (shadow) update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: msvec(a)suse.com QA Contact: qa-bugs(a)suse.de CC: meissner(a)suse.com, mvetter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- This is what I get with the latest MU: + zypper patch --with-optional Problem: 1: the to be installed libsemanage2-3.5-150600.1.48.x86_64 requires 'libsemanage-conf >= 3.5', but this requirement cannot be provided not installable providers: libsemanage-conf-3.5-150600.1.48.x86_64[repo-oss] Solution 1: Following actions will be done: do not install patch:openSUSE-SLE-15.6-2024-2808-1.noarch do not install patch:openSUSE-SLE-15.6-2024-2630-1.noarch Solution 2: deinstallation of libsemanage1-3.1-150400.1.65.x86_64 Solution 3: deinstallation of shadow-4.8.1-150400.8.57.x86_64 Solution 4: break libsemanage2-3.5-150600.1.48.x86_64 by ignoring some of its dependencies -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1217774] New: qt6-webengine qtpdf.index reproducible builds
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1217774 Bug ID: 1217774 Summary: qt6-webengine qtpdf.index reproducible builds Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our qt6-webengine / qt6-webengine-docs-html subpackage varied between builds in /usr/share/doc/qt6/qtpdf/qtpdf.index See diff at https://rb.zq1.de/compare.factory-20230830/diffs/qt6-webengine-compare.out You probably need to build with osc build -M docs -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1229570] New: python3-pygit2 broken due to runtime requirement on unsatisfied cffi version
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229570 Bug ID: 1229570 Summary: python3-pygit2 broken due to runtime requirement on unsatisfied cffi version Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP6 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: ngompa13(a)gmail.com QA Contact: packagehub-bugs(a)suse.com Target Milestone: --- Found By: --- Blocker: --- python3-pygit2 is broken in openSUSE Leap 15.6 because it has an unsatisfied runtime dependency on cffi>=1.16 (Leap only has 1.13.2). I detected this because pagure workers are crashing now on code.opensuse.org ever since pygit2 was upgraded (August 17 according to rpm). The traceback looks like this: Aug 21 11:28:42 pagure01 celery[5426]: Traceback (most recent call last): Aug 21 11:28:42 pagure01 celery[5426]: File "/usr/lib/python3.6/site-packages/celery/app/trace.py", line 412, in trace_task Aug 21 11:28:42 pagure01 celery[5426]: R = retval = fun(*args, **kwargs) Aug 21 11:28:42 pagure01 celery[5426]: File "/usr/lib/python3.6/site-packages/celery/app/trace.py", line 704, in __protected_call__ Aug 21 11:28:42 pagure01 celery[5426]: return self.run(*args, **kwargs) Aug 21 11:28:42 pagure01 celery[5426]: File "/usr/lib/python3.6/site-packages/pagure/lib/tasks_utils.py", line 36, in decorated_function Aug 21 11:28:42 pagure01 celery[5426]: return function(self, session, *args, **kwargs) Aug 21 11:28:42 pagure01 celery[5426]: File "/usr/lib/python3.6/site-packages/pagure/lib/tasks.py", line 117, in generate_gitolite_acls Aug 21 11:28:42 pagure01 celery[5426]: helper = pagure.lib.git_auth.get_git_auth_helper() Aug 21 11:28:42 pagure01 celery[5426]: File "/usr/lib/python3.6/site-packages/pagure/lib/git_auth.py", line 80, in get_git_auth_helper Aug 21 11:28:42 pagure01 celery[5426]: cls = classes[backend].load() Aug 21 11:28:42 pagure01 celery[5426]: File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2442, in load Aug 21 11:28:42 pagure01 celery[5426]: self.require(*args, **kwargs) Aug 21 11:28:42 pagure01 celery[5426]: File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2465, in require Aug 21 11:28:42 pagure01 celery[5426]: items = working_set.resolve(reqs, env, installer, extras=self.extras) Aug 21 11:28:42 pagure01 celery[5426]: File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 791, in resolve Aug 21 11:28:42 pagure01 celery[5426]: raise VersionConflict(dist, req).with_context(dependent_req) Aug 21 11:28:42 pagure01 celery[5426]: pkg_resources.ContextualVersionConflict: (cffi 1.13.2 (/usr/lib64/python3.6/site-packages), Requirement.parse('cffi>=1.16.0'), {'pygit2'}) This breakage is the result of this commit in pygit2 (part of 1.14.0 release): https://github.com/libgit2/pygit2/commit/aab211a842b17c8b699b2753301abb3a9b… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227174] New: VUL-0: CVE-2024-39705: python-nltk: remote code execution through the integrated data package download functionality
by bugzilla_noreply＠suse.com 18 Oct '24

18 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227174 Bug ID: 1227174 Summary: VUL-0: CVE-2024-39705: python-nltk: remote code execution through the integrated data package download functionality Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/412359/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: python-maintainers(a)suse.com 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: --- NLTK through 3.8.1 allows remote code execution if untrusted packages have pickled Python code, and the integrated data package download functionality is used. This affects, for example, averaged_perceptron_tagger and punkt. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-39705 https://www.cve.org/CVERecord?id=CVE-2024-39705 https://github.com/nltk/nltk/issues/2522 https://github.com/nltk/nltk/issues/3266 https://bugzilla.redhat.com/show_bug.cgi?id=2294671 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1227311] New: Upgrade of mariadb from 11.2.3 to 11.4.2 will fail if ssl can't be verified.
by bugzilla_noreply＠suse.com 18 Oct '24

18 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227311 Bug ID: 1227311 Summary: Upgrade of mariadb from 11.2.3 to 11.4.2 will fail if ssl can't be verified. Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: silentworks(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The recent release of mariadb-11.4.2 creates a quite annoying issue, the installation script will create /var/lib/misc/.mariadb_run_upgrade, since a mysql_upgrade should be done with the version change. The next time systemd tries to start mariadb /usr/libexec/mysql/mysql-systemd-helper sees that .mariadb_run_upgrade exists, and that enables the upgrade flag. Here comes the problem, since mariadb 11.3 the upgrade function has ssl verification enabled by default. So if the mariadb server has any self-signed cert, any custom cert, or the hostname doesn't match, the verification will fail. And hence the upgrade and the script will fail. mysql_upgrade will refuse the connection, and the script isn't designed to handle this. --disable-ssl-verify-server-cert should be passed by default in the script In line 119: "if /usr/bin/mysql_upgrade --disable-ssl-verify-server-cert" And i don't know if the mysqladmin behaves in he same way (didn't check). I think in some situations the .mariadb_run_upgrade may not be deleted too, even if the upgrade finished, that could cause a loop that will cause the upgrade script to run everytime mariadb is started from systemd, which is what happened to me and i had to delete the .mariadb_run_upgrade manually, but i'm not sure why. (i did the upgrade manually afterwards) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1229999] New: High idle power usage on Lenovo Slim 7 16" AMD
by bugzilla_noreply＠suse.com 17 Oct '24

17 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229999 Bug ID: 1229999 Summary: High idle power usage on Lenovo Slim 7 16" AMD 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: variable_valuables761(a)simplelogin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Tumbleweed seems to have unusually high power consumption when idle. I tested on KDE (Krypton live usb) with nothing open except Konsole running powertop, and compared with Fedora Rawhide live usb. My machine is a Lenovo Slim 7 16" AMD (16ARH7, 82UX0001US). Outputs from powertop attached (Overview & Device stats): ~25W on Krypton vs ~14W on Rawhide How should we diagnose what the issue could be? (Note the ongoing issue with Pipewire/libcamera webcam power usage has just been fixed in libcamera, which has not been released yet. Disabling the webcam as a workaround only drops power usage by a few watts on my system.) -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1221890] New: Audacious crashes when opening file dialog since Plasma 6
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1221890 Bug ID: 1221890 Summary: Audacious crashes when opening file dialog since Plasma 6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: foss(a)grueninger.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After I installed Plasma and KF 6, the media player crashes when opening the file dialog (to open or append tracks). Steps to reproduce: 1. Open Audacious 2. Press Ctrl + o to open a audio file. 3. Dialog flashes and Audacious is terminated It seems to be a packaging issue, upstream has no idea. See the according issue: https://github.com/orgs/audacious-media-player/discussions/122 -- You are receiving this mail because: You are on the CC list for the bug.

1 4