--17186524202.0dfcc.18840
Date: Mon, 17 Jun 2024 19:27:00 +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=3D1226449

            Bug ID: 1226449
           Summary: Intermittent sound Lenovo Legion Pro 7 16ARX8H
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: brynn-at-hotmail.co.uk
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 875531
  --> https://bugzilla.suse.com/attachment.cgi?id=3D875531&action=3Dedit
alsa -info.sh With no sound

I have intermittent sound from my speakers. Ive had this on a couple of for=
ums
for a while to try gather more info but no luck.

The quirks have only recently been added to allow the speakers to work and =
they
do but they stop after a few minutes if i open another window or click a
notification.

However, if i open a video in vlc before they have stopped it will play fine
for half an hour.

When they have stopped I can bring it back by setting my laptop to sleep and
waking it up again the immediately playing something

They have stopped in the time its taken to type this out.

I=E2=80=99ve attached alsa-info.sh with the sound working and one without f=
rom the same
boot a few minutes apart.

To work around this i can play a long audio file on loop with the volume se=
t to
0.

This is somewhat related to Bug 1223462. I never noticed this being an issue
with 6.7.9-1-default but don't have it any more and its too far back in the
repo history for me to download.

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

--17186524202.0dfcc.18840
Date: Mon, 17 Jun 2024 19:27:00 +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
          1226449

          Summary
          Intermittent sound Lenovo Legion Pro 7 16ARX8H

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Sound

          Assignee
          tiwai@suse.com

          Reporter
          brynn@hotmail.co.uk

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment=
 875531 [details]
alsa -info.sh With no sound

I have intermittent sound from my speakers. Ive had this on a couple of for=
ums
for a while to try gather more info but no luck.

The quirks have only recently been added to allow the speakers to work and =
they
do but they stop after a few minutes if i open another window or click a
notification.

However, if i open a video in vlc before they have stopped it will play fine
for half an hour.

When they have stopped I can bring it back by setting my laptop to sleep and
waking it up again the immediately playing something

They have stopped in the time its taken to type this out.

I=E2=80=99ve attached alsa-info.sh with the sound working and one without f=
rom the same
boot a few minutes apart.

To work around this i can play a long audio file on loop with the volume se=
t to
0.

This is somewhat related to Bug 1223462. I never noticed this=
 being an issue
with 6.7.9-1-default but don't have it any more and its too far back in the
repo history for me to download.

Thanks brynn.

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

You are on the CC list for the bug.

=

--17186524202.0dfcc.18840--


--17186694051.6356A9c.19023
Date: Tue, 18 Jun 2024 00:10:05 +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=3D1226452

            Bug ID: 1226452
           Summary: pam-config: Faulty on user systemd services due to encrypted home dir
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: joseskvolpe-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Systemd is triggered before user home directory is unlocked with fscrypt or
ecryptfs, which results on errors with some services.

To reproduce the issue i'm using fscrypt and onedriver
(home:jstaf/packages/onedriver), i've setup to automount my OneDrive storag=
e in
a directory inside my home dir. After logging in i get an error about
'/etc/mtab' not having the OneDriver entry. Changing the pam.d order in
/etc/pam.d/common-session fixes that.

Fscrypt README
(https://github.com/google/fscrypt?tab=3Dreadme-ov-file#enabling-the-pam-mo=
dule-on-other-linux-distros)
advices to call pam_fscrypt.so before pam_systemd.so.

The original file is found as:
session optional        pam_systemd.so
session required        pam_limits.so=20=20=20
session required        pam_unix.so     try_first_pass
session optional        pam_umask.so=20=20=20=20
session optional        pam_fscrypt.so
(...)

It should be:
session required        pam_limits.so=20=20=20
session required        pam_unix.so     try_first_pass
session optional        pam_umask.so=20=20=20=20
session optional        pam_fscrypt.so
session optional        pam_systemd.so
(...)

EXPECTED RESULTS: The user home directory must be unlocked before trying to
execute any user service. This configuration must be automatically set by
pam-config.

CURRENT RESULTS: SystemD is triggered to start user services before it's ho=
me
directory is unlocked, which breaks some programs.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17186694051.6356A9c.19023
Date: Tue, 18 Jun 2024 00:10:05 +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
          1226452

          Summary
          pam-config: Faulty on user systemd services due to encrypted =
home dir

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          All

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          joseskvolpe@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Systemd is triggered before user home directory is unlocked =
with fscrypt or
ecryptfs, which results on errors with some services.

To reproduce the issue i'm using fscrypt and onedriver
(home:jstaf/packages/onedriver), i've setup to automount my OneDrive storag=
e in
a directory inside my home dir. After logging in i get an error about
'/etc/mtab' not having the OneDriver entry. Changing the pam.d order in
/etc/pam.d/common-session fixes that.

Fscrypt README
(https://github.com/google/fscrypt?t=
ab=3Dreadme-ov-file#enabling-the-pam-module-on-other-linux-distros)
advices to call pam_fscrypt.so before pam_systemd.so.

The original file is found as:
session optional        pam_systemd.so
session required        pam_limits.so=20=20=20
session required        pam_unix.so     try_first_pass
session optional        pam_umask.so=20=20=20=20
session optional        pam_fscrypt.so
(...)

It should be:
session required        pam_limits.so=20=20=20
session required        pam_unix.so     try_first_pass
session optional        pam_umask.so=20=20=20=20
session optional        pam_fscrypt.so
session optional        pam_systemd.so
(...)

EXPECTED RESULTS: The user home directory must be unlocked before trying to
execute any user service. This configuration must be automatically set by
pam-config.

CURRENT RESULTS: SystemD is triggered to start user services before it's ho=
me
directory is unlocked, which breaks some programs.

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

You are on the CC list for the bug.

=

--17186694051.6356A9c.19023--


--17186944492.c799Aa22.19272
Date: Tue, 18 Jun 2024 07:07:29 +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=3D1226459

            Bug ID: 1226459
           Summary: network:utilities/socat: Bug: E xioopen_ipdgram_listen(): unknown address family 0
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: meissner-at-suse.com
          Reporter: szotsaki-at-gmail.com
        QA Contact: screening-team-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

When starting socat with UDP listening, it fails with the error message in =
the
title.

Please, see https://github.com/termux/termux-packages/issues/18645 for the
details, and please apply the patch there.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17186944492.c799Aa22.19272
Date: Tue, 18 Jun 2024 07:07:29 +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
          1226459

          Summary
          network:utilities/socat: Bug: E xioopen_ipdgram_listen(): unk=
nown address family 0

          Classification
          openSUSE

          Product
          openSUSE.org

          Version
          unspecified

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          3rd party software

          Assignee
          meissner@suse.com

          Reporter
          szotsaki@gmail.com

          QA Contact
          screening-team-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

When starting socat with UDP listening, it fails with the er=
ror message in the
title.

Please, see https://github.com/termux/termux-packages/issues/18645 for the
details, and please apply the patch there.

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

You are on the CC list for the bug.

=

--17186944492.c799Aa22.19272--


--17186945961.B3C0C.19281
Date: Tue, 18 Jun 2024 07:09:56 +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=3D1226460

            Bug ID: 1226460
           Summary: AUDIT-0: aaa_base: sysctl.d/52-yama.conf
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

As discussed in several threads, to make it easier for developers to enable
ptrace again for development, aaa_base has a new sub-package with a sysctl.d
file for this:

aaa_base-yama-enable-ptrace
/usr/lib/sysctl.d/52-yama.conf
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17186945961.B3C0C.19281
Date: Tue, 18 Jun 2024 07:09:56 +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
          1226460

          Summary
          AUDIT-0: aaa_base: sysctl.d/52-yama.conf

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          kukuk@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

As discussed in several threads, to make it easier for devel=
opers to enable
ptrace again for development, aaa_base has a new sub-package with a sysctl.d
file for this:

aaa_base-yama-enable-ptrace
/usr/lib/sysctl.d/52-yama.conf

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

You are on the CC list for the bug.

=

--17186945961.B3C0C.19281--


--17186947244.BAdfa345.19293
Date: Tue, 18 Jun 2024 07:12:04 +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=3D1226462

            Bug ID: 1226462
           Summary: Drop text, icons, theme etc after last update in KDE
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: didekridek-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 875538
  --> https://bugzilla.suse.com/attachment.cgi?id=3D875538&action=3Dedit
Text in KDE settings

After last full system update i have this (watch my screen and screen from
community).

Now i don't have mouse "icon" cursor, but mouse working in "transparent" mo=
de
)))

Something with 90% of text on shortcut names, widgets and etc.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17186947244.BAdfa345.19293
Date: Tue, 18 Jun 2024 07:12:04 +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
          1226462

          Summary
          Drop text, icons, theme etc after last update in KDE

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Critical

          Priority
          P5 - None

          Component
          KDE Workspace (Plasma)

          Assignee
          opensuse-kde-bugs@opensuse.org

          Reporter
          didekridek@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 875538=
 [details]
Text in KDE settings

After last full system update i have this (watch my screen and screen from
community).

Now i don't have mouse "icon" cursor, but mouse working in "=
transparent" mode
)))

Something with 90% of text on shortcut names, widgets and etc.

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

You are on the CC list for the bug.

=

--17186947244.BAdfa345.19293--


--17186951113.Fc4F91.19323
Date: Tue, 18 Jun 2024 07:18:31 +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=3D1226463

            Bug ID: 1226463
           Summary: algif_hash in kernel-obs-build causes an openssl-1_1 test failure
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 875539
  --> https://bugzilla.suse.com/attachment.cgi?id=3D875539&action=3Dedit
diff of lsinitrd

From
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:=
K/openssl-1_1/standard/x86_64
:

> [  248s] ../test/recipes/30-test_afalg.t                  (Wstat: 256 (ex=
ited 1) Tests: 1 Failed: 1)

Comparing /proc/modules in the build VM shows:
+algif_hash 12288 0 - Live 0x0000000000000000 (E)
+af_alg 36864 1 algif_hash, Live 0x0000000000000000 (E)

So apparently, algif_hash brings af_alg and that for some unknown reason br=
eaks
the test.

If I rm algif_hash from KERNEL_MODULES, it works again.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17186951113.Fc4F91.19323
Date: Tue, 18 Jun 2024 07:18:31 +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
          1226463

          Summary
          algif_hash in kernel-obs-build causes an openssl-1_1 test fai=
lure

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          jslaby@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created att=
achment 875539 [details]
diff of lsinitrd

From
https://build.opensuse.org/packag=
e/live_build_log/openSUSE:Factory:Staging:K/openssl-1_1/standard/x86_64
:

> [  248s] ../test/recipes/30-test_afalg.t        =
          (Wstat: 256 (exited 1) Tests: 1 Failed: 1)

Comparing /proc/modules in the build VM shows:
+algif_hash 12288 0 - Live 0x0000000000000000 (E)
+af_alg 36864 1 algif_hash, Live 0x0000000000000000 (E)

So apparently, algif_hash brings af_alg and that for some unknown reason br=
eaks
the test.

If I rm algif_hash from KERNEL_MODULES, it works again.

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

You are on the CC list for the bug.

=

--17186951113.Fc4F91.19323--


--17186951420.0A1BC4D.19332
Date: Tue, 18 Jun 2024 07:19: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=3D1226464

            Bug ID: 1226464
           Summary: AUDIT-0: aaa_base: sysctl.d/50-default.conf has new defaults
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

sysctl.d/50-default.conf in aaa_base has new defaults:

    Remove kernel.pid_max limit (bsc#1219038)

    kernel.pid_max is one of multiple mechanisms to restrict number of
    processes [1]. Its kernel default is scaled with nr_cpus but 1024
    tasks/cpu cap is too much if they were all running and it is also too
    little when they are idle (memory being bottleneck).

    Bump the limit to maximum kernel-accepted value and defer to other
    mechanisms for tasks limit enforcing.

    (This way we converge to same config like upstream systemd [2] but we
    ship distro defaults together from this package.)

    [1] https://www.suse.com/support/kb/doc/?id=3D000020429
    [2]
https://github.com/systemd/systemd/blob/72192b6cc9b856c10abc7f1e5f98240fde1=
7b8b4/sysctl.d/50-pid-max.conf
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17186951420.0A1BC4D.19332
Date: Tue, 18 Jun 2024 07:19: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
          1226464

          Summary
          AUDIT-0: aaa_base: sysctl.d/50-default.conf has new defaults

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          kukuk@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

sysctl.d/50-default.conf in aaa_base has new defaults:

    Remove kernel.pid_max limit (bsc#1219038)

    kernel.pid_max is one of multiple mechanisms to restrict number of
    processes [1]. Its kernel default is scaled with nr_cpus but 1024
    tasks/cpu cap is too much if they were all running and it is also too
    little when they are idle (memory being bottleneck).

    Bump the limit to maximum kernel-accepted value and defer to other
    mechanisms for tasks limit enforcing.

    (This way we converge to same config like upstream systemd [2] but we
    ship distro defaults together from this package.)

    [1] htt=
ps://www.suse.com/support/kb/doc/?id=3D000020429
    [2]
https://github.com/systemd/syste=
md/blob/72192b6cc9b856c10abc7f1e5f98240fde17b8b4/sysctl.d/50-pid-max.conf</=
a>

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

You are on the CC list for the bug.

=

--17186951420.0A1BC4D.19332--


--17187759872.A397F3EdD.21368
Date: Wed, 19 Jun 2024 05:46:27 +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=3D1226504

            Bug ID: 1226504
           Summary: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 126.0.6478.114
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: gmbr3-at-opensuse.org
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-des=
ktop_18.html

Stable Channel Update for Desktop
Tuesday, June 18, 2024

The Stable channel has been updated to 126.0.6478.114/115 for Windows, Mac =
and
126.0.6478.114 for Linux which will roll out over the coming days/weeks. A =
full
list of changes in this build is available in the Log.

Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majori=
ty
of users are updated with a fix. We will also retain restrictions if the bug
exists in a third party library that other projects similarly depend on, but
haven=E2=80=99t yet fixed.

This update includes 6 security fixes. Below, we highlight fixes that were
contributed by external researchers. Please see the Chrome Security Page for
more information.

High CVE-2024-6100: Type Confusion in V8.
High CVE-2024-6101: Inappropriate implementation in WebAssembly.
High CVE-2024-6102: Out of bounds memory access in Dawn.
High CVE-2024-6103: Use after free in Dawn.

We would also like to thank all security researchers that worked with us du=
ring
the development cycle to prevent security bugs from ever reaching the stable
channel.

As usual, our ongoing internal security work was responsible for a wide ran=
ge
of fixes:

Various fixes from internal audits, fuzzing and other initiatives

Many of our security bugs are detected using AddressSanitizer, MemorySaniti=
zer,
UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17187759872.A397F3EdD.21368
Date: Wed, 19 Jun 2024 05:46:27 +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
          1226504

          Summary
          VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities =
fixed in 126.0.6478.114

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          gmbr3@opensuse.org

          Reporter
          abergmann@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

https://chromereleases.googleblog.c=
om/2024/06/stable-channel-update-for-desktop_18.html

Stable Channel Update for Desktop
Tuesday, June 18, 2024

The Stable channel has been updated to 126.0.6478.114/115 for Windows, Mac =
and
126.0.6478.114 for Linux which will roll out over the coming days/weeks. A =
full
list of changes in this build is available in the Log.

Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majori=
ty
of users are updated with a fix. We will also retain restrictions if the bug
exists in a third party library that other projects similarly depend on, but
haven=E2=80=99t yet fixed.

This update includes 6 security fixes. Below, we highlight fixes that were
contributed by external researchers. Please see the Chrome Security Page for
more information.

High CVE-2024-6100: Type Confusion in V8.
High CVE-2024-6101: Inappropriate implementation in WebAssembly.
High CVE-2024-6102: Out of bounds memory access in Dawn.
High CVE-2024-6103: Use after free in Dawn.

We would also like to thank all security researchers that worked with us du=
ring
the development cycle to prevent security bugs from ever reaching the stable
channel.

As usual, our ongoing internal security work was responsible for a wide ran=
ge
of fixes:

Various fixes from internal audits, fuzzing and other initiatives

Many of our security bugs are detected using AddressSanitizer, MemorySaniti=
zer,
UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.

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

You are on the CC list for the bug.

=

--17187759872.A397F3EdD.21368--


body:
--17188288470.09ce.22753
Date: Wed, 19 Jun 2024 20:27:27 +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=3D1226541

            Bug ID: 1226541
           Summary: Cockpit Packagekit does not appear in UI
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Cockpit
          Assignee: Cockpit-bugs-at-suse.de
          Reporter: cody.henderson-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

After installing cockpit-packagekit the Software Updates tab did not appear.
After doing a little digging it appears to be caused by an incorrect path
listed in the manifest for the plugin.

In /usr/share/cockpit/packagekit/manifest.json it has the following conditi=
ons:

>    "conditions": [
>        {"path-exists": "/lib/systemd/system/packagekit.service"},
>        {"path-not-exists": "/sysroot/ostree"}
>    ],

The path /lib/systemd/system/packagekit.service does not exist with package=
kit
installed on the system. Instead it is located at
/usr/lib/systemd/system/packagekit.service. If I change that line to the
corrected path the Software Update tab then appears and seems to function j=
ust
fine.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17188288470.09ce.22753
Date: Wed, 19 Jun 2024 20:27:27 +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
          1226541

          Summary
          Cockpit Packagekit does not appear in UI

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Cockpit

          Assignee
          Cockpit-bugs@suse.de

          Reporter
          cody.henderson@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

After installing cockpit-packagekit the Software Updates tab=
 did not appear.
After doing a little digging it appears to be caused by an incorrect path
listed in the manifest for the plugin.

In /usr/share/cockpit/packagekit/manifest.json it has the following conditi=
ons:

>    "conditions": [
>        {"path-exists": "/lib/systemd/system/packagekit.=
service"},
>        {"path-not-exists": "/sysroot/ostree"}
>    ],

The path /lib/systemd/system/packagekit.service does not exist with package=
kit
installed on the system. Instead it is located at
/usr/lib/systemd/system/packagekit.service. If I change that line to the
corrected path the Software Update tab then appears and seems to function j=
ust
fine.

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

You are on the CC list for the bug.

=

--17188288470.09ce.22753--

pkgs: cockpit cockpit-podman


--17188808407.2b9f1F0.23560
Date: Thu, 20 Jun 2024 10:54:00 +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=3D1226586

            Bug ID: 1226586
           Summary: avahi-browse -a fails with "Invalid service type"
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: gnome-bugs-at-suse.de
          Reporter: martin.wilck-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

The following error occurs on multiple openSUSE systems, both 15.6 and Fact=
ory:

Error:

> avahi-browse -v -a
Server version: avahi 0.8; Host name: ares.local
E Ifce Prot Name                                          Type=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20
Domain
+   eth0 IPv4 connector-0=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
_spotify-connect._tcp local
+   eth0 IPv4 one-s-0=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
_spotify-connect._tcp local
: Cache exhausted
+   eth0 IPv4 Raumfeld-One-S-5aa49215a71dce5d5e3942e76961a1d1 _googlecast._=
tcp=20
   local
+   eth0 IPv4 Raumfeld-Connector-d40ebb7d92cef2980bd98614fc032254
_googlecast._tcp     local
+   eth0 IPv4 5aa49215-a71d-ce5d-5e39-42e76961a1d1          _googlezone._tc=
p=20=20=20
 local
+   eth0 IPv4 d40ebb7d-92ce-f298-0bd9-8614fc032254          _googlezone._tc=
p=20=20=20
 local
+   eth0 IPv4 192-168-1-4                                   Microsoft Windo=
ws
Network local
+   eth0 IPv4 fritz-box                                     Microsoft Windo=
ws
Network local
+   eth0 IPv4 PROXY                                         Microsoft Windo=
ws
Network local
+   eth0 IPv4 ANANAS                                        Microsoft Windo=
ws
Network local
+   eth0 IPv4 one-s                                         SFTP File Trans=
fer=20
 local
+   eth0 IPv4 connector                                     SFTP File Trans=
fer=20
 local
+   eth0 IPv4 2064991846AFDD81                              _matterd._udp=
=20=20=20=20=20=20
 local
+   eth0 IPv4 dahua1                                        Web Site=20=20=
=20=20=20=20=20=20=20=20=20
 local
+   eth0 IPv4 PROXY                                         Device Info=20=
=20=20=20=20=20=20=20
 local
+   eth0 IPv4 ANANAS                                        Device Info=20=
=20=20=20=20=20=20=20
 local
avahi_service_browser_new() failed: Invalid service type

> avahi-browse -v -a
Server version: avahi 0.8; Host name: ares.local
E Ifce Prot Name                                          Type=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20
Domain
avahi_service_browser_new() failed: Invalid service type

# Preliminary analysis via dbus monitor

The client makes an invalid ServiceBrowserNew() method call with empty serv=
ice
type parameter:

=E2=80=A3 Type=3Dmethod_call  Endian=3Dl  Flags=3D0  Version=3D1 Cookie=3D3=
1  Timestamp=3D"Thu
2024-06-20 10:05:32.977645 UTC"
  Sender=3D:1.657  Destination=3Dorg.freedesktop.Avahi  Path=3D/=20
Interface=3Dorg.freedesktop.Avahi.Server  Member=3DServiceBrowserNew
  UniqueName=3D:1.657
  MESSAGE "iissu" {
          INT32 -1;
          INT32 -1;
          STRING "";
          STRING "";
          UINT32 0;
  };

=E2=80=A3 Type=3Derror  Endian=3Dl  Flags=3D1  Version=3D1 Cookie=3D137  Re=
plyCookie=3D31=20
Timestamp=3D"Thu 2024-06-20 10:05:32.977975 UTC"
  Sender=3D:1.656  Destination=3D:1.657
  ErrorName=3Dorg.freedesktop.Avahi.InvalidServiceTypeError=20
ErrorMessage=3D"Invalid service type"
  UniqueName=3D:1.656
  MESSAGE "s" {
          STRING "Invalid service type";
  };

It appears that this service type has been previously passed from the daemo=
n to
the client via a DBus signal, either one of the following:

Type=3Dsignal  Endian=3Dl  Flags=3D1  Version=3D1 Cookie=3D133  Timestamp=
=3D"Thu 2024-06-20
10:05:32.976296 UTC"
  Sender=3D:1.656  Destination=3D:1.657  Path=3D/Client1/ServiceTypeBrowser=
1=20
Interface=3Dorg.freedesktop.Avahi.ServiceTypeBrowser  Member=3DItemNew
  UniqueName=3D:1.656
  MESSAGE "iissu" {
          INT32 2;
          INT32 0;
          STRING "";
          STRING "";
          UINT32 4;
  };

=E2=80=A3 Type=3Dsignal  Endian=3Dl  Flags=3D1  Version=3D1 Cookie=3D134  T=
imestamp=3D"Thu
2024-06-20 10:05:32.976485 UTC"
  Sender=3D:1.656  Destination=3D:1.657  Path=3D/Client1/ServiceTypeBrowser=
1=20
Interface=3Dorg.freedesktop.Avahi.ServiceTypeBrowser  Member=3DItemNew
  UniqueName=3D:1.656
  MESSAGE "iissu" {
          INT32 2;
          INT32 0;
          STRING "";
          STRING "local";
          UINT32 4;
  };
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17188808407.2b9f1F0.23560
Date: Thu, 20 Jun 2024 10:54:00 +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
          1226586

          Summary
          avahi-browse -a fails with "Invalid service type"

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          GNOME

          Assignee
          gnome-bugs@suse.de

          Reporter
          martin.wilck@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

The following error occurs on multiple openSUSE systems, bot=
h 15.6 and Factory:

Error:

> avahi-browse -v -a
Server version: avahi 0.8; Host name: ares.local
E Ifce Prot Name                                          Type=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20
Domain
+   eth0 IPv4 connector-0=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
_spotify-connect._tcp local
+   eth0 IPv4 one-s-0=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
_spotify-connect._tcp local
: Cache exhausted
+   eth0 IPv4 Raumfeld-One-S-5aa49215a71dce5d5e3942e76961a1d1 _googlecast._=
tcp=20
   local
+   eth0 IPv4 Raumfeld-Connector-d40ebb7d92cef2980bd98614fc032254
_googlecast._tcp     local
+   eth0 IPv4 5aa49215-a71d-ce5d-5e39-42e76961a1d1          _googlezone._tc=
p=20=20=20
 local
+   eth0 IPv4 d40ebb7d-92ce-f298-0bd9-8614fc032254          _googlezone._tc=
p=20=20=20
 local
+   eth0 IPv4 192-168-1-4                                   Microsoft Windo=
ws
Network local
+   eth0 IPv4 fritz-box                                     Microsoft Windo=
ws
Network local
+   eth0 IPv4 PROXY                                         Microsoft Windo=
ws
Network local
+   eth0 IPv4 ANANAS                                        Microsoft Windo=
ws
Network local
+   eth0 IPv4 one-s                                         SFTP File Trans=
fer=20
 local
+   eth0 IPv4 connector                                     SFTP File Trans=
fer=20
 local
+   eth0 IPv4 2064991846AFDD81                              _matterd._udp=
=20=20=20=20=20=20
 local
+   eth0 IPv4 dahua1                                        Web Site=20=20=
=20=20=20=20=20=20=20=20=20
 local
+   eth0 IPv4 PROXY                                         Device Info=20=
=20=20=20=20=20=20=20
 local
+   eth0 IPv4 ANANAS                                        Device Info=20=
=20=20=20=20=20=20=20
 local
avahi_service_browser_new() failed: Invalid service type

> avahi-browse -v -a
Server version: avahi 0.8; Host name: ares.local
E Ifce Prot Name                                          Type=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20
Domain
avahi_service_browser_new() failed: Invalid service type

# Preliminary analysis via dbus monitor

The client makes an invalid ServiceBrowserNew() method call with empty serv=
ice
type parameter:

=E2=80=A3 Type=3Dmethod_call  Endian=3Dl  Flags=3D0  Version=3D1 Cookie=3D3=
1  Timestamp=3D"Thu
2024-06-20 10:05:32.977645 UTC"
  Sender=3D:1.657  Destination=3Dorg.freedesktop.Avahi  Path=3D/=20
Interface=3Dorg.freedesktop.Avahi.Server  Member=3DServiceBrowserNew
  UniqueName=3D:1.657
  MESSAGE "iissu" {
          INT32 -1;
          INT32 -1;
          STRING "";
          STRING "";
          UINT32 0;
  };

=E2=80=A3 Type=3Derror  Endian=3Dl  Flags=3D1  Version=3D1 Cookie=3D137  Re=
plyCookie=3D31=20
Timestamp=3D"Thu 2024-06-20 10:05:32.977975 UTC"
  Sender=3D:1.656  Destination=3D:1.657
  ErrorName=3Dorg.freedesktop.Avahi.InvalidServiceTypeError=20
ErrorMessage=3D"Invalid service type"
  UniqueName=3D:1.656
  MESSAGE "s" {
          STRING "Invalid service type";
  };

It appears that this service type has been previously passed from the daemo=
n to
the client via a DBus signal, either one of the following:

Type=3Dsignal  Endian=3Dl  Flags=3D1  Version=3D1 Cookie=3D133  Timestamp=
=3D"Thu 2024-06-20
10:05:32.976296 UTC"
  Sender=3D:1.656  Destination=3D:1.657  Path=3D/Client1/ServiceTypeBrowser=
1=20
Interface=3Dorg.freedesktop.Avahi.ServiceTypeBrowser  Member=3DItemNew
  UniqueName=3D:1.656
  MESSAGE "iissu" {
          INT32 2;
          INT32 0;
          STRING "";
          STRING "";
          UINT32 4;
  };

=E2=80=A3 Type=3Dsignal  Endian=3Dl  Flags=3D1  Version=3D1 Cookie=3D134  T=
imestamp=3D"Thu
2024-06-20 10:05:32.976485 UTC"
  Sender=3D:1.656  Destination=3D:1.657  Path=3D/Client1/ServiceTypeBrowser=
1=20
Interface=3Dorg.freedesktop.Avahi.ServiceTypeBrowser  Member=3DItemNew
  UniqueName=3D:1.656
  MESSAGE "iissu" {
          INT32 2;
          INT32 0;
          STRING "";
          STRING "local";
          UINT32 4;
  };

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

You are on the CC list for the bug.

=

--17188808407.2b9f1F0.23560--


--17189204211.fb09e9Dc.25870
Date: Thu, 20 Jun 2024 21:53:41 +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=3D1226664

            Bug ID: 1226664
           Summary: Wicked crashing with macvlan interface since recent `zypper patch` in systemd-nspawn container
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: georg.jansing-at-web.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 875621
  --> https://bugzilla.suse.com/attachment.cgi?id=3D875621&action=3Dedit
Script to create a container that crashes wicked

I have a `systemd-nspawn` based container to separate a proprietary device =
from
the rest of the house network.

This container is installed with a quite minimal openSUSE installation
(initially with Leap 15.4, upgraded to 15.5).

Since a `zypper patch` this week the `wicked` service fails to start and
`wicked ifup [...]` commands segfault.

Both upgrading to Leap 15.6 and reinstalling the container cleanly does not
solve the issue.

I tracked the problem down to the container sharing its outbound network
interface with the server via MACVLAN. After switching to IPVLAN or removing
the interface, wicked is stable again.

I attached a script, that generates a very minimal container (can do both 1=
5.6
and 15.5), that reproduces the error for me.

Trying to get a back trace (as in the last paragraph of
https://en.opensuse.org/openSUSE:Bugreport_wicked) did not succeed. I did n=
ot
find the path to the core dump.

I could attach a gdb to wicked and got it to crash (also documented in the
script) with the message:
```
Program received signal SIGSEGV, Segmentation faultwarning: could not conve=
rt
'si_code' from the host encoding (ANSI_X3.4-1968) to UTF-32.
This normally should not happen, please file a bug report.
```
Then it complains about a lot of missing debuginfo packages, which I could =
not
install. Maybe I need an additional repo?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17189204211.fb09e9Dc.25870
Date: Thu, 20 Jun 2024 21:53:41 +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
          1226664

          Summary
          Wicked crashing with macvlan interface since recent `zypper p=
atch` in systemd-nspawn container

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          georg.jansing@web.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 875621 [=
details]
Script to create a container that crashes wicked

I have a `systemd-nspawn` based container to separate a proprietary device =
from
the rest of the house network.

This container is installed with a quite minimal openSUSE installation
(initially with Leap 15.4, upgraded to 15.5).

Since a `zypper patch` this week the `wicked` service fails to start and
`wicked ifup [...]` commands segfault.

Both upgrading to Leap 15.6 and reinstalling the container cleanly does not
solve the issue.

I tracked the problem down to the container sharing its outbound network
interface with the server via MACVLAN. After switching to IPVLAN or removing
the interface, wicked is stable again.

I attached a script, that generates a very minimal container (can do both 1=
5.6
and 15.5), that reproduces the error for me.

Trying to get a back trace (as in the last paragraph of
https://en.op=
ensuse.org/openSUSE:Bugreport_wicked) did not succeed. I did not
find the path to the core dump.

I could attach a gdb to wicked and got it to crash (also documented in the
script) with the message:
```
Program received signal SIGSEGV, Segmentation faultwarning: could not conve=
rt
'si_code' from the host encoding (ANSI_X3.4-1968) to UTF-32.
This normally should not happen, please file a bug report.
```
Then it complains about a lot of missing debuginfo packages, which I could =
not
install. Maybe I need an additional repo?

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

You are on the CC list for the bug.

=

--17189204211.fb09e9Dc.25870--


--17189552371.30CfB811C.149
Date: Fri, 21 Jun 2024 07:33: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=3D1226676

            Bug ID: 1226676
           Summary: Installation: kdump reports an error if systemd-boot has been selected for bootloader
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Installation
          Assignee: yast2-maintainers-at-suse.de
          Reporter: schubi-at-suse.com
        QA Contact: jsrain-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 875628
  --> https://bugzilla.suse.com/attachment.cgi?id=3D875628&action=3Dedit
y2log

YaST reports an error that the call of mkdumprd has been failed.

Calling mkdumprd manually returns:

/usr/lib/kdump/kdump-read-config.sh: line 144: /etc/sysconfig/kdump: No such
file or directory
Kernel not found.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17189552371.30CfB811C.149
Date: Fri, 21 Jun 2024 07:33: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
          1226676

          Summary
          Installation: kdump reports an error if systemd-boot has been=
 selected for bootloader

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Installation

          Assignee
          yast2-maintainers@suse.de

          Reporter
          schubi@suse.com

          QA Contact
          jsrain@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 875628 [details]
y2log

YaST reports an error that the call of mkdumprd has been failed.

Calling mkdumprd manually returns:

/usr/lib/kdump/kdump-read-config.sh: line 144: /etc/sysconfig/kdump: No such
file or directory
Kernel not found.

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

You are on the CC list for the bug.

=

--17189552371.30CfB811C.149--


--17189653791.a725f1a.683
Date: Fri, 21 Jun 2024 10:22:59 +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=3D1226725

            Bug ID: 1226725
           Summary: [Build 20240617] openQA test fails in bootloader_s390 - color change in Installer UI
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: S/390-64
               URL: https://openqa.opensuse.org/tests/4288524/modules/boot
                    loader_s390/steps/59
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: gfx-bugs-at-suse.de
          Reporter: mgriessmeier-at-suse.com
        QA Contact: gfx-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

## Observation

The Color of the YaST Installer Welcome screen changed from Build 20240614 =
to
20240617 on s390x

>From the changelog, the most promising candidates of causing this:
>  Mesa (24.0.9 -> 24.1.0)
>  Mesa-drivers (24.0.9 -> 24.1.0)

see attached screenshots for reference

openQA test in scenario
opensuse-Tumbleweed-DVD-s390x-textmode-server@s390x-zVM-vswitch-l2 fails in
[bootloader_s390](https://openqa.opensuse.org/tests/4288524/modules/bootloa=
der_s390/steps/59)

## Test suite description
The base test suite is used for job templates defined in YAML documents. It=
 has
no settings of its own.

## Reproducible

Fails since (at least) Build
[20240606](https://openqa.opensuse.org/tests/4255925)

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=3Ds390x&distri=3Dope=
nsuse&flavor=3DDVD&machine=3Ds390x-zVM-vswitch-l2&test=3Dtextmode-server&ve=
rsion=3DTumbleweed)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17189653791.a725f1a.683
Date: Fri, 21 Jun 2024 10:22:59 +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
          1226725

          Summary
          [Build 20240617] openQA test fails in bootloader_s390 - color=
 change in Installer UI

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          S/390-64

          URL
          https://openqa.opensuse.org/tests/4288524/modules/bootloader_=
s390/steps/59

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X.Org

          Assignee
          gfx-bugs@suse.de

          Reporter
          mgriessmeier@suse.com

          QA Contact
          gfx-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

## Observation

The Color of the YaST Installer Welcome screen changed from Build 20240614 =
to
20240617 on s390x

>From the changelog, the most promising candidates of causing this:
>  Mesa (24.0.9 -> 24.1.0)
>  Mesa-drivers (24.0.9 -> 24.1.0)

see attached screenshots for reference

openQA test in scenario
opensuse-Tumbleweed-DVD-s390x-textmode-server@s390x-zVM-vswitch-l2 fail=
s in
[bootloader_s390](https://openqa.opensuse.org/tests/4288524/mod=
ules/bootloader_s390/steps/59)

## Test suite description
The base test suite is used for job templates defined in YAML documents. It=
 has
no settings of its own.

## Reproducible

Fails since (at least) Build
[20240606](https://op=
enqa.opensuse.org/tests/4255925)

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.=
org/tests/latest?arch=3Ds390x&distri=3Dopensuse&flavor=3DDVD&ma=
chine=3Ds390x-zVM-vswitch-l2&test=3Dtextmode-server&version=3DTumbl=
eweed)

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

You are on the CC list for the bug.

=

--17189653791.a725f1a.683--


--17189658580.7A8f.707
Date: Fri, 21 Jun 2024 10:30:58 +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=3D1226727

            Bug ID: 1226727
           Summary: can't install micro os on SoC missing grub2-i386-efi
    Classification: openSUSE
           Product: openSUSE Leap Micro
           Version: 5.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Installation
          Assignee: yast2-maintainers-at-suse.de
          Reporter: opensuseidp@ikol.8shield.net
        QA Contact: jalausuch-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I can't install micro os on SoC.

The installer says it's missing grub2-i386-efi and only find grub2-i386-pc
seems to be available.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17189658580.7A8f.707
Date: Fri, 21 Jun 2024 10:30:58 +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
          1226727

          Summary
          can't install micro os on SoC missing grub2-i386-efi

          Classification
          openSUSE

          Product
          openSUSE Leap Micro

          Version
          5.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Installation

          Assignee
          yast2-maintainers@suse.de

          Reporter
          opensuseidp@ikol.8shield.net

          QA Contact
          jalausuch@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I can't install micro os on SoC.

The installer says it's missing grub2-i386-efi and only find grub2-i386-pc
seems to be available.

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

You are on the CC list for the bug.

=

--17189658580.7A8f.707--


body:
--17189736168.c418e7.1124
Date: Fri, 21 Jun 2024 12:40:16 +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=3D1226763

            Bug ID: 1226763
           Summary: Missing non-oss source repo for aarch64
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Patterns
          Assignee: dimstar-at-opensuse.org
          Reporter: lubos.kocman-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

We have a source repo for non-oss  ports on s390x and ppc but not on arm
we can either add it for Arm, or drop it for others

guillaume_g
As it exists for x86_64, I guess we should publish it for :ARM as well
https://download.opensuse.org/source/tumbleweed/repo/non-oss/

(using patterns component so it ends on rel-eng)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17189736168.c418e7.1124
Date: Fri, 21 Jun 2024 12:40:16 +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
          1226763

          Summary
          Missing non-oss source repo for aarch64

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          aarch64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Patterns

          Assignee
          dimstar@opensuse.org

          Reporter
          lubos.kocman@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

We have a source repo for non-oss  ports on s390x and ppc bu=
t not on arm
we can either add it for Arm, or drop it for others

guillaume_g
As it exists for x86_64, I guess we should publish it for :ARM as well
h=
ttps://download.opensuse.org/source/tumbleweed/repo/non-oss/

(using patterns component so it ends on rel-eng)

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

You are on the CC list for the bug.

=

--17189736168.c418e7.1124--

summary: Missing non-oss source repo for aarch64


--17191610192.65848E.2720
Date: Sun, 23 Jun 2024 16:43: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=3D1226826

            Bug ID: 1226826
           Summary: python-rebulk too old for python-guessit
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: aloisio-at-gmx.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

pkg_resources.ContextualVersionConflict: (rebulk 3.1.0
(/usr/lib/python3.6/site-packages), Requirement.parse('rebulk>=3D3.2.0'),
{'guessit'})
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17191610192.65848E.2720
Date: Sun, 23 Jun 2024 16:43: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
          1226826

          Summary
          python-rebulk too old for python-guessit

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          aloisio@gmx.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

pkg_resources.ContextualVersionConflict: (rebulk 3.1.0
(/usr/lib/python3.6/site-packages), Requirement.parse('rebulk>=3D3.2.0'),
{'guessit'})

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

You are on the CC list for the bug.

=

--17191610192.65848E.2720--


body:
Gecko/20100101
Firefox/127.0
Build Identifier:=20

Run gzdoom without arguments or with any normal arguments as I normally wou=
ld,
e.g. 'gzdoom -iwad ~/doom/DOOM2.WAD -skill 3 -file Utopia.wad -record Utopi=
a'.

Reproducible: Always

Steps to Reproduce:
1. gzdoom
Actual Results:=20=20

*** Fatal Error ***
!!! Failed to exec debug process
zsh: segmentation fault (core dumped)  gzdoom

% gdb /usr/bin/gzdoom gzdoom-16267-1719180269.core
(gdb) bt
#0  0x00007fcaba0949dc in __pthread_kill_implementation () at /lib64/libc.s=
o.6
#1  0x00007fcaba041176 in raise () at /lib64/libc.so.6
#2  0x000055fafe140ca7 in crash_catcher (signum=3D11, siginfo=3D<optimiz=
ed out>,
context=3D<optimized out>)
    at
/usr/src/debug/gzdoom-g4.12.2/src/common/platform/posix/sdl/crashcatcher.c:=
254
#3  0x00007fcaba041240 in <signal handler called> () at /lib64/libc.s=
o.6
#4  0x00007fcaba17ff6c in __strlen_evex () at /lib64/libc.so.6
#5  0x00007fcaba0643e1 in __printf_buffer () at /lib64/libc.so.6
#6  0x00007fcaba0649f9 in __vfprintf_internal () at /lib64/libc.so.6
#7  0x00007fcaba059ecf in printf () at /lib64/libc.so.6
#8  0x000055fafe118899 in main (argc=3D1, argv=3D0x7ffcaeb7df68) at
/usr/src/debug/gzdoom-g4.12.2/src/common/platform/posix/sdl/i_main.cpp:158
(gdb) frame 8
#8  0x000055fafe118899 in main (argc=3D1, argv=3D0x7ffcaeb7df68) at
/usr/src/debug/gzdoom-g4.12.2/src/common/platform/posix/sdl/i_main.cpp:158
158             printf(GAMENAME" %s - %s - SDL version\nCompiled on %s=
\n",

Expected Results:=20=20
gzdoom runs

% rpm -qi gzdoom
Name        : gzdoom
Version     : 4.12.2
Release     : 3.1
Architecture: x86_64
Install Date: Mon Jun  3 18:40:25 2024
Group       : Amusements/Games/3D/Shoot
Size        : 28312984
License     : GPL-3.0-only
Signature   : RSA/SHA512, Mon May 27 05:09:27 2024, Key ID 35a2f86e29b700a4
Source RPM  : gzdoom-4.12.2-3.1.src.rpm
Build Date  : Fri May 17 17:04:47 2024
Build Host  : reproducible
Packager    : https://bugs.opensuse.o=
rg
Vendor      : openSUSE
URL         : https://zdoom.org/
Summary     : A DOOM source port with graphic and modding extensions
Description :
GZDoom is a port (a modification) of the original Doom source code, featuri=
ng:
* an OpenGL renderer, HQnX/xBRZ rescaling, 3D floor and model support
* Truecolor software rendering, extending the classic 8-bit palette
* Heretic, Hexen and Strife game modes and support for a lot of
  additional IWADs.
* Boom and Hexen map extension support, scriptability with ACS and
  ZScript, and various modding features regarding actors and scenery.
* Demo record/playback of classic and Boom demos is not supported.
Distribution: openSUSE Tumbleweed

% rpm -qi openSUSE-release
Name        : openSUSE-release
Version     : 20240621
Release     : 2966.1
Architecture: x86_64
Install Date: Sat Jun 22 09:32:45 2024

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

You are on the CC list for the bug.

=

--17191810040.52aD1.2783--

summary: gzdoom segmentation fault


--17192233141.aa81CDB2E.3332
Date: Mon, 24 Jun 2024 10:01:54 +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=3D1226850

            Bug ID: 1226850
           Summary: Useradd doesn't create a group under the same name despite not using the -N flag
    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: alice.brooks-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

So I've downloaded the latest Tumbleweed image (20240621) and ran it inside=
 a
vm, however any user that's created is no longer created with a matching na=
med
group, this includes ones from the initial installer and any new ones creat=
ed
via useradd

You can recreate this either by running through the installer as mentioned
above, or something like below:

```
sudo useradd -m test=20
cat /etc/group | grep test
```

Prints out nothing, as the group test was never created
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17192233141.aa81CDB2E.3332
Date: Mon, 24 Jun 2024 10:01:54 +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
          1226850

          Summary
          Useradd doesn't create a group under the same name despite no=
t using the -N flag

          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
          alice.brooks@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

So I've downloaded the latest Tumbleweed image (20240621) an=
d ran it inside a
vm, however any user that's created is no longer created with a matching na=
med
group, this includes ones from the initial installer and any new ones creat=
ed
via useradd

You can recreate this either by running through the installer as mentioned
above, or something like below:

```
sudo useradd -m test=20
cat /etc/group | grep test
```

Prints out nothing, as the group test was never created

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

You are on the CC list for the bug.

=

--17192233141.aa81CDB2E.3332--


--17192961494.3eDD3a.5027
Date: Tue, 25 Jun 2024 06:15:49 +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=3D1226933

            Bug ID: 1226933
           Summary: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 126.0.6478.126
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: gmbr3-at-opensuse.org
          Reporter: rfrohl-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: Andreas.Stieger-at-gmx.de, m.szczepaniak.000-at-gmail.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

The Stable channel has been updated to 126.0.6478.126/127 for Windows, Mac =
and
126.0.6478.126 for Linux which will roll out over the coming days/weeks.

- CVE-2024-6290: Use after free in Dawn. Reported by wgslfuzz on 2024-05-23
- CVE-2024-6291: Use after free in Swiftshader. Reported by Cassidy
Kim(@cassidy6564) on 2023-11-15
- CVE-2024-6292: Use after free in Dawn. Reported by wgslfuzz on 2024-05-24
- CVE-2024-6293: Use after free in Dawn. Reported by wgslfuzz on 2024-06-09

https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-des=
ktop_24.html
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17192961494.3eDD3a.5027
Date: Tue, 25 Jun 2024 06:15:49 +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
          1226933

          Summary
          VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities =
fixed in 126.0.6478.126

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          gmbr3@opensuse.org

          Reporter
          rfrohl@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          Andreas.Stieger@gmx.de, m.szczepaniak.000@gmail.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

The Stable channel has been updated to 126.0.6478.126/127 fo=
r Windows, Mac and
126.0.6478.126 for Linux which will roll out over the coming days/weeks.

- CVE-2024-6290: Use after free in Dawn. Reported by wgslfuzz on 2024-05-23
- CVE-2024-6291: Use after free in Swiftshader. Reported by Cassidy
Kim(@cassidy6564) on 2023-11-15
- CVE-2024-6292: Use after free in Dawn. Reported by wgslfuzz on 2024-05-24
- CVE-2024-6293: Use after free in Dawn. Reported by wgslfuzz on 2024-06-09

https://chromereleases.googleblog.com/2024/06/stab=
le-channel-update-for-desktop_24.html

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

You are on the CC list for the bug.

=

--17192961494.3eDD3a.5027--


--17194118592.28E8B.16747
Date: Wed, 26 Jun 2024 14:24:19 +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=3D1227092

            Bug ID: 1227092
           Summary: network/boinc-client: Add WorkingDirectory=3D to unit file (and other possible unit file enhancements)
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: All
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: 3rd party software
          Assignee: chris-at-computersalat.de
          Reporter: timuzhti-at-gmail.com
        QA Contact: screening-team-bugs-at-suse.de
                CC: Sascha.Manns-at-outlook.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

This is a pretty minor issue but without WorkingDirectory=3D set, the ExecS=
top=3D
command (/usr/bin/boinccmd --quit) does not actually function because it ca=
n't
find the gui_rpc_auth.cfg file. This causes the unit to report failure every
time it's stopped.

According to documentation, boinccmd checks three places for the password (=
it
doesn't have a --datadir option). Changing the working directory to either
/var/lib/boinc or ~ (which is the same thing by default) seems to be the
easiest way to resolve this, since /etc/boinc-client/ and /var/lib/boinc-cl=
ient
are not used by default.

I'm not really sure which of the two options would be better. Using the home
directory of the boinc user would probably make it easier to reconfigure to
another directory, but I'm not sure that's worth it. It might be even bette=
r to
somehow pull $BOINC_BOINC_DIR into WorkingDirectory=3D but systemd doesn't =
seem
to support this.

Another quirk uncovered looking at the logs is that systemd apparently
interprets /lockfile as part of the variable name, sample log message as
follows:

(rm): boinc-client.service: Invalid environment variable name evaluates to =
an
empty string: BOINC_BOINC_DIR/lockfile

This can be avoided by wrapping the variable name in braces,
ExecStopPost=3D/bin/rm -f ${BOINC_BOINC_DIR}/lockfile though I'm not sure i=
f this
is actually a systemd issue.

Finally, the upstream unit file at
https://github.com/BOINC/boinc/blob/master/client/scripts/boinc-client.serv=
ice.in
includes a couple of systemd hardening options. Some of these are off by
default because Atlas requires setuid root, but the three options limiting =
the
read/write access of the unit to the boinc directory only might be worthwhi=
le.

ProtectSystem=3Dfull
ProtectControlGroups=3Dtrue
ReadWritePaths=3D-/var/lib/boinc -/etc/boinc-client
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17194118592.28E8B.16747
Date: Wed, 26 Jun 2024 14:24:19 +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
          1227092

          Summary
          network/boinc-client: Add WorkingDirectory=3D to unit file (a=
nd other possible unit file enhancements)

          Classification
          openSUSE

          Product
          openSUSE.org

          Version
          unspecified

          Hardware
          All

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Enhancement

          Priority
          P5 - None

          Component
          3rd party software

          Assignee
          chris@computersalat.de

          Reporter
          timuzhti@gmail.com

          QA Contact
          screening-team-bugs@suse.de

          CC
          Sascha.Manns@outlook.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

This is a pretty minor issue but without WorkingDirectory=3D=
 set, the ExecStop=3D
command (/usr/bin/boinccmd --quit) does not actually function because it ca=
n't
find the gui_rpc_auth.cfg file. This causes the unit to report failure every
time it's stopped.

According to documentation, boinccmd checks three places for the password (=
it
doesn't have a --datadir option). Changing the working directory to either
/var/lib/boinc or ~ (which is the same thing by default) seems to be the
easiest way to resolve this, since /etc/boinc-client/ and /var/lib/boinc-cl=
ient
are not used by default.

I'm not really sure which of the two options would be better. Using the home
directory of the boinc user would probably make it easier to reconfigure to
another directory, but I'm not sure that's worth it. It might be even bette=
r to
somehow pull $BOINC_BOINC_DIR into WorkingDirectory=3D but systemd doesn't =
seem
to support this.

Another quirk uncovered looking at the logs is that systemd apparently
interprets /lockfile as part of the variable name, sample log message as
follows:

(rm): boinc-client.service: Invalid environment variable name evaluates to =
an
empty string: BOINC_BOINC_DIR/lockfile

This can be avoided by wrapping the variable name in braces,
ExecStopPost=3D/bin/rm -f ${BOINC_BOINC_DIR}/lockfile though I'm not sure i=
f this
is actually a systemd issue.

Finally, the upstream unit file at
https://github.com/BOINC/boinc/blob/master/client/script=
s/boinc-client.service.in
includes a couple of systemd hardening options. Some of these are off by
default because Atlas requires setuid root, but the three options limiting =
the
read/write access of the unit to the boinc directory only might be worthwhi=
le.

ProtectSystem=3Dfull
ProtectControlGroups=3Dtrue
ReadWritePaths=3D-/var/lib/boinc -/etc/boinc-client

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

You are on the CC list for the bug.

=

--17194118592.28E8B.16747--


body:
--17194748311.26cE3.80
Date: Thu, 27 Jun 2024 07:53:51 +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=3D1227116

            Bug ID: 1227116
           Summary: osinfo still uses deprecated SL-Micro name
    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: felix.niederwanger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

The osinfo-query os programm still uses the deprecated SL-Micro nomenclature

> osinfo-query os | grep -i slm6
>  slm6.0               | SUSE Linux Micro 6.0                             =
  | 6.0      | http://suse.com/slm/6.0=20

This affects then also applications like virt-manager. Since the name of
SL-Micro 6.0 has been renamed back to SLEM 6.0, this should also display it
similar to previous SLEM versions:

>  slem5.0              | SUSE Linux Enterprise Micro                      =
  | 5.0      | http://suse.com/slem/5.0=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
>  slem5.1              | SUSE Linux Enterprise Micro 5.1                  =
  | 5.1      | http://suse.com/slem/5.1=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
>  slem5.2              | SUSE Linux Enterprise Micro 5.2                  =
  | 5.2      | http://suse.com/slem/5.2=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
>  slem5.3              | SUSE Linux Enterprise Micro 5.3                  =
  | 5.3      | http://suse.com/slem/5.3=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
>  slem5.4              | SUSE Linux Enterprise Micro 5.4                  =
  | 5.4      | http://suse.com/slem/5.4=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
>  slem5.5              | SUSE Linux Enterprise Micro 5.5                  =
  | 5.5      | http://suse.com/slem/5.5=20

Here it should be listed als `slem6.0`.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17194748311.26cE3.80
Date: Thu, 27 Jun 2024 07:53:51 +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
          1227116

          Summary
          osinfo still uses deprecated SL-Micro name

          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
          felix.niederwanger@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

The osinfo-query os programm still uses the deprecated SL-Mi=
cro nomenclature

> osinfo-query os | grep -i slm6
>  slm6.0               | SUSE Linux Micro 6.0                          =
     | 6.0      | http://suse.com/slm/6=
.0

This affects then also applications like virt-manager. Since the name of
SL-Micro 6.0 has been renamed back to SLEM 6.0, this should also display it
similar to previous SLEM versions:

>  slem5.0              | SUSE Linux Enterprise Mi=
cro                        | 5.0      | http://suse.com/slem/5.0=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20
>  slem5.1              | SUSE Linux Enterprise Micro 5.1               =
     | 5.1      | http://suse.com/slem=
/5.1=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>  slem5.2              | SUSE Linux Enterprise Micro 5.2               =
     | 5.2      | http://suse.com/slem=
/5.2=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>  slem5.3              | SUSE Linux Enterprise Micro 5.3               =
     | 5.3      | http://suse.com/slem=
/5.3=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>  slem5.4              | SUSE Linux Enterprise Micro 5.4               =
     | 5.4      | http://suse.com/slem=
/5.4=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
>  slem5.5              | SUSE Linux Enterprise Micro 5.5               =
     | 5.5      | http://suse.com/slem=
/5.5

Here it should be listed als `slem6.0`.

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

You are on the CC list for the bug.

=

--17194748311.26cE3.80--

pkgs: osinfo-db virt-manager


--17194753441.6bAA2.104
Date: Thu, 27 Jun 2024 08:02:24 +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=3D1227117

            Bug ID: 1227117
           Summary: systemd-sysctl[189]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: armv7
               URL: https://openqa.opensuse.org/tests/4302790/modules/jour
                    nal_check/steps/11
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

## Observation

openQA test in scenario
opensuse-Tumbleweed-JeOS-for-AArch64-arm-jeos@aarch32-HD20G fails in
[journal_check](https://openqa.opensuse.org/tests/4302790/modules/journal_c=
heck/steps/11)

On armv7 (32-bit arm) we have the following problem since snapshot 20240625
(20240624 was fine):
**********
systemd-sysctl[189]: Couldn't write '4194304' to 'kernel/pid_max': Invalid
argument
**********

## Test suite description
Maintainer: fvogt, mnowak

Start JeOS from the HDD image, configure it using the firstboot wizard and =
then
run basic tests. console=3Dtty0 added as needed for aarch64.

## Reproducible

Fails since (at least) Build
[20240625](https://openqa.opensuse.org/tests/4301144)

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=3Darm&distri=3Dopens=
use&flavor=3DJeOS-for-AArch64&machine=3Daarch32-HD20G&test=3Djeos&version=
=3DTumbleweed)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17194753441.6bAA2.104
Date: Thu, 27 Jun 2024 08:02:24 +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
          1227117

          Summary
          systemd-sysctl[189]: Couldn't write '4194304' to 'kernel/pid_=
max': Invalid argument

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          armv7

          URL
          https://openqa.opensuse.org/tests/4302790/modules/journal_che=
ck/steps/11

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          guillaume.gardet@arm.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

## Observation

openQA test in scenario
opensuse-Tumbleweed-JeOS-for-AArch64-arm-jeos@aarch32-HD20G fails in
[journal_check](https://openqa.opensuse.org/tests/4302790/modules=
/journal_check/steps/11)

On armv7 (32-bit arm) we have the following problem since snapshot 20240625
(20240624 was fine):
**********
systemd-sysctl[189]: Couldn't write '4194304' to 'kernel/pid_max': Invalid
argument
**********

## Test suite description
Maintainer: fvogt, mnowak

Start JeOS from the HDD image, configure it using the firstboot wizard and =
then
run basic tests. console=3Dtty0 added as needed for aarch64.

## Reproducible

Fails since (at least) Build
[20240625](https://op=
enqa.opensuse.org/tests/4301144)

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tes=
ts/latest?arch=3Darm&distri=3Dopensuse&flavor=3DJeOS-for-AArch64&am=
p;machine=3Daarch32-HD20G&test=3Djeos&version=3DTumbleweed)</pr=
e>

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

You are on the CC list for the bug.

=

--17194753441.6bAA2.104--


--17195722750.d2d7.2252
Date: Fri, 28 Jun 2024 10:57:55 +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=3D1227158

            Bug ID: 1227158
           Summary: VUL-0: CVE-2024-24792: app-builder: golang.org/x/image/tiff: parsing of a corrupt or malicious image with invalid color indices can cause a panic
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/412299/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: brunopitrus-at-hotmail.com
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: camila.matos-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

Parsing a corrupt or malicious image with invalid color indices can cause a
panic.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-24792
https://www.cve.org/CVERecord?id=3DCVE-2024-24792
https://go.dev/cl/588115
https://go.dev/issue/67624
https://pkg.go.dev/vuln/GO-2024-2937
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17195722750.d2d7.2252
Date: Fri, 28 Jun 2024 10:57:55 +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
          1227158

          Summary
          VUL-0: CVE-2024-24792: app-builder: golang.org/x/image/tiff: =
parsing of a corrupt or malicious image with invalid color indices can caus=
e a panic

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          brunopitrus@hotmail.com

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          camila.matos@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

Parsing a corrupt or malicious image with invalid color indi=
ces can cause a
panic.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-24792
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-24792
https://go.dev/cl/588115
https://go.dev/issue/67624
https://pkg.go.dev/vuln/GO=
-2024-2937

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

You are on the CC list for the bug.

=

--17195722750.d2d7.2252--


--17195783262.cbBDe.2471
Date: Fri, 28 Jun 2024 12:38:46 +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=3D1227174

            Bug ID: 1227174
           Summary: VUL-0: CVE-2024-39705: python-nltk: remote code execution through the integrated data package download functionality
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/412359/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: python-maintainers-at-suse.com
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: camila.matos-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

NLTK through 3.8.1 allows remote code execution if untrusted packages have
pickled Python code, and the integrated data package download functionality=
 is
used. This affects, for example, averaged_perceptron_tagger and punkt.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-39705
https://www.cve.org/CVERecord?id=3DCVE-2024-39705
https://github.com/nltk/nltk/issues/2522
https://github.com/nltk/nltk/issues/3266
https://bugzilla.redhat.com/show_bug.cgi?id=3D2294671
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17195783262.cbBDe.2471
Date: Fri, 28 Jun 2024 12:38:46 +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
          1227174

          Summary
          VUL-0: CVE-2024-39705: python-nltk: remote code execution thr=
ough the integrated data package download functionality

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          python-maintainers@suse.com

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          camila.matos@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

NLTK through 3.8.1 allows remote code execution if untrusted=
 packages have
pickled Python code, and the integrated data package download functionality=
 is
used. This affects, for example, averaged_perceptron_tagger and punkt.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-39705
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-39705
https://github.com/nlt=
k/nltk/issues/2522
https://github.com/nlt=
k/nltk/issues/3266
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2294671

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

You are on the CC list for the bug.

=

--17195783262.cbBDe.2471--


--17197488082.f8DA6aA8.347
Date: Sun, 30 Jun 2024 12:00:08 +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=3D1227208

            Bug ID: 1227208
           Summary: wdmd.service: Service has more than one ExecStart=3D setting
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: opensuse-at-mike.franken.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

With Tumbleweed snapshot 20240627 I get:

systemd[1]: wdmd.service: Service has more than one ExecStart=3D setting, w=
hich
is only allowed for Type=3Doneshot services. Refusing.

in my journal.
wdmd seems to be part of sanlock.

Besides these messages I have problems with ssh connections to my remote
machines, which are just disconnected without any message. Not sure, if thi=
s is
related.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17197488082.f8DA6aA8.347
Date: Sun, 30 Jun 2024 12:00:08 +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
          1227208

          Summary
          wdmd.service: Service has more than one ExecStart=3D setting

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          opensuse@mike.franken.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

With Tumbleweed snapshot 20240627 I get:

systemd[1]: wdmd.service: Service has more than one ExecStart=3D setting, w=
hich
is only allowed for Type=3Doneshot services. Refusing.

in my journal.
wdmd seems to be part of sanlock.

Besides these messages I have problems with ssh connections to my remote
machines, which are just disconnected without any message. Not sure, if thi=
s is
related.

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

You are on the CC list for the bug.

=

--17197488082.f8DA6aA8.347--