--17345096755.F02d.11
Date: Wed, 18 Dec 2024 08:14:35 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1234681

            Bug ID: 1234681
           Summary: python-urllib3:test FTBFS in Tumbleweedl
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Python
          Assignee: python-maintainers-at-suse.com
          Reporter: ana.guerrero-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

python-urllib3:test has been failing since 12 or 13 December. This is a rin=
g1
package so while it's broken, it might block other updates.

The failures are:

[   34s] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D short test summary info
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_https_proxy
- assert 500 =3D=3D 200
[   34s]  +  where 500 =3D <urllib3.response.HTTPResponse object at
0x7f8fd2e6a770>.status
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_https_proxy_with_proxy_ssl_context
- assert 500 =3D=3D 200
[   34s]  +  where 500 =3D <urllib3.response.HTTPResponse object at
0x7f8fd838fbb0>.status
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_https_proxy_pyopenssl_not_supported
- assert 500 =3D=3D 200
[   34s]  +  where 500 =3D <urllib3.response.HTTPResponse object at
0x7f8fd83d6cb0>.status
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_https_proxy_forwarding_for_https
- assert 500 =3D=3D 200
[   34s]  +  where 500 =3D <urllib3.response.HTTPResponse object at
0x7f8fd8654a30>.status
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_https_headers_forwarding_for_https
- json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_https_headers
- json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_is_verified_https_proxy_to_http_target
- assert 500 =3D=3D 200
[   34s]  +  where 500 =3D <urllib3.response.HTTPResponse object at
0x7fb34b776320>.status
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_http_and_https_kwarg_ca_cert_data_proxy
- assert 500 =3D=3D 200
[   34s]  +  where 500 =3D <urllib3.response.HTTPResponse object at
0x7fb34bb60910>.status
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPSProxyVerification=
::test_https_proxy_ipv4_san
- urllib3.exceptions.ProxySchemeUnsupported: TLS in TLS requires
SSLContext.wrap_bio() which isn't available on non-native SSLContext
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPSProxyVerification=
::test_https_proxy_ipv6_san
- urllib3.exceptions.ProxySchemeUnsupported: TLS in TLS requires
SSLContext.wrap_bio() which isn't available on non-native SSLContext
[   34s] =3D=3D=3D=3D 10 failed, 1667 passed, 320 skipped, 4 xfailed, 114 w=
arnings in
22.40s =3D=3D=3D=3D

See full log at:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Rings:1-=
MinimalX/python-urllib3:test/standard/x86_64
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17345096755.F02d.11
Date: Wed, 18 Dec 2024 08:14:35 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1234681

          Summary
          python-urllib3:test FTBFS in Tumbleweedl

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Python

          Assignee
          python-maintainers@suse.com

          Reporter
          ana.guerrero@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

python-urllib3:test has been failing since 12 or 13 December=
. This is a ring1
package so while it's broken, it might block other updates.

The failures are:

[   34s] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D short test summary info
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_https_proxy
- assert 500 =3D=3D 200
[   34s]  +  where 500 =3D <urllib3.response.HTTPResponse object at
0x7f8fd2e6a770>.status
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_https_proxy_with_proxy_ssl_context
- assert 500 =3D=3D 200
[   34s]  +  where 500 =3D <urllib3.response.HTTPResponse object at
0x7f8fd838fbb0>.status
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_https_proxy_pyopenssl_not_supported
- assert 500 =3D=3D 200
[   34s]  +  where 500 =3D <urllib3.response.HTTPResponse object at
0x7f8fd83d6cb0>.status
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_https_proxy_forwarding_for_https
- assert 500 =3D=3D 200
[   34s]  +  where 500 =3D <urllib3.response.HTTPResponse object at
0x7f8fd8654a30>.status
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_https_headers_forwarding_for_https
- json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_https_headers
- json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_is_verified_https_proxy_to_http_target
- assert 500 =3D=3D 200
[   34s]  +  where 500 =3D <urllib3.response.HTTPResponse object at
0x7fb34b776320>.status
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPProxyManager::test=
_http_and_https_kwarg_ca_cert_data_proxy
- assert 500 =3D=3D 200
[   34s]  +  where 500 =3D <urllib3.response.HTTPResponse object at
0x7fb34bb60910>.status
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPSProxyVerification=
::test_https_proxy_ipv4_san
- urllib3.exceptions.ProxySchemeUnsupported: TLS in TLS requires
SSLContext.wrap_bio() which isn't available on non-native SSLContext
[   34s] FAILED
test/with_dummyserver/test_proxy_poolmanager.py::TestHTTPSProxyVerification=
::test_https_proxy_ipv6_san
- urllib3.exceptions.ProxySchemeUnsupported: TLS in TLS requires
SSLContext.wrap_bio() which isn't available on non-native SSLContext
[   34s] =3D=3D=3D=3D 10 failed, 1667 passed, 320 skipped, 4 xfailed, 114 w=
arnings in
22.40s =3D=3D=3D=3D

See full log at:
https://build.open=
suse.org/package/live_build_log/openSUSE:Factory:Rings:1-MinimalX/python-ur=
llib3:test/standard/x86_64

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17345096755.F02d.11--


--17345202850.d8f8Eb.377
Date: Wed, 18 Dec 2024 11:11:25 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1234688

            Bug ID: 1234688
           Summary: VUL-0: CVE-2024-54662: dante: incorrect access control for some sockd.conf configurations
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/433220/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: abergmann-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

Dante 1.4.0 through 1.4.3 (fixed in 1.4.4) has incorrect access control for
some sockd.conf configurations involving socksmethod.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-54662
https://www.cve.org/CVERecord?id=3DCVE-2024-54662
https://www.inet.no/dante/
https://www.inet.no/dante/advisory-2024-12-16.txt
https://bugzilla.redhat.com/show_bug.cgi?id=3D2332886
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17345202850.d8f8Eb.377
Date: Wed, 18 Dec 2024 11:11:25 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1234688

          Summary
          VUL-0: CVE-2024-54662: dante: incorrect access control for so=
me sockd.conf configurations

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          URL
          https://smash.suse.de/issue/433220/

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          abergmann@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

Dante 1.4.0 through 1.4.3 (fixed in 1.4.4) has incorrect acc=
ess control for
some sockd.conf configurations involving socksmethod.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-54662
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-54662
https://www.inet.no/dante/
https://www.i=
net.no/dante/advisory-2024-12-16.txt
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2332886

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17345202850.d8f8Eb.377--


--17345336881.853c6b3.249
Date: Wed, 18 Dec 2024 14:54:48 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1234692

            Bug ID: 1234692
           Summary: Moval of dbus-launch to dbus-daemon prevents start of Dolphin super user mode
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: sturm-fr-at-web.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Since moval of dbus-launch to the subpackage dbus-daemon (dbus-1-daemon),
applications which need dbus-launch won't start anymore.
Related change:
https://build.opensuse.org/projects/Base:System/packages/dbus-1/files/dbus-=
1.changes?expand=3D1

dbus-1-daemon is not part of any pattern and does not get installed by defa=
ult
when you install Tumbleweed from any actual sbnapshot ISO (broken since at
least snapshot 20241208).

As example in KDE Plasma 6, Doplphin super user mode (application starter)
fails to open as it calls following command:
dbus-launch dolphin -qwindowtitle %c %u
See
https://build.opensuse.org/projects/openSUSE:Factory/packages/dolphin/files=
/dolphinsu.desktop?expand=3D1

There are already several reports in the forum regarding this topic. Either
make dbus-1-daemon a part of a base pattern or adapt the Dolphin-super use =
mode
starter to work in other ways.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17345336881.853c6b3.249
Date: Wed, 18 Dec 2024 14:54:48 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1234692

          Summary
          Moval of dbus-launch to dbus-daemon prevents start of Dolphin=
 super user mode

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          sturm-fr@web.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Since moval of dbus-launch to the subpackage dbus-daemon (db=
us-1-daemon),
applications which need dbus-launch won't start anymore.
Related change:
https://build.opensuse.org/projects/Base:S=
ystem/packages/dbus-1/files/dbus-1.changes?expand=3D1

dbus-1-daemon is not part of any pattern and does not get installed by defa=
ult
when you install Tumbleweed from any actual sbnapshot ISO (broken since at
least snapshot 20241208).

As example in KDE Plasma 6, Doplphin super user mode (application starter)
fails to open as it calls following command:
dbus-launch dolphin -qwindowtitle %c %u
See
https://build.opensuse.org/projec=
ts/openSUSE:Factory/packages/dolphin/files/dolphinsu.desktop?expand=3D1

There are already several reports in the forum regarding this topic. Either
make dbus-1-daemon a part of a base pattern or adapt the Dolphin-super use =
mode
starter to work in other ways.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17345336881.853c6b3.249--


--17346968541.bBD6Dfa.140
Date: Fri, 20 Dec 2024 12:14:14 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1234754

            Bug ID: 1234754
           Summary: [Build 20241219] tuned conflicting power-profiles-daemin
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/4720354/modules/zdup
                    /steps/12
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

## Observation

This is basically the same as
https://bugzilla.opensuse.org/show_bug.cgi?id=3D1224202

tuned still has the conflicts on power-profiles-daemon - every user of any
desktop environment has tuned and ppd installed on their system. This confl=
ict
means every user now has to understand what that means and chose one or the
other (and if they run a desktop and pick tuned, much bad will come from it)

* tuned is recommended by the base pattern (i.e on all systems)
* power-profiles-daemon is recommended by gnome-control-cener and powerveil
(i.e the GUI parts interacting with ppd)

in a default install, tuned is installed, but services disabled. GNOME and =
KDE
interact on dbus with ppd, which means in most cases that service will be
running.

Having the packages conflict on installation seems just exaggerated (and ca=
uses
probably way more harm than good for upgraders)

openQA test in scenario
opensuse-Tumbleweed-NET-x86_64-zdup-Leap-15.6-gnome@64bit fails in
[zdup](https://openqa.opensuse.org/tests/4720354/modules/zdup/steps/12)

## Test suite description
Maintained by qe-core

## Reproducible

Fails since (at least) Build
[20241219](https://openqa.opensuse.org/tests/4720354) (current job)

## Expected result

Last good: [20241218](https://openqa.opensuse.org/tests/4713428) (or more
recent)

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=3Dx86_64&distri=3Dop=
ensuse&flavor=3DNET&machine=3D64bit&test=3Dzdup-Leap-15.6-gnome&version=3DT=
umbleweed)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17346968541.bBD6Dfa.140
Date: Fri, 20 Dec 2024 12:14:14 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1234754

          Summary
          [Build 20241219] tuned conflicting power-profiles-daemin

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          URL
          https://openqa.opensuse.org/tests/4720354/modules/zdup/steps/=
12

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          dimstar@opensuse.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

## Observation

This is basically the same as
https:/=
/bugzilla.opensuse.org/show_bug.cgi?id=3D1224202

tuned still has the conflicts on power-profiles-daemon - every user of any
desktop environment has tuned and ppd installed on their system. This confl=
ict
means every user now has to understand what that means and chose one or the
other (and if they run a desktop and pick tuned, much bad will come from it)

* tuned is recommended by the base pattern (i.e on all systems)
* power-profiles-daemon is recommended by gnome-control-cener and powerveil
(i.e the GUI parts interacting with ppd)

in a default install, tuned is installed, but services disabled. GNOME and =
KDE
interact on dbus with ppd, which means in most cases that service will be
running.

Having the packages conflict on installation seems just exaggerated (and ca=
uses
probably way more harm than good for upgraders)

openQA test in scenario
opensuse-Tumbleweed-NET-x86_64-zdup-Leap-15.6-gnome@64bit fails in
[zdup](https://openqa.opensuse.org/tests/4720354/modules/zdup/steps/12)

## Test suite description
Maintained by qe-core

## Reproducible

Fails since (at least) Build
[20241219](https://op=
enqa.opensuse.org/tests/4720354) (current job)

## Expected result

Last good: [20241218](https://openqa.opensuse.org/tests/4713428) (or more
recent)

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests=
/latest?arch=3Dx86_64&distri=3Dopensuse&flavor=3DNET&machine=3D=
64bit&test=3Dzdup-Leap-15.6-gnome&version=3DTumbleweed)

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17346968541.bBD6Dfa.140--


--17347163420.fa7b.92
Date: Fri, 20 Dec 2024 17:39:02 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1234765

            Bug ID: 1234765
           Summary: systemd-network recommends development package
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: systemd-maintainers-at-suse.de
          Reporter: arvidjaar-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Normally no run-time package should depend on a development package.

tw:/run/systemd/network # zypper in systemd-network
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following recommended package was automatically selected:
  libidn2-devel

The following 2 NEW packages are going to be installed:
  libidn2-devel systemd-network
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17347163420.fa7b.92
Date: Fri, 20 Dec 2024 17:39:02 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1234765

          Summary
          systemd-network recommends development package

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          systemd-maintainers@suse.de

          Reporter
          arvidjaar@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Normally no run-time package should depend on a development =
package.

tw:/run/systemd/network # zypper in systemd-network
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following recommended package was automatically selected:
  libidn2-devel

The following 2 NEW packages are going to be installed:
  libidn2-devel systemd-network

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17347163420.fa7b.92--


--17348796332.BBBcEE.35
Date: Sun, 22 Dec 2024 15:00:33 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1234782

            Bug ID: 1234782
           Summary: Kernel 6.12.6 with amdgpu breaks brightness control after resume
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: fkrueger-at-mailbox.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Given TW20241220 with kernel 6.12.6 and resuming after suspend, the display
brightness starts to increase until reaching its maximum value, and then
switches off (Thinkpad T14 with AMD Ryzen 7 PRO 4750U). Since kernel version
6.12.4 works fine, I suspect that this was introduced with 6.12.5 and is du=
e to=20

commit 99a02eab82515343d536796aa917dee50aec1551
Author: Alex Deucher <alexander.deucher-at-amd.com>
Date:   Mon Nov 25 13:59:09 2024 -0500

    drm/amdgpu: rework resume handling for display (v2)

    commit 73dae652dcac776296890da215ee7dec357a1032 upstream.

    Split resume into a 3rd step to handle displays when DCC is
    enabled on DCN 4.0.1.  Move display after the buffer funcs
    have been re-enabled so that the GPU will do the move and
    properly set the DCC metadata for DCN.

    v2: fix fence irq resume ordering
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17348796332.BBBcEE.35
Date: Sun, 22 Dec 2024 15:00:33 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1234782

          Summary
          Kernel 6.12.6 with amdgpu breaks brightness control after res=
ume

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          fkrueger@mailbox.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Given TW20241220 with kernel 6.12.6 and resuming after suspe=
nd, the display
brightness starts to increase until reaching its maximum value, and then
switches off (Thinkpad T14 with AMD Ryzen 7 PRO 4750U). Since kernel version
6.12.4 works fine, I suspect that this was introduced with 6.12.5 and is du=
e to=20

commit 99a02eab82515343d536796aa917dee50aec1551
Author: Alex Deucher <a=
lexander.deucher@amd.com>
Date:   Mon Nov 25 13:59:09 2024 -0500

    drm/amdgpu: rework resume handling for display (v2)

    commit 73dae652dcac776296890da215ee7dec357a1032 upstream.

    Split resume into a 3rd step to handle displays when DCC is
    enabled on DCN 4.0.1.  Move display after the buffer funcs
    have been re-enabled so that the GPU will do the move and
    properly set the DCC metadata for DCN.

    v2: fix fence irq resume ordering

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17348796332.BBBcEE.35--


--17353068390.d326a6.50
Date: Fri, 27 Dec 2024 13:40:39 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1234858

            Bug ID: 1234858
           Summary: Intel hybrid driver "hybrid_drv_video.so" for VA API (VAAPI) does not work
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 3rd Party Driver
          Assignee: gfx-bugs-at-suse.de
          Reporter: kaykaykay123-at-gmail.com
        QA Contact: sndirsch-at-suse.com
  Target Milestone: ---
          Found By: Community User
           Blocker: ---

Intel hybrid driver "hybrid_drv_video.so" for VA API (VAAPI) does not work.=
=20
It provides VP9 decoding for Intel GPUs from Haswell (maybe Ivy Bridge) till
Skylake by using CPU together with GPU shaders.=20

Package intel-hybrid-driver installs "hybrid_drv_video.so", requires package
libcmrt1 to work.
Link to package: https://software.opensuse.org/package/intel-hybrid-driver
Intel-hybrid-driver is available for Leap - backported from SLE (bp156, bp1=
55
prefixes).

OpenSUSE uses 2 from 5 available patches.
Possibly patch "U_Update-the-dependency-to-libva-2.0.patch" is not needed a=
ny
more.
https://build.opensuse.org/projects/X11:XOrg/packages/intel-hybrid-driver/f=
iles/U_Update-the-dependency-to-libva-2.0.patch?expand=3D1

Intel hybrid driver versions:
https://repology.org/project/intel-hybrid-driver/versions

Intel hybrid driver patches from Gentoo:
https://gitweb.gentoo.org/repo/gentoo.git/tree/media-libs/intel-hybrid-code=
c-driver/files

After applying all 5 patches driver can be versioned as 2.0.0.

To test intel-hybrid-driver you need to explicitly require it by using
environment variable:
"LIBVA_DRIVER_NAME=3Dhybrid":

Now it is

:~> LIBVA_DRIVER_NAME=3Dhybrid vainfo
libva info: VA-API version 1.16.0
libva info: User environment variable requested driver 'hybrid'
libva info: Trying to open /usr/lib64/dri/hybrid_drv_video.so
libva error: /usr/lib64/dri/hybrid_drv_video.so has no function
__vaDriverInit_1_0
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

Output for working driver radeonsi_drv_video.so:

:~> vainfo
libva info: VA-API version 1.16.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_16
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.16 (libva 2.15.0)
vainfo: Driver version: Mesa Gallium driver 22.3.5 for AMD Radeon Graphics
(raven, LLVM 15.0.7, DRM 3.49, 5.14.21-150500.55.88-default)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointEncSlice
      VAProfileHEVCMain10             : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile2            : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc

Output for working hybrid_drv_video.so on some old system:

timo@Zeo ~ % export LIBVA_DRIVER_NAME=3Dhybrid
timo@Zeo ~ % vainfo
libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 0
libva info: User requested driver 'hybrid'
libva info: Trying to open /usr/lib64/va/drivers/hybrid_drv_video.so
libva info: Found init function __vaDriverInit_0_34
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.38 (libva 1.6.1.pre1)
vainfo: Driver version: Intel hybrid driver - 1.0.1.pre1
vainfo: Supported profile and entrypoints
      VAProfileVP8Version0_3          : VAEntrypointEncSlice
      VAProfileVP9Profile0            : VAEntrypointVLD

Exploring error "libva error: /usr/lib64/dri/hybrid_drv_video.so has no
function __vaDriverInit_1_0" ->

Finding vaDriverInit in intel-hybrid-driver driver:

:~> /usr/bin/nm --demangle -D
/home/mypc/Temp/intel-hybrid-driver-1.0.2-bp156.4.4.x86_64/usr/lib64/dri/hy=
brid_drv_video.so
| grep vaDriverInit
000000000001c530 T __vaDriverInit_0_34

Finding vaDriverInit in radeonsi_drv_video.so driver from Mesa 22.3.5:

:~> /usr/bin/nm --demangle -D /home/mypc/Temp/radeonsi_drv_video.so | grep
vaDriverInit
0000000000068a90 T __vaDriverInit_1_16

ILL patch
https://gitweb.gentoo.org/repo/gentoo.git/tree/media-libs/intel-hybrid-code=
c-driver/files/intel-hybrid-codec-driver-2.0.0-vadriverinit-fix.patch=20
is needed to solve that error.

Conclusion: please apply all 5 patches:
https://gitweb.gentoo.org/repo/gentoo.git/tree/media-libs/intel-hybrid-code=
c-driver/files
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17353068390.d326a6.50
Date: Fri, 27 Dec 2024 13:40:39 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1234858

          Summary
          Intel hybrid driver "hybrid_drv_video.so" for VA AP=
I (VAAPI) does not work

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          x86-64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X11 3rd Party Driver

          Assignee
          gfx-bugs@suse.de

          Reporter
          kaykaykay123@gmail.com

          QA Contact
          sndirsch@suse.com

          Target Milestone
          ---

          Found By
          Community User

          Blocker
          ---

Intel hybrid driver "hybrid_drv_video.so" for VA A=
PI (VAAPI) does not work.=20
It provides VP9 decoding for Intel GPUs from Haswell (maybe Ivy Bridge) till
Skylake by using CPU together with GPU shaders.=20

Package intel-hybrid-driver installs "hybrid_drv_video.so", requi=
res package
libcmrt1 to work.
Link to package: https://software.opensuse.org/package/intel-hybrid-driver
Intel-hybrid-driver is available for Leap - backported from SLE (bp156, bp1=
55
prefixes).

OpenSUSE uses 2 from 5 available patches.
Possibly patch "U_Update-the-dependency-to-libva-2.0.patch" is no=
t needed any
more.
http=
s://build.opensuse.org/projects/X11:XOrg/packages/intel-hybrid-driver/files=
/U_Update-the-dependency-to-libva-2.0.patch?expand=3D1

Intel hybrid driver versions:
https=
://repology.org/project/intel-hybrid-driver/versions

Intel hybrid driver patches from Gentoo:
https://gitweb.gentoo.org/repo/gentoo.git/tree/m=
edia-libs/intel-hybrid-codec-driver/files

After applying all 5 patches driver can be versioned as 2.0.0.

To test intel-hybrid-driver you need to explicitly require it by using
environment variable:
"LIBVA_DRIVER_NAME=3Dhybrid":

Now it is

:~> LIBVA_DRIVER_NAME=3Dhybrid vainfo
libva info: VA-API version 1.16.0
libva info: User environment variable requested driver 'hybrid'
libva info: Trying to open /usr/lib64/dri/hybrid_drv_video.so
libva error: /usr/lib64/dri/hybrid_drv_video.so has no function
__vaDriverInit_1_0
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

Output for working driver radeonsi_drv_video.so:

:~> vainfo
libva info: VA-API version 1.16.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_16
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.16 (libva 2.15.0)
vainfo: Driver version: Mesa Gallium driver 22.3.5 for AMD Radeon Graphics
(raven, LLVM 15.0.7, DRM 3.49, 5.14.21-150500.55.88-default)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointEncSlice
      VAProfileHEVCMain10             : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile2            : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc

Output for working hybrid_drv_video.so on some old system:

timo@Zeo ~ % export LIBVA_DRIVER_NAME=3Dhybrid
timo@Zeo ~ % vainfo
libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 0
libva info: User requested driver 'hybrid'
libva info: Trying to open /usr/lib64/va/drivers/hybrid_drv_video.so
libva info: Found init function __vaDriverInit_0_34
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.38 (libva 1.6.1.pre1)
vainfo: Driver version: Intel hybrid driver - 1.0.1.pre1
vainfo: Supported profile and entrypoints
      VAProfileVP8Version0_3          : VAEntrypointEncSlice
      VAProfileVP9Profile0            : VAEntrypointVLD

Exploring error "libva error: /usr/lib64/dri/hybrid_drv_video.so has no
function __vaDriverInit_1_0" ->

Finding vaDriverInit in intel-hybrid-driver driver:

:~> /usr/bin/nm --demangle -D
/home/mypc/Temp/intel-hybrid-driver-1.0.2-bp156.4.4.x86_64/usr/lib64/dri/hy=
brid_drv_video.so
| grep vaDriverInit
000000000001c530 T __vaDriverInit_0_34

Finding vaDriverInit in radeonsi_drv_video.so driver from Mesa 22.3.5:

:~> /usr/bin/nm --demangle -D /home/mypc/Temp/radeonsi_drv_video.so | gr=
ep
vaDriverInit
0000000000068a90 T __vaDriverInit_1_16

ILL patch
https://gitweb.gentoo.org/repo/gentoo.git/tree/media-libs/intel-hybr=
id-codec-driver/files/intel-hybrid-codec-driver-2.0.0-vadriverinit-fix.patc=
h=20
is needed to solve that error.

Conclusion: please apply all 5 patches:
https://gitweb.gentoo.org/repo/gentoo.git/tree/m=
edia-libs/intel-hybrid-codec-driver/files

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17353068390.d326a6.50--


body:
--17353576401.95BE2CE4.11
Date: Sat, 28 Dec 2024 03:47:20 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1234865

            Bug ID: 1234865
           Summary: emacs-wayland startup failure
    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-at-suse.de
          Reporter: 1923170329-at-qq.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

When I use emacs-x11 under GNOME Wayland it works, when I use emacs-wayland=
 it
comes up with

/usr/bin/emacs(emacs_backtrace+0x4c) [0x5602dd9524ac]
/usr/bin/emacs(terminate_due_to_signal+0x84) [0x5602dd82d76d]
/usr/bin/emacs(+0x8ff80) [0x5602dd82df80]
/usr/bin/emacs(+0x323c68) [0x5602ddac1c68]
/usr/bin/emacs(+0x1b2c79) [0x5602dd950c79]
/lib64/libc.so.6(+0x41580) [0x7f50d2441580]
/lib64/libnvidia-tls.so.565.57.01(+0x36e4) [0x7f50cf9256e4]
Segmentation fault (core dumped)

I am trying to compile emacs myself with the pgtk option and it works fine
under GNOME Wayland.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17353576401.95BE2CE4.11
Date: Sat, 28 Dec 2024 03:47:20 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1234865

          Summary
          emacs-wayland startup failure

          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@suse.de

          Reporter
          1923170329@qq.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

When I use emacs-x11 under GNOME Wayland it works, when I us=
e emacs-wayland it
comes up with

/usr/bin/emacs(emacs_backtrace+0x4c) [0x5602dd9524ac]
/usr/bin/emacs(terminate_due_to_signal+0x84) [0x5602dd82d76d]
/usr/bin/emacs(+0x8ff80) [0x5602dd82df80]
/usr/bin/emacs(+0x323c68) [0x5602ddac1c68]
/usr/bin/emacs(+0x1b2c79) [0x5602dd950c79]
/lib64/libc.so.6(+0x41580) [0x7f50d2441580]
/lib64/libnvidia-tls.so.565.57.01(+0x36e4) [0x7f50cf9256e4]
Segmentation fault (core dumped)

I am trying to compile emacs myself with the pgtk option and it works fine
under GNOME Wayland.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17353576401.95BE2CE4.11--

summary: emacs-wayland startup failure


--17354609852.5e86B860.17
Date: Sun, 29 Dec 2024 08:29:45 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1234870

            Bug ID: 1234870
           Summary: Virtualbox-guests-tools: /usr/lib/systemd/system/vboxclient.service: Unknown key 'ExecCondition' in section [Unit]
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: mark.wenzel@t-online.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

In a virtualbox virtual machine running openSUSE 15.6 as guest operating sy=
stem
in text mode:
- Install virtualbox-guest-tools from
http://download.opensuse.org/update/leap/15.6/oss:
Name               : virtualbox-guest-tools
Version            : 7.1.4-lp156.2.4.1
Arch               : x86_64
Anbieter           : openSUSE
Installierte Gr=C3=B6=C3=9Fe : 2,6 MiB
Installiert        : Ja
Status             : aktuell

In journal the following error is logged any time systemd reloads (i.e when
installing updates of any packages):
systemd[1]: /usr/lib/systemd/system/vboxclient.service:4: Unknown key
'ExecCondition' in section [Unit], ignoring.

- Show status: systemctl status vboxclient.service:
...
systemd[1]: /usr/lib/systemd/system/vboxclient.service:4: Unknown key
'ExecCondition' in section [Unit], ignoring.
...

ExecCondition should appear in [Service] section, not in [Unit] section.

Link to relevant documentation:
https://www.freedesktop.org/software/systemd/man/latest/systemd.service.htm=
l#ExecCondition=3D

When using 'ExecCondition' in section [Service] the exit code should not be=
 -1
because this means a failure. Instead a return code of 1 would indicate that
this service will be not started because of unmet condition.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17354609852.5e86B860.17
Date: Sun, 29 Dec 2024 08:29:45 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1234870

          Summary
          Virtualbox-guests-tools: /usr/lib/systemd/system/vboxclient.s=
ervice: Unknown key 'ExecCondition' in section [Unit]

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          x86-64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Virtualization:Tools

          Assignee
          virt-bugs@suse.de

          Reporter
          mark.wenzel@t-online.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

In a virtualbox virtual machine running openSUSE 15.6 as gue=
st operating system
in text mode:
- Install virtualbox-guest-tools from
http://downlo=
ad.opensuse.org/update/leap/15.6/oss:
Name               : virtualbox-guest-tools
Version            : 7.1.4-lp156.2.4.1
Arch               : x86_64
Anbieter           : openSUSE
Installierte Gr=C3=B6=C3=9Fe : 2,6 MiB
Installiert        : Ja
Status             : aktuell

In journal the following error is logged any time systemd reloads (i.e when
installing updates of any packages):
systemd[1]: /usr/lib/systemd/system/vboxclient.service:4: Unknown key
'ExecCondition' in section [Unit], ignoring.

- Show status: systemctl status vboxclient.service:
...
systemd[1]: /usr/lib/systemd/system/vboxclient.service:4: Unknown key
'ExecCondition' in section [Unit], ignoring.
...

ExecCondition should appear in [Service] section, not in [Unit] section.

Link to relevant documentation:
https://www.freedesktop.org/software/systemd/ma=
n/latest/systemd.service.html#ExecCondition=3D

When using 'ExecCondition' in section [Service] the exit code should not be=
 -1
because this means a failure. Instead a return code of 1 would indicate that
this service will be not started because of unmet condition.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17354609852.5e86B860.17--


body:
--17355576610.91b7.398
Date: Mon, 30 Dec 2024 11:21:01 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1234904

            Bug ID: 1234904
           Summary: openQA tests failing with systemd 257.1
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: ana.guerrero-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

After accepting 257.1 in Factory (SR#1233450) there are at least 2 openQA
testing failing that seem to be caused by this upload. So I'm reverting the
package.

nginx  https://openqa.opensuse.org/tests/4737876#step/nginx/14

# wait_serial expected: "systemctl --no-pager start nginx; echo aeoQx-\$?-"
# Result:
systemctl --no-pager start nginx; echo aeoQx-$?-

followed up by

# wait_serial expected: qr/aeoQx-\d+-/u
# Result:

Job for nginx.service failed because the control process exited with error
code.
See "systemctl status nginx.service" and "journalctl -xeu nginx.service" for
details.
aeoQx-1-

zdup https://openqa.opensuse.org/tests/4737947#step/zdup/224

(2481/3318) Installing: kded-5.116.0-1.1.x86_64 [.. ... done]
Additional rpm output:
user@0.service is not active, cannot reload.

several times until:

Error: Subprocess failed. Error: RPM failed: user@0.service is not active,
cannot reload.
error: %prein(libPlasma6-6.2.4-1.1.x86_64) scriptlet failed, exit status 1=
=20
error: libPlasma6-6.2.4-1.1.x86_64: install failed

Abort, retry, ignore? [a/r/i] (a):
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17355576610.91b7.398
Date: Mon, 30 Dec 2024 11:21:01 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1234904

          Summary
          openQA tests failing with systemd 257.1

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          ana.guerrero@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

After accepting 257.1 in Factory (SR#1233450) there are at l=
east 2 openQA
testing failing that seem to be caused by this upload. So I'm reverting the
package.

nginx  =
https://openqa.opensuse.org/tests/4737876#step/nginx/14

# wait_serial expected: "systemctl --no-pager start nginx; echo aeoQx-=
\$?-"
# Result:
systemctl --no-pager start nginx; echo aeoQx-$?-

followed up by

# wait_serial expected: qr/aeoQx-\d+-/u
# Result:

Job for nginx.service failed because the control process exited with error
code.
See "systemctl status nginx.service" and "journalctl -xeu ng=
inx.service" for
details.
aeoQx-1-

zdup ht=
tps://openqa.opensuse.org/tests/4737947#step/zdup/224

(2481/3318) Installing: kded-5.116.0-1.1.x86_64 [.. ... done]
Additional rpm output:
user@0.service is not active,=
 cannot reload.

several times until:

Error: Subprocess failed. Error: RPM failed: user@0.service is not active,
cannot reload.
error: %prein(libPlasma6-6.2.4-1.1.x86_64) scriptlet failed, exit status 1=
=20
error: libPlasma6-6.2.4-1.1.x86_64: install failed

Abort, retry, ignore? [a/r/i] (a):

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17355576610.91b7.398--

summary: openQA tests failing with systemd 257.1


--17356896121.B279A3Dd5.20
Date: Wed, 1 Jan 2025 00:00:12 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1234979

            Bug ID: 1234979
           Summary: wezterm complaining about missing cursor
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mrueckert-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

00:57:34.022  ERROR  window::os::wayland::window > set_cursor: Cursor not f=
ound

could this also be the reason why things like clicking the title bar e.g. d=
ont
work?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17356896121.B279A3Dd5.20
Date: Wed, 1 Jan 2025 00:00:12 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1234979

          Summary
          wezterm complaining about missing cursor

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          mrueckert@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

00:57:34.022  ERROR  window::os::wayland::window > set_cu=
rsor: Cursor not found

could this also be the reason why things like clicking the title bar e.g. d=
ont
work?

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17356896121.B279A3Dd5.20--


--17358169593.eEfa5A3.161
Date: Thu, 2 Jan 2025 11:22:39 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1234995

            Bug ID: 1234995
           Summary: libvirt:  libvirt: virtimetest failing with the change to  year 2025
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Other
          Assignee: virt-bugs-at-suse.de
          Reporter: ana.guerrero-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

The `virtimetest` in libvirt started failing with the transition to the year
2025. This failure is blocking Tumbleweed development.

I've created a Submit Request with a temporary fix:
https://build.opensuse.org/request/show/1234542. I plan to accept it today =
in
Factory to unblock development.

However, this issue needs a more permanent solution, hence this bug report.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17358169593.eEfa5A3.161
Date: Thu, 2 Jan 2025 11:22:39 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1234995

          Summary
          libvirt:  libvirt: virtimetest failing with the change to  ye=
ar 2025

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Virtualization:Other

          Assignee
          virt-bugs@suse.de

          Reporter
          ana.guerrero@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

The `virtimetest` in libvirt started failing with the transi=
tion to the year
2025. This failure is blocking Tumbleweed development.

I've created a Submit Request with a temporary fix:
https://build.o=
pensuse.org/request/show/1234542. I plan to accept it today in
Factory to unblock development.

However, this issue needs a more permanent solution, hence this bug report.=

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17358169593.eEfa5A3.161--


--17358564202.0eBA2fb4B.62
Date: Thu, 2 Jan 2025 22:20:20 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1235020

            Bug ID: 1235020
           Summary: Hard freeze workqueue lockup mediatek bluetooth
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: andrea.ippo-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Hi, I've been experiencing random lockups on TW for a while now (more than a
month):

https://community.frame.work/t/workqueue-lockup-opensuse-tw/60430 (I'm the =
OP
here)

https://forums.opensuse.org/t/workqueue-lockup-should-i-file-a-bug/180387

I had to switch to Fedora for the past couple of weeks, and surprisingly I
never experienced this issue there, which makes me think it might be relate=
d to
the opensuse kernel (or maybe, just bad luck on TW).

The problem seems to be related to bluetooth, as we can see by checking at =
the
logs at the timestamp preceding the BUG - lockup entry by X seconds as
specified in the error:

Examples:
https://pastebin.com/79dj1PeX
https://pastebin.com/n3m1S8B7

In both cases if we go back by 58s we get around this part:

Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Execution of wmt command
timed out
Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Failed to send wmt patch
dwnld (-110)
Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Failed to set up firmware
(-110)
Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: HCI Enhanced Setup
Synchronous Connection command is advertised, but not supported.
Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: Failed to read MSFT
supported features (-110)
Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: command 0xfd30 tx timeout
Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: AOSP get vendor capabili=
ties
(-110)
Jan 02 18:19:35 andromeda bluetoothd[1147]: Failed to set mode: Authenticat=
ion
Failed (0x05)

When this happens, my entire DE becomes unresponsive, even systemctl reboot
won't work and I'm forced to hard power off.

I'm running 6.12.6-1-default

Thanks
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17358564202.0eBA2fb4B.62
Date: Thu, 2 Jan 2025 22:20:20 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1235020

          Summary
          Hard freeze workqueue lockup mediatek bluetooth

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          andrea.ippo@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Hi, I've been experiencing random lockups on TW for a while =
now (more than a
month):

https://community.frame.work/t/workqueue-lockup-opensuse-tw/60430 (I=
'm the OP
here)

https://forums.opensuse.org/t/workqueue-lockup-should-i-file-a-b=
ug/180387

I had to switch to Fedora for the past couple of weeks, and surprisingly I
never experienced this issue there, which makes me think it might be relate=
d to
the opensuse kernel (or maybe, just bad luck on TW).

The problem seems to be related to bluetooth, as we can see by checking at =
the
logs at the timestamp preceding the BUG - lockup entry by X seconds as
specified in the error:

Examples:
https://pastebin.com/79dj1PeX
https://pastebin.com/n3m1S8B7

In both cases if we go back by 58s we get around this part:

Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Execution of wmt command
timed out
Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Failed to send wmt patch
dwnld (-110)
Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: Failed to set up firmware
(-110)
Jan 02 18:19:33 andromeda kernel: Bluetooth: hci0: HCI Enhanced Setup
Synchronous Connection command is advertised, but not supported.
Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: Failed to read MSFT
supported features (-110)
Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: command 0xfd30 tx timeout
Jan 02 18:19:35 andromeda kernel: Bluetooth: hci0: AOSP get vendor capabili=
ties
(-110)
Jan 02 18:19:35 andromeda bluetoothd[1147]: Failed to set mode: Authenticat=
ion
Failed (0x05)

When this happens, my entire DE becomes unresponsive, even systemctl reboot
won't work and I'm forced to hard power off.

I'm running 6.12.6-1-default

Thanks

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17358564202.0eBA2fb4B.62--


--17359499880.0CCA9b9.113
Date: Sat, 4 Jan 2025 00:19:48 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1235078

            Bug ID: 1235078
           Summary: easyeffects doesn't start on tumbleweed 20250102 - symbol lookup error: undefined symbol
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Maintenance
          Assignee: screening-team-bugs-at-suse.de
          Reporter: piotrus3g-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

System information:
Operating System: openSUSE Tumbleweed 20250102
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.6-1-default (64-bit)
Graphics Platform: X11
Processors: 4 =C3=97 Intel=C2=AE Core=E2=84=A2 i5-7600K CPU @ 3.80GHz
Memory: 15,6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

Issue description:
After updating to tumbleweed 20250102 easyeffects doesn't start anymore. It
worked without issues on the previous system update. Below is the output of
running it in terminal:

> easyeffects=20
easyeffects: symbol lookup error: easyeffects: undefined symbol:
_ZN3fmt3v116detail10locale_refC1ISt6localeEERKT_

Related journalctl output:

sty 04 01:04:46 tumbleweed systemd[1672]: Started
dbus-:1.2-com.github.wwmm.easyeffects@1.service.
sty 04 01:04:46 tumbleweed easyeffects[19505]: /usr/bin/easyeffects: symbol
lookup error: /usr/bin/easyeffects: undefined symbol:
_ZN3fmt3v116detail10locale_refC1ISt6localeEERKT_
sty 04 01:04:46 tumbleweed systemd[1672]:
dbus-:1.2-com.github.wwmm.easyeffects@1.service: Main process exited,
code=3Dexited, status=3D127/n/a
sty 04 01:04:46 tumbleweed systemd[1672]:
dbus-:1.2-com.github.wwmm.easyeffects@1.service: Failed with result
'exit-code'.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17359499880.0CCA9b9.113
Date: Sat, 4 Jan 2025 00:19:48 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1235078

          Summary
          easyeffects doesn't start on tumbleweed 20250102 - symbol loo=
kup error: undefined symbol

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Maintenance

          Assignee
          screening-team-bugs@suse.de

          Reporter
          piotrus3g@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

System information:
Operating System: openSUSE Tumbleweed 20250102
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.6-1-default (64-bit)
Graphics Platform: X11
Processors: 4 =C3=97 Intel=C2=AE Core=E2=84=A2 i5-7600K CPU @ 3.80GHz
Memory: 15,6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

Issue description:
After updating to tumbleweed 20250102 easyeffects doesn't start anymore. It
worked without issues on the previous system update. Below is the output of
running it in terminal:

> easyeffects
easyeffects: symbol lookup error: easyeffects: undefined symbol:
_ZN3fmt3v116detail10locale_refC1ISt6localeEERKT_

Related journalctl output:

sty 04 01:04:46 tumbleweed systemd[1672]: Started
dbus-:1.2-=
com.github.wwmm.easyeffects@1.service.
sty 04 01:04:46 tumbleweed easyeffects[19505]: /usr/bin/easyeffects: symbol
lookup error: /usr/bin/easyeffects: undefined symbol:
_ZN3fmt3v116detail10locale_refC1ISt6localeEERKT_
sty 04 01:04:46 tumbleweed systemd[1672]:
dbus-:1.2-=
com.github.wwmm.easyeffects@1.service: Main process exited,
code=3Dexited, status=3D127/n/a
sty 04 01:04:46 tumbleweed systemd[1672]:
dbus-:1.2-=
com.github.wwmm.easyeffects@1.service: Failed with result
'exit-code'.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17359499880.0CCA9b9.113--


--17362228624.8fa0F.536
Date: Tue, 7 Jan 2025 04:07:42 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1235144

            Bug ID: 1235144
           Summary: spack: records number of build machine cores
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: eich-at-suse.com
          Reporter: bwiedemann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: Development
           Blocker: ---

While working on reproducible builds for openSUSE,
I found that our spack package varies from the number of build machine core=
s.

To reproduce, you can use
for N in 1 4 ; do
  osc build -M=3Ddoc --release=3D1.1 --noservice --clean \
   --vm-type=3Dkvm -j$N --keep-pkg=3DRPMS.$N openSUSE_Tumbleweed
done
md5sum RPMS.*/spack-man-0.23.0-1.1.noarch.rpm
/usr/lib/build/pkg-diff.sh -a RPMS.{1,4}/spack-man-0.23.0-1.1.noarch.rpm

The diff for /usr/share/man/man1/spack.1 is
-.B spack.config.CONFIG_DEFAULTS =3D {\(aqconfig\(aq: {\(aqbuild_jobs\(aq: =
4,
\(aqbuild_stage\(aq: \(aq$tempdir/spack\-stage\(aq, \(aqchecksum\(aq: True,
\(aqconnect_timeout\(aq: 10, \(aqdebug\(aq: False, \(aqdirty\(aq: False,
\(aqlicense_dir\(aq:
\(aq/home/abuild/rpmbuild/BUILD/spack\-0.23.0/etc/spack/licenses\(aq,
\(aqverify_ssl\(aq: True}}
+.B spack.config.CONFIG_DEFAULTS =3D {\(aqconfig\(aq: {\(aqbuild_jobs\(aq: =
1,
\(aqbuild_stage\(aq: \(aq$tempdir/spack\-stage\(aq, \(aqchecksum\(aq: True,
\(aqconnect_timeout\(aq: 10, \(aqdebug\(aq: False, \(aqdirty\(aq: False,
\(aqlicense_dir\(aq:
\(aq/home/abuild/rpmbuild/BUILD/spack\-0.23.0/etc/spack/licenses\(aq,
\(aqverify_ssl\(aq: True}}
...
@@ -71561,7 +71561,7 @@
 .UNINDENT
 .INDENT 0.0
 .TP
-.B spack.config.determine_number_of_jobs(*, parallel: \X'tty: link
https://docs.python.org/3/library/functions.html#bool'\fI\%bool\fP\X'tty: l=
ink'
=3D False, max_cpus: \X'tty: link
https://docs.python.org/3/library/functions.html#int'\fI\%int\fP\X'tty: lin=
k' =3D
4, config: \fI\%Configuration\fP | \X'tty: link
https://docs.python.org/3/library/constants.html#None'\fI\%None\fP\X'tty: l=
ink'
=3D None) -> \X'tty: link
https://docs.python.org/3/library/functions.html#int'\fI\%int\fP\X'tty: lin=
k'
+.B spack.config.determine_number_of_jobs(*, parallel: \X'tty: link
https://docs.python.org/3/library/functions.html#bool'\fI\%bool\fP\X'tty: l=
ink'
=3D False, max_cpus: \X'tty: link
https://docs.python.org/3/library/functions.html#int'\fI\%int\fP\X'tty: lin=
k' =3D
1, config: \fI\%Configuration\fP | \X'tty: link
https://docs.python.org/3/library/constants.html#None'\fI\%None\fP\X'tty: l=
ink'
=3D None) -> \X'tty: link
https://docs.python.org/3/library/functions.html#int'\fI\%int\fP\X'tty: lin=
k'
 Packages that require sequential builds need 1 job. Otherwise we use the

my 2y old notes say, the output is produced by=20
makeinfo --no-split -o 'Spack.info' 'Spack.texi'
and the input Spack.texi already varies.

https://github.com/spack/spack/pull/36064 and
https://github.com/spack/spack/pull/20629 had an old patch.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17362228624.8fa0F.536
Date: Tue, 7 Jan 2025 04:07:42 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1235144

          Summary
          spack: records number of build machine cores

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          All

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          eich@suse.com

          Reporter
          bwiedemann@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          Development

          Blocker
          ---

While working on reproducible builds for openSUSE,
I found that our spack package varies from the number of build machine core=
s.

To reproduce, you can use
for N in 1 4 ; do
  osc build -M=3Ddoc --release=3D1.1 --noservice --clean \
   --vm-type=3Dkvm -j$N --keep-pkg=3DRPMS.$N openSUSE_Tumbleweed
done
md5sum RPMS.*/spack-man-0.23.0-1.1.noarch.rpm
/usr/lib/build/pkg-diff.sh -a RPMS.{1,4}/spack-man-0.23.0-1.1.noarch.rpm

The diff for /usr/share/man/man1/spack.1 is
-.B spack.config.CONFIG_DEFAULTS =3D {\(aqconfig\(aq: {\(aqbuild_jobs\(aq: =
4,
\(aqbuild_stage\(aq: \(aq$tempdir/spack\-stage\(aq, \(aqchecksum\(aq: True,
\(aqconnect_timeout\(aq: 10, \(aqdebug\(aq: False, \(aqdirty\(aq: False,
\(aqlicense_dir\(aq:
\(aq/home/abuild/rpmbuild/BUILD/spack\-0.23.0/etc/spack/licenses\(aq,
\(aqverify_ssl\(aq: True}}
+.B spack.config.CONFIG_DEFAULTS =3D {\(aqconfig\(aq: {\(aqbuild_jobs\(aq: =
1,
\(aqbuild_stage\(aq: \(aq$tempdir/spack\-stage\(aq, \(aqchecksum\(aq: True,
\(aqconnect_timeout\(aq: 10, \(aqdebug\(aq: False, \(aqdirty\(aq: False,
\(aqlicense_dir\(aq:
\(aq/home/abuild/rpmbuild/BUILD/spack\-0.23.0/etc/spack/licenses\(aq,
\(aqverify_ssl\(aq: True}}
...
@@ -71561,7 +71561,7 @@
 .UNINDENT
 .INDENT 0.0
 .TP
-.B spack.config.determine_number_of_jobs(*, parallel: \X'tty: link
https://docs.python.org/3/library/functions.html#bool'\fI\%bool\f=
P\X'tty: link'
=3D False, max_cpus: \X'tty: link
https://docs.python.org/3/library/functions.html#int'\fI\%int\fP\X'=
tty: link' =3D
4, config: \fI\%Configuration\fP | \X'tty: link
https://docs.python.org/3/library/constants.html#None'\fI\%None\f=
P\X'tty: link'
=3D None) -> \X'tty: link
https://docs.python.org/3/library/functions.html#int'\fI\%int\fP\X'=
tty: link'
+.B spack.config.determine_number_of_jobs(*, parallel: \X'tty: link
https://docs.python.org/3/library/functions.html#bool'\fI\%bool\f=
P\X'tty: link'
=3D False, max_cpus: \X'tty: link
https://docs.python.org/3/library/functions.html#int'\fI\%int\fP\X'=
tty: link' =3D
1, config: \fI\%Configuration\fP | \X'tty: link
https://docs.python.org/3/library/constants.html#None'\fI\%None\f=
P\X'tty: link'
=3D None) -> \X'tty: link
https://docs.python.org/3/library/functions.html#int'\fI\%int\fP\X'=
tty: link'
 Packages that require sequential builds need 1 job. Otherwise we use the

my 2y old notes say, the output is produced by=20
makeinfo --no-split -o 'Spack.info' 'Spack.texi'
and the input Spack.texi already varies.

https://github.com/sp=
ack/spack/pull/36064 and
https://github.com/sp=
ack/spack/pull/20629 had an old patch.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17362228624.8fa0F.536--


--17362324171.2CAD.48
Date: Tue, 7 Jan 2025 06:46:57 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1235146

            Bug ID: 1235146
           Summary: [6.13] vbox kmp fails to build with kernel 6.13
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Other
          Assignee: virt-bugs-at-suse.de
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

https://build.opensuse.org/package/live_build_log/Kernel:HEAD:KMP/virtualbo=
x:kmp/standard/x86_64
> [   83s] vbox_drv.c:43:11: fatal error: drm/drm_aperture.h: No such file =
or directory
> [   83s]    43 | # include <drm/drm_aperture.h>
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17362324171.2CAD.48
Date: Tue, 7 Jan 2025 06:46:57 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1235146

          Summary
          [6.13] vbox kmp fails to build with kernel 6.13

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Virtualization:Other

          Assignee
          virt-bugs@suse.de

          Reporter
          jslaby@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

https://build.opensuse.org=
/package/live_build_log/Kernel:HEAD:KMP/virtualbox:kmp/standard/x86_64
> [   83s] vbox_drv.c:43:11: fatal error: drm/drm_=
aperture.h: No such file or directory
> [   83s]    43 | # include <drm/drm_aperture.h>

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17362324171.2CAD.48--


--17362428810.5BFBb8C8.303
Date: Tue, 7 Jan 2025 09:41:21 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1235150

            Bug ID: 1235150
           Summary: X11:wxWidgets/wxWidgets-3_2: Please build with GLCANVAS_EGL for Wayland
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: sbrabec-at-suse.com
          Reporter: asn-at-cryptomilk.org
        QA Contact: screening-team-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Currently we are not able to build several applications with wayland suppor=
t,
because wxWidget isn't built with -DwxUSE_GLCANVAS_EGL=3DON.

Could you please enable it?

P.S.: You can also build wxWidgets with cmake.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17362428810.5BFBb8C8.303
Date: Tue, 7 Jan 2025 09:41:21 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1235150

          Summary
          X11:wxWidgets/wxWidgets-3_2: Please build with GLCANVAS_EGL f=
or Wayland

          Classification
          openSUSE

          Product
          openSUSE.org

          Version
          unspecified

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          3rd party software

          Assignee
          sbrabec@suse.com

          Reporter
          asn@cryptomilk.org

          QA Contact
          screening-team-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Currently we are not able to build several applications with=
 wayland support,
because wxWidget isn't built with -DwxUSE_GLCANVAS_EGL=3DON.

Could you please enable it?

P.S.: You can also build wxWidgets with cmake.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17362428810.5BFBb8C8.303--


--17362487179.fF10e.588
Date: Tue, 7 Jan 2025 11:18:37 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1235162

            Bug ID: 1235162
           Summary: VUL-0: CVE-2023-49295: kubo: github.com/quic-go/quic-go: memory exhaustion attack against QUIC's path validation mechanism
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
               URL: https://smash.suse.de/issue/390776/
                OS: Other
            Status: NEW
        Whiteboard: CVSSv3.1:SUSE:CVE-2023-49295:6.5:(AV:N/AC:L/PR:L/UI:N/
                    S:U/C:N/I:N/A:H)
                    CVSSv4:SUSE:CVE-2023-49295:6.0:(AV:N/AC:L/AT:P/PR:L/UI
                    :N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N)
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: bwiedemann-at-suse.com
          Reporter: andrea.mattiazzo-at-suse.com
        QA Contact: security-team-at-suse.de
            Blocks: 1234982
  Target Milestone: ---
          Found By: ---
           Blocker: ---

quic-go is an implementation of the QUIC protocol (RFC 9000, RFC 9001, RFC
9002) in Go. An attacker can cause its peer to run out of memory sending a
large number of PATH_CHALLENGE frames. The receiver is supposed to respond =
to
each PATH_CHALLENGE frame with a PATH_RESPONSE frame. The attacker can prev=
ent
the receiver from sending out (the vast majority of) these PATH_RESPONSE fr=
ames
by collapsing the peers congestion window (by selectively acknowledging
received packets) and by manipulating the peer's RTT estimate. This
vulnerability has been patched in versions 0.37.7, 0.38.2 and 0.39.4.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2023-49295
https://www.cve.org/CVERecord?id=3DCVE-2023-49295
https://github.com/quic-go/quic-go/commit/17fc98c2d81dbe685c19702dc694a9d60=
6ac56dc
https://github.com/quic-go/quic-go/commit/21609ddfeff93668c7625a85eb09f1541=
fdad965
https://github.com/quic-go/quic-go/commit/3a9c18bcd27a01c551ac9bf8bd2b4bded=
77c189a
https://github.com/quic-go/quic-go/commit/554d543b50b917369fb1394cc5396d928=
166cf49
https://github.com/quic-go/quic-go/commit/6cc3d58935426191296171a6c0d1ee965=
e10534e
https://github.com/quic-go/quic-go/commit/9aaefe19fc3dc8c8917cc87e6128bb56d=
9e9e6cc
https://github.com/quic-go/quic-go/commit/a0ffa757499913f7be69aa78f573a6aee=
3430ae4
https://github.com/quic-go/quic-go/commit/d7aa627ebde91cf799ada2a07443faa9b=
1e5abb8
https://github.com/quic-go/quic-go/security/advisories/GHSA-ppxx-5m9h-6vxf
https://bugzilla.redhat.com/show_bug.cgi?id=3D2257815
https://lists.fedoraproject.org/archives/list/package-announce-at-lists.fedora=
project.org/message/G5RSHDTVMYAIGYVVFGKTMFHAZJMA3EVV/
https://lists.fedoraproject.org/archives/list/package-announce-at-lists.fedora=
project.org/message/ZE7IOKXX5AATU2WR3V76X5Y3A44QAATG/
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17362487179.fF10e.588
Date: Tue, 7 Jan 2025 11:18:37 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1235162

          Summary
          VUL-0: CVE-2023-49295: kubo: github.com/quic-go/quic-go: memo=
ry exhaustion attack against QUIC's path validation mechanism

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          URL
          https://smash.suse.de/issue/390776/

          OS
          Other

          Status
          NEW

          Whiteboard
          CVSSv3.1:SUSE:CVE-2023-49295:6.5:(AV:N/AC:L/PR:L/UI:N/S:U/C:N=
/I:N/A:H) CVSSv4:SUSE:CVE-2023-49295:6.0:(AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:=
N/VA:H/SC:N/SI:N/SA:N)

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          bwiedemann@suse.com

          Reporter
          andrea.mattiazzo@suse.com

          QA Contact
          security-team@suse.de

          Blocks
          1234982

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

quic-go is an implementation of the QUIC protocol (RFC 9000,=
 RFC 9001, RFC
9002) in Go. An attacker can cause its peer to run out of memory sending a
large number of PATH_CHALLENGE frames. The receiver is supposed to respond =
to
each PATH_CHALLENGE frame with a PATH_RESPONSE frame. The attacker can prev=
ent
the receiver from sending out (the vast majority of) these PATH_RESPONSE fr=
ames
by collapsing the peers congestion window (by selectively acknowledging
received packets) and by manipulating the peer's RTT estimate. This
vulnerability has been patched in versions 0.37.7, 0.38.2 and 0.39.4.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2023-49295
https://www.c=
ve.org/CVERecord?id=3DCVE-2023-49295
https://github.com/quic-go/quic-go/commit/17fc98c2d81db=
e685c19702dc694a9d606ac56dc
https://github.com/quic-go/quic-go/commit/21609ddfeff93=
668c7625a85eb09f1541fdad965
https://github.com/quic-go/quic-go/commit/3a9c18bcd27a0=
1c551ac9bf8bd2b4bded77c189a
https://github.com/quic-go/quic-go/commit/554d543b50b91=
7369fb1394cc5396d928166cf49
https://github.com/quic-go/quic-go/commit/6cc3d58935426=
191296171a6c0d1ee965e10534e
https://github.com/quic-go/quic-go/commit/9aaefe19fc3dc=
8c8917cc87e6128bb56d9e9e6cc
https://github.com/quic-go/quic-go/commit/a0ffa75749991=
3f7be69aa78f573a6aee3430ae4
https://github.com/quic-go/quic-go/commit/d7aa627ebde91=
cf799ada2a07443faa9b1e5abb8
https://github.com/quic-go/quic-go/security/advisories/GHSA-ppx=
x-5m9h-6vxf
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2257815
https=
://lists.fedoraproject.org/archives/list/package-announce@lists.fedorap=
roject.org/message/G5RSHDTVMYAIGYVVFGKTMFHAZJMA3EVV/
https=
://lists.fedoraproject.org/archives/list/package-announce@lists.fedorap=
roject.org/message/ZE7IOKXX5AATU2WR3V76X5Y3A44QAATG/

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17362487179.fF10e.588--


body:
--17362665114.EF974bed.1331
Date: Tue, 7 Jan 2025 16:15:11 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1235247

            Bug ID: 1235247
           Summary: nscd incompatible with with systemd 257
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: schwab-at-suse.de
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: ana.guerrero-at-suse.com, fbui-at-suse.com, kukuk-at-suse.com,
                    qa-bugs-at-suse.de
        Depends on: 1234904
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Installing the nginx package invokes systemd-sysusers for creating the nginx
system user and group. While the user was created successfully, nginx fails=
 to
start because getpwnam("nginx") fails. Fresh installations of TW do not ins=
tall
nscd by default and do not show this failure.

Output from zypper:
( 9/11) Installing: nginx-1.27.3-1.1.x86_64 [..
/usr/bin/systemd-sysusers --replace=3D/usr/lib/sysusers.d/nginx.conf -
Creating group 'nginx' with GID 445.
Creating user 'nginx' (User for nginx) with UID 445 and GID 445.
done]

The journal shows:

Dec 30 03:29:23.732701 susetest nscd[1000]: 1000 monitored file `/etc/group`
was moved into place, adding watch
Dec 30 03:29:23.734160 susetest nscd[1000]: 1000 ignored inotify event for
`/etc/passwd` (file exists)
Dec 30 03:29:23.734166 susetest nscd[1000]: 1000 ignored inotify event for
`/etc/passwd` (file exists)
Dec 30 03:29:23.734170 susetest nscd[1000]: 1000 ignored inotify event for
`/etc/passwd` (file exists)
Dec 30 03:29:23.737131 susetest nscd[1000]: 1000 monitored file `/etc/group`
was written to
Dec 30 03:29:23.783331 susetest [RPM][38374]: install nginx-1.27.3-1.1.x86_=
64:
success
Dec 30 03:29:23.785165 susetest [RPM][38374]: install nginx-1.27.3-1.1.x86_=
64:
success
Dec 30 03:29:23.785171 susetest [RPM][38374]: Transaction ID 677259e3 finis=
hed:
0
...
Dec 30 03:29:28 susetest nginx[40235]: nginx: [emerg] getpwnam("nginx") fai=
led

It appears like the inotify events for /etc/passwd are not handled properly?

Using inotifywait, I see that systemd-sysusers triggers the following event=
s at
the end:

/etc/ MOVED_FROM .#groupc5866089038123a0
/etc/ MOVED_TO group
/etc/ MOVED_FROM .#passwdbd62e5a7a6a138fe
/etc/ MOVED_TO passwd
/etc/ MOVED_FROM .#shadow710f5a458e31233a
/etc/ MOVED_TO shadow
/etc/ CLOSE_WRITE,CLOSE shadow
/etc/ CLOSE_WRITE,CLOSE group
/etc/ CLOSE_WRITE,CLOSE passwd

Given that nscd is not part of fresh installations of TW anymore, the easie=
st
and most consistent option is probably to drop the nscd package from the
distribution.

+++ This bug was initially created as a clone of Bug #1234904 +++

After accepting 257.1 in Factory (SR#1233450) there are at least 2 openQA
testing failing that seem to be caused by this upload. So I'm reverting the
package.

nginx  https://openqa.opensuse.org/tests/4737876#step/nginx/14

# wait_serial expected: "systemctl --no-pager start nginx; echo aeoQx-\$?-"
# Result:
systemctl --no-pager start nginx; echo aeoQx-$?-

followed up by

# wait_serial expected: qr/aeoQx-\d+-/u
# Result:

Job for nginx.service failed because the control process exited with error
code.
See "systemctl status nginx.service" and "journalctl -xeu nginx.service" for
details.
aeoQx-1-
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17362665114.EF974bed.1331
Date: Tue, 7 Jan 2025 16:15:11 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1235247

          Summary
          nscd incompatible with with systemd 257

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          schwab@suse.de

          Reporter
          fvogt@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          ana.guerrero@suse.com, fbui@suse.com, kukuk@suse.=
com, qa-bugs@suse.de

          Depends on
          1234904

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Installing the nginx package invokes systemd-sysusers for cr=
eating the nginx
system user and group. While the user was created successfully, nginx fails=
 to
start because getpwnam("nginx") fails. Fresh installations of TW =
do not install
nscd by default and do not show this failure.

Output from zypper:
( 9/11) Installing: nginx-1.27.3-1.1.x86_64 [..
/usr/bin/systemd-sysusers --replace=3D/usr/lib/sysusers.d/nginx.conf -
Creating group 'nginx' with GID 445.
Creating user 'nginx' (User for nginx) with UID 445 and GID 445.
done]

The journal shows:

Dec 30 03:29:23.732701 susetest nscd[1000]: 1000 monitored file `/etc/group`
was moved into place, adding watch
Dec 30 03:29:23.734160 susetest nscd[1000]: 1000 ignored inotify event for
`/etc/passwd` (file exists)
Dec 30 03:29:23.734166 susetest nscd[1000]: 1000 ignored inotify event for
`/etc/passwd` (file exists)
Dec 30 03:29:23.734170 susetest nscd[1000]: 1000 ignored inotify event for
`/etc/passwd` (file exists)
Dec 30 03:29:23.737131 susetest nscd[1000]: 1000 monitored file `/etc/group`
was written to
Dec 30 03:29:23.783331 susetest [RPM][38374]: install nginx-1.27.3-1.1.x86_=
64:
success
Dec 30 03:29:23.785165 susetest [RPM][38374]: install nginx-1.27.3-1.1.x86_=
64:
success
Dec 30 03:29:23.785171 susetest [RPM][38374]: Transaction ID 677259e3 finis=
hed:
0
...
Dec 30 03:29:28 susetest nginx[40235]: nginx: [emerg] getpwnam("nginx&=
quot;) failed

It appears like the inotify events for /etc/passwd are not handled properly?

Using inotifywait, I see that systemd-sysusers triggers the following event=
s at
the end:

/etc/ MOVED_FROM .#groupc5866089038123a0
/etc/ MOVED_TO group
/etc/ MOVED_FROM .#passwdbd62e5a7a6a138fe
/etc/ MOVED_TO passwd
/etc/ MOVED_FROM .#shadow710f5a458e31233a
/etc/ MOVED_TO shadow
/etc/ CLOSE_WRITE,CLOSE shadow
/etc/ CLOSE_WRITE,CLOSE group
/etc/ CLOSE_WRITE,CLOSE passwd

Given that nscd is not part of fresh installations of TW anymore, the easie=
st
and most consistent option is probably to drop the nscd package from the
distribution.

+++ This bug was initially created as a clone of Bug #1234904 +++

After accepting 257.1 in Factory (SR#1233450) there are at least 2 openQA
testing failing that seem to be caused by this upload. So I'm reverting the
package.

nginx  =
https://openqa.opensuse.org/tests/4737876#step/nginx/14

# wait_serial expected: "systemctl --no-pager start nginx; echo aeoQx-=
\$?-"
# Result:
systemctl --no-pager start nginx; echo aeoQx-$?-

followed up by

# wait_serial expected: qr/aeoQx-\d+-/u
# Result:

Job for nginx.service failed because the control process exited with error
code.
See "systemctl status nginx.service" and "journalctl -xeu ng=
inx.service" for
details.
aeoQx-1-

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17362665114.EF974bed.1331--

summary: nscd incompatible with with systemd 257


--17362688002.22E566Df.1544
Date: Tue, 7 Jan 2025 16:53:20 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1235332

            Bug ID: 1235332
           Summary: VUL-0: CVE-2024-45338: hauler: golang.org/x/net/html: denial of service due to non-linear parsing of case-insensitive content
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
               URL: https://smash.suse.de/issue/433408/
                OS: Other
            Status: NEW
        Whiteboard: CVSSv3.1:SUSE:CVE-2024-45338:5.9:(AV:N/AC:H/PR:N/UI:N/
                    S:U/C:N/I:N/A:H)
                    CVSSv4:SUSE:CVE-2024-45338:8.2:(AV:N/AC:H/AT:P/PR:N/UI
                    :N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N)
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: dmueller-at-suse.com
          Reporter: andrea.mattiazzo-at-suse.com
        QA Contact: security-team-at-suse.de
            Blocks: 1234794
  Target Milestone: ---
          Found By: ---
           Blocker: ---

An attacker can craft an input to the Parse functions that would be process=
ed
non-linearly with respect to its length, resulting in extremely slow parsin=
g.
This could cause a denial of service.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45338
https://www.cve.org/CVERecord?id=3DCVE-2024-45338
https://go.dev/cl/637536
https://go.dev/issue/70906
https://groups.google.com/g/golang-announce/c/wSCRmFnNmPA/m/Lvcd0mRMAwAJ
https://pkg.go.dev/vuln/GO-2024-3333
https://bugzilla.redhat.com/show_bug.cgi?id=3D2333122
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17362688002.22E566Df.1544
Date: Tue, 7 Jan 2025 16:53:20 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1235332

          Summary
          VUL-0: CVE-2024-45338: hauler: golang.org/x/net/html: denial =
of service due to non-linear parsing of case-insensitive content

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          URL
          https://smash.suse.de/issue/433408/

          OS
          Other

          Status
          NEW

          Whiteboard
          CVSSv3.1:SUSE:CVE-2024-45338:5.9:(AV:N/AC:H/PR:N/UI:N/S:U/C:N=
/I:N/A:H) CVSSv4:SUSE:CVE-2024-45338:8.2:(AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:=
N/VA:H/SC:N/SI:N/SA:N)

          Severity
          Major

          Priority
          P5 - None

          Component
          Security

          Assignee
          dmueller@suse.com

          Reporter
          andrea.mattiazzo@suse.com

          QA Contact
          security-team@suse.de

          Blocks
          1234794

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

An attacker can craft an input to the Parse functions that w=
ould be processed
non-linearly with respect to its length, resulting in extremely slow parsin=
g.
This could cause a denial of service.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45338
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-45338
https://go.dev/cl/637536
https://go.dev/issue/70906
https://groups.google.com/g/golang-announce/c/wSCRmFnNmPA/m/Lvcd0=
mRMAwAJ
https://pkg.go.dev/vuln/GO=
-2024-3333
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2333122

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17362688002.22E566Df.1544--