December 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1205401] [Build 20221113] Error: Cannot update the dynamic configuration policy - no /sbin/netconfig
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205401 https://bugzilla.suse.com/show_bug.cgi?id=1205401#c18 --- Comment #18 from Dominique Leuenberger <dimstar(a)opensuse.org> --- (In reply to Thomas Schmidt from comment #17) > Do we need to support that architecture? Maybe just exclude suseconnect-ng > from ppc64 builds, because SLES is also not build on that architecture, and > the only reason for having suseconnect on opensuse is the migration to SLES. Works for me, from a TW PoV (please mark it as ExclusiveArch or ExcludeArch in the spec file to have it built on the arches where it makes sense).. This in turn will require yast2-registration to also be disabled on ppc64 or at least not have it require suseconnect; if disabled this continues down to yast2-schema-default, which requires -registration -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205401] [Build 20221113] Error: Cannot update the dynamic configuration policy - no /sbin/netconfig
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205401 https://bugzilla.suse.com/show_bug.cgi?id=1205401#c17 --- Comment #17 from Thomas Schmidt <tschmidt(a)suse.com> --- Do we need to support that architecture? Maybe just exclude suseconnect-ng from ppc64 builds, because SLES is also not build on that architecture, and the only reason for having suseconnect on opensuse is the migration to SLES. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205863] Qt private API issue
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205863 https://bugzilla.suse.com/show_bug.cgi?id=1205863#c4 --- Comment #4 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Michael Dluhosch from comment #3) > I noticed the isse because we use in our application following symbol > "QQuickFramebufferObject::Renderer::framebufferObject const" which causes > the final binary to use the wrongly private tagged symbol > "QQuickFramebufferObject::Renderer::framebufferObject() > const@@Qt_5.15.2_PRIVATE_API" This binary needs now to be recompiled with > every new update to the qt5declarative package. > We currently have SP1 SP3 and SP4 systems, it would be nice if I could > compile on SP1 and just use the binary everywhere. This bug makes it > impossible so I tried to get it fixed so that we can at least use our SP4 > binary when SP5 arrives. Unfortunately the patch would not make that any better for SP5. Qt on SP5 would then provide "QQuickFramebufferObject::Renderer::framebufferObject() const" without symbol version and still not work. This would only improve it for a possible SP6+. Backporting the change to SP4 is also not possible because it breaks ABI. There might be a way to provide both symbols in SP4, but it won't be simple. Currently it's not clear whether SP5 will even get a newer Qt version than SP4, so ATM your build against SP4 will work on SP5 unchanged. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205863] New: Qt private API issue
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205863 Bug ID: 1205863 Summary: Qt private API issue 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: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Received by email today. I'm adding a bug report for discussion: � I write to you because you changed the last revisions here: https://build.opensuse.org/package/revisions/KDE:Qt:5.15/libqt5-qtbase. To fix the issue described here: https://bugreports.qt.io/browse/QTBUG-109030 I would like to create a patch for the libqt5-qtbase package. I have a rough Idea how to use osc and how to create a patch with it. But I have absolutely no Idea to which of the many libqt5-qtbase packages found in build.opensuse.org I should apply this patch to. My goal would be that the patch appears at some point in the future in SLES15-SP4. � -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1205918] [Build 20221130] yast2 security crashes
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205918 https://bugzilla.suse.com/show_bug.cgi?id=1205918#c6 --- Comment #6 from Stefan Hundhammer <shundhammer(a)suse.com> --- We just discussed this in IRC, and it turned out that the test was improved as well, so the problem was there for a long time (since SLE-15 SP4 / Leap 15.4), but undiscovered. So the fix should be released for SLE-15 SP4 / Leap 15.4 as well since it's a crash, and it's security relevant since changes to those LSM settings won't be saved, and there won't be an error about it. No installer self-update is needed, though, since this runs from the YaST control center in the installed system, not during installation. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205918] New: [Build 20221130] yast2 security crashes
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205918 Bug ID: 1205918 Summary: [Build 20221130] yast2 security crashes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2919731/modules/yast 2_security/steps/100 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: openQA Blocker: Yes ## Observation The test opens yast2 security Upon clicking 'login settings', yast crashes away openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_gui@64bit fails in [yast2_security](https://openqa.opensuse.org/tests/2919731/modules/yast2_sec… ## Test suite description Maintainer: qsf-y Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests. Temporarily added YAST2_GUI_TERMINATE_PREVIOUS_INSTANCES to see if helps. This variable triggers code which terminates all yast2 processes before starting new one. (see poo#26104). ## Reproducible Fails since (at least) Build [20221130](https://openqa.opensuse.org/tests/2919011) ## Expected result Last good: [20221129](https://openqa.opensuse.org/tests/2916559) (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 1

[Bug 1205401] [Build 20221113] Error: Cannot update the dynamic configuration policy - no /sbin/netconfig
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205401 https://bugzilla.suse.com/show_bug.cgi?id=1205401#c16 --- Comment #16 from Dominique Leuenberger <dimstar(a)opensuse.org> --- (In reply to Thomas Schmidt from comment #15) > In OBS, suseconnect-ng just succeeded to build on ppc64le: > https://build.opensuse.org/package/live_build_log/systemsmanagement:SCC/ > suseconnect-ng/openSUSE_Factory/ppc64le ppc64 != ppc64le: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:PowerPC/… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205109] New: emacs cannot reach XDG_RUNTIME_DIR
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205109 Bug ID: 1205109 Summary: emacs cannot reach XDG_RUNTIME_DIR Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: All OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: zimtsui(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # Description Emacs checks whether environment variable `XDG_RUNTIME_DIR` exists to determine where a certain socket file should be placed. If `XDG_RUNTIME_DIR` doesn't exist, emacs will fallback to some other location. See <https://git.savannah.gnu.org/cgit/emacs.git/tree/lib-src/emacsclient.c?h=em…> `sudo` defaults to unset all environment variables and set some certain ones. So any program run by `sudo` should miss `XDG_RUNTIME_DIR` in its environment. If I run `sudo emacs-nox`, everything goes expectedly. But if I run `sudo emacs`, emacs prompts `Unable to set up transient service directory: XDG_RUNTIME_DIR "/run/user/0" not available: No such file or directory`. # Possible reason The binary `/usr/bin/emacs` is not built from emacs source, but made by the SUSE package maintainer. The binary checks whether it's run in terminal or X to determine whether it should exec `emacs-nox` or `emacs-x11`. The `/usr/bin/emacs` binary defines an environment variable `XDG_RUNTIME_DIR` as `/run/user/<USER_ID>` arbitrarily. But `/run/user/0` doesn't exist because it should be created by `/etc/profile` in a login shell. And `sudo` doesn't spawn a new login shell. # Reproduction 1. Install `emacs` and `emcas-nox` from zypper, and don't install `emacs-x11`. 1. Restart your computer and don't login as root in any tty, but login as a regular user. 1. `sudo emacs` 1. Quit emacs. 1. You will see the prompt. # Versions openSUSE Leap 15.4 Emacs 27.2 Sudo 1.9.9 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1164084] VUL-0: sendmail: Sendmail upstream security bug report
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1164084 http://bugzilla.opensuse.org/show_bug.cgi?id=1164084#c18 Dr. Werner Fink <werner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #18 from Dr. Werner Fink <werner(a)suse.com> --- This one is fixed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205918] [Build 20221130] yast2 security crashes
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205918 https://bugzilla.suse.com/show_bug.cgi?id=1205918#c5 --- Comment #5 from Stefan Hundhammer <shundhammer(a)suse.com> --- Judging from my manual tests and from the source code, it does write all settings correctly despite the crash - except for the LSM settings: https://github.com/yast/yast-security/blob/master/src/modules/Security.rb#L… I crashes right before write_lsm_config(), so that part won't be written. Is that what this OpenQA tests is testing? Or does it check for error return codes in general? I am confused with all those screenshots in the yast2_system_settings part of https://openqa.opensuse.org/tests/2919011# . -- You are receiving this mail because: You are on the CC list for the bug.

1 0