--172664625211.1eD9.173
Date: Wed, 18 Sep 2024 07:57:32 +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=3D1230686

            Bug ID: 1230686
           Summary: VUL-0: CVE-2024-45405: onefetch: gix-path: gix-path improperly resolves configuration path reported by Git
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
               URL: https://smash.suse.de/issue/419949/
                OS: Other
            Status: NEW
        Whiteboard: CVSSv3.1:SUSE:CVE-2024-45405:6.4:(AV:L/AC:H/PR:H/UI:N/
                    S:U/C:H/I:H/A:H)
                    CVSSv4.0:SUSE:CVE-2024-45405:7.0:(AV:L/AC:H/AT:P/PR:H/
                    UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H)
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: mvetter-at-suse.com
          Reporter: andrea.mattiazzo-at-suse.com
        QA Contact: security-team-at-suse.de
            Blocks: 1230682
  Target Milestone: ---
          Found By: ---
           Blocker: ---

`gix-path` is a crate of the `gitoxide` project (an implementation of `git`
written in Rust) dealing paths and their conversions. Prior to version 0.10=
.11,
`gix-path` runs `git` to find the path of a configuration file associated w=
ith
the `git` installation, but improperly resolves paths containing unusual or
non-ASCII characters, in rare cases enabling a local attacker to inject
configuration leading to code execution. Version 0.10.11 contains a patch f=
or
the issue.

In `gix_path::env`, the underlying implementation of the `installation_conf=
ig`
and `installation_config_prefix` functions calls `git config -l --show-orig=
in`
to find the path of a file to treat as belonging to the `git` installation.
Affected versions of `gix-path` do not pass `-z`/`--null` to cause `git` to
report literal paths. Instead, to cover the occasional case that `git` outp=
uts
a quoted path, they attempt to parse the path by stripping the quotation ma=
rks.
The problem is that, when a path is quoted, it may change in substantial wa=
ys
beyond the concatenation of quotation marks. If not reversed, these changes=
 can
result in another valid path that is not equivalent to the original.

On a single-user system, it is not possible to exploit this, unless
`GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` have been set to unusual values=
 or
Git has been installed in an unusual way. Such a scenario is not expected.
Exploitation is unlikely even on a multi-user system, though it is plausibl=
e in
some uncommon configurations or use cases. In general, exploitation is more
likely to succeed if users are expected to install `git` themselves, and are
likely to do so in predictable locations; locations where `git` is installe=
d,
whether due to usernames in their paths or otherwise, contain characters th=
at
`git` quotes by default in paths, such as non-English letters and accented
letters; a custom `system`-scope configuration file is specified with the
`GIT_CONFIG_SYSTEM` environment variable, and its path is in an unusual
location or has strangely named components; or a `system`-scope configurati=
on
file is absent, empty, or suppressed by means other than `GIT_CONFIG_NOSYST=
EM`.
Currently, `gix-path` can treat a `global`-scope configuration file as
belonging to the installation if no higher scope configuration file is
available. This increases the likelihood of exploitation even on a system w=
here
`git` is installed system-wide in an ordinary way. However, exploitation is
expected to be very difficult even under any combination of those factors.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45405
https://bugzilla.redhat.com/show_bug.cgi?id=3D2310412
https://www.cve.org/CVERecord?id=3DCVE-2024-45405
https://github.com/Byron/gitoxide/blob/1cfe577d461293879e91538dbc4bbfe01722=
e1e8/gix-path/src/env/git/mod.rs#L138-L142
https://github.com/Byron/gitoxide/commit/650a1b5cf25e086197cc55a68525a411e1=
c28031
https://github.com/Byron/gitoxide/security/advisories/GHSA-m8rp-vv92-46c7
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--172664625211.1eD9.173
Date: Wed, 18 Sep 2024 07:57:32 +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
          1230686

          Summary
          VUL-0: CVE-2024-45405: onefetch: gix-path: gix-path improperl=
y resolves configuration path reported by Git

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Whiteboard
          CVSSv3.1:SUSE:CVE-2024-45405:6.4:(AV:L/AC:H/PR:H/UI:N/S:U/C:H=
/I:H/A:H) CVSSv4.0:SUSE:CVE-2024-45405:7.0:(AV:L/AC:H/AT:P/PR:H/UI:N/VC:N/V=
I:H/VA:N/SC:H/SI:H/SA:H)=20

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          mvetter@suse.com

          Reporter
          andrea.mattiazzo@suse.com

          QA Contact
          security-team@suse.de

          Blocks
          1230682

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

`gix-path` is a crate of the `gitoxide` project (an implemen=
tation of `git`
written in Rust) dealing paths and their conversions. Prior to version 0.10=
.11,
`gix-path` runs `git` to find the path of a configuration file associated w=
ith
the `git` installation, but improperly resolves paths containing unusual or
non-ASCII characters, in rare cases enabling a local attacker to inject
configuration leading to code execution. Version 0.10.11 contains a patch f=
or
the issue.

In `gix_path::env`, the underlying implementation of the `installation_conf=
ig`
and `installation_config_prefix` functions calls `git config -l --show-orig=
in`
to find the path of a file to treat as belonging to the `git` installation.
Affected versions of `gix-path` do not pass `-z`/`--null` to cause `git` to
report literal paths. Instead, to cover the occasional case that `git` outp=
uts
a quoted path, they attempt to parse the path by stripping the quotation ma=
rks.
The problem is that, when a path is quoted, it may change in substantial wa=
ys
beyond the concatenation of quotation marks. If not reversed, these changes=
 can
result in another valid path that is not equivalent to the original.

On a single-user system, it is not possible to exploit this, unless
`GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` have been set to unusual values=
 or
Git has been installed in an unusual way. Such a scenario is not expected.
Exploitation is unlikely even on a multi-user system, though it is plausibl=
e in
some uncommon configurations or use cases. In general, exploitation is more
likely to succeed if users are expected to install `git` themselves, and are
likely to do so in predictable locations; locations where `git` is installe=
d,
whether due to usernames in their paths or otherwise, contain characters th=
at
`git` quotes by default in paths, such as non-English letters and accented
letters; a custom `system`-scope configuration file is specified with the
`GIT_CONFIG_SYSTEM` environment variable, and its path is in an unusual
location or has strangely named components; or a `system`-scope configurati=
on
file is absent, empty, or suppressed by means other than `GIT_CONFIG_NOSYST=
EM`.
Currently, `gix-path` can treat a `global`-scope configuration file as
belonging to the installation if no higher scope configuration file is
available. This increases the likelihood of exploitation even on a system w=
here
`git` is installed system-wide in an ordinary way. However, exploitation is
expected to be very difficult even under any combination of those factors.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45405
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2310412
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-45405
https://github.com/B=
yron/gitoxide/blob/1cfe577d461293879e91538dbc4bbfe01722e1e8/gix-path/src/en=
v/git/mod.rs#L138-L142
https://github.com/Byron/gitoxide/commit/650a1b5cf25e086=
197cc55a68525a411e1c28031
https://github.com/Byron/gitoxide/security/advisories/GHSA-m8rp-=
vv92-46c7

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

You are on the CC list for the bug.

=

--172664625211.1eD9.173--


--17266462538.3B844.173
Date: Wed, 18 Sep 2024 07:57:33 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1230691
           Summary: VUL-0: CVE-2024-45405: stgit: gix-path: gix-path improperly resolves configuration path reported by Git
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
               URL: https://smash.suse.de/issue/419949/
                OS: Other
            Status: NEW
        Whiteboard: CVSSv3.1:SUSE:CVE-2024-45405:6.4:(AV:L/AC:H/PR:H/UI:N/
                    S:U/C:H/I:H/A:H)
                    CVSSv4.0:SUSE:CVE-2024-45405:7.0:(AV:L/AC:H/AT:P/PR:H/
                    UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H)
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: tiwai-at-suse.com
          Reporter: andrea.mattiazzo-at-suse.com
        QA Contact: security-team-at-suse.de
            Blocks: 1230682
  Target Milestone: ---
          Found By: ---
           Blocker: ---

`gix-path` is a crate of the `gitoxide` project (an implementation of `git`
written in Rust) dealing paths and their conversions. Prior to version 0.10=
.11,
`gix-path` runs `git` to find the path of a configuration file associated w=
ith
the `git` installation, but improperly resolves paths containing unusual or
non-ASCII characters, in rare cases enabling a local attacker to inject
configuration leading to code execution. Version 0.10.11 contains a patch f=
or
the issue.

In `gix_path::env`, the underlying implementation of the `installation_conf=
ig`
and `installation_config_prefix` functions calls `git config -l --show-orig=
in`
to find the path of a file to treat as belonging to the `git` installation.
Affected versions of `gix-path` do not pass `-z`/`--null` to cause `git` to
report literal paths. Instead, to cover the occasional case that `git` outp=
uts
a quoted path, they attempt to parse the path by stripping the quotation ma=
rks.
The problem is that, when a path is quoted, it may change in substantial wa=
ys
beyond the concatenation of quotation marks. If not reversed, these changes=
 can
result in another valid path that is not equivalent to the original.

On a single-user system, it is not possible to exploit this, unless
`GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` have been set to unusual values=
 or
Git has been installed in an unusual way. Such a scenario is not expected.
Exploitation is unlikely even on a multi-user system, though it is plausibl=
e in
some uncommon configurations or use cases. In general, exploitation is more
likely to succeed if users are expected to install `git` themselves, and are
likely to do so in predictable locations; locations where `git` is installe=
d,
whether due to usernames in their paths or otherwise, contain characters th=
at
`git` quotes by default in paths, such as non-English letters and accented
letters; a custom `system`-scope configuration file is specified with the
`GIT_CONFIG_SYSTEM` environment variable, and its path is in an unusual
location or has strangely named components; or a `system`-scope configurati=
on
file is absent, empty, or suppressed by means other than `GIT_CONFIG_NOSYST=
EM`.
Currently, `gix-path` can treat a `global`-scope configuration file as
belonging to the installation if no higher scope configuration file is
available. This increases the likelihood of exploitation even on a system w=
here
`git` is installed system-wide in an ordinary way. However, exploitation is
expected to be very difficult even under any combination of those factors.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45405
https://bugzilla.redhat.com/show_bug.cgi?id=3D2310412
https://www.cve.org/CVERecord?id=3DCVE-2024-45405
https://github.com/Byron/gitoxide/blob/1cfe577d461293879e91538dbc4bbfe01722=
e1e8/gix-path/src/env/git/mod.rs#L138-L142
https://github.com/Byron/gitoxide/commit/650a1b5cf25e086197cc55a68525a411e1=
c28031
https://github.com/Byron/gitoxide/security/advisories/GHSA-m8rp-vv92-46c7
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17266462538.3B844.173
Date: Wed, 18 Sep 2024 07:57:33 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1230691

          Summary
          VUL-0: CVE-2024-45405: stgit: gix-path: gix-path improperly r=
esolves configuration path reported by Git

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Whiteboard
          CVSSv3.1:SUSE:CVE-2024-45405:6.4:(AV:L/AC:H/PR:H/UI:N/S:U/C:H=
/I:H/A:H) CVSSv4.0:SUSE:CVE-2024-45405:7.0:(AV:L/AC:H/AT:P/PR:H/UI:N/VC:N/V=
I:H/VA:N/SC:H/SI:H/SA:H)=20

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          tiwai@suse.com

          Reporter
          andrea.mattiazzo@suse.com

          QA Contact
          security-team@suse.de

          Blocks
          1230682

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

`gix-path` is a crate of the `gitoxide` project (an implemen=
tation of `git`
written in Rust) dealing paths and their conversions. Prior to version 0.10=
.11,
`gix-path` runs `git` to find the path of a configuration file associated w=
ith
the `git` installation, but improperly resolves paths containing unusual or
non-ASCII characters, in rare cases enabling a local attacker to inject
configuration leading to code execution. Version 0.10.11 contains a patch f=
or
the issue.

In `gix_path::env`, the underlying implementation of the `installation_conf=
ig`
and `installation_config_prefix` functions calls `git config -l --show-orig=
in`
to find the path of a file to treat as belonging to the `git` installation.
Affected versions of `gix-path` do not pass `-z`/`--null` to cause `git` to
report literal paths. Instead, to cover the occasional case that `git` outp=
uts
a quoted path, they attempt to parse the path by stripping the quotation ma=
rks.
The problem is that, when a path is quoted, it may change in substantial wa=
ys
beyond the concatenation of quotation marks. If not reversed, these changes=
 can
result in another valid path that is not equivalent to the original.

On a single-user system, it is not possible to exploit this, unless
`GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` have been set to unusual values=
 or
Git has been installed in an unusual way. Such a scenario is not expected.
Exploitation is unlikely even on a multi-user system, though it is plausibl=
e in
some uncommon configurations or use cases. In general, exploitation is more
likely to succeed if users are expected to install `git` themselves, and are
likely to do so in predictable locations; locations where `git` is installe=
d,
whether due to usernames in their paths or otherwise, contain characters th=
at
`git` quotes by default in paths, such as non-English letters and accented
letters; a custom `system`-scope configuration file is specified with the
`GIT_CONFIG_SYSTEM` environment variable, and its path is in an unusual
location or has strangely named components; or a `system`-scope configurati=
on
file is absent, empty, or suppressed by means other than `GIT_CONFIG_NOSYST=
EM`.
Currently, `gix-path` can treat a `global`-scope configuration file as
belonging to the installation if no higher scope configuration file is
available. This increases the likelihood of exploitation even on a system w=
here
`git` is installed system-wide in an ordinary way. However, exploitation is
expected to be very difficult even under any combination of those factors.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45405
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2310412
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-45405
https://github.com/B=
yron/gitoxide/blob/1cfe577d461293879e91538dbc4bbfe01722e1e8/gix-path/src/en=
v/git/mod.rs#L138-L142
https://github.com/Byron/gitoxide/commit/650a1b5cf25e086=
197cc55a68525a411e1c28031
https://github.com/Byron/gitoxide/security/advisories/GHSA-m8rp-=
vv92-46c7

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

You are on the CC list for the bug.

=

--17266462538.3B844.173--


--17266462536.3D8eDd01.173
Date: Wed, 18 Sep 2024 07:57:33 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1230690
           Summary: VUL-0: CVE-2024-45405: sile: gix-path: gix-path improperly resolves configuration path reported by Git
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
               URL: https://smash.suse.de/issue/419949/
                OS: Other
            Status: NEW
        Whiteboard: CVSSv3.1:SUSE:CVE-2024-45405:6.4:(AV:L/AC:H/PR:H/UI:N/
                    S:U/C:H/I:H/A:H)
                    CVSSv4.0:SUSE:CVE-2024-45405:7.0:(AV:L/AC:H/AT:P/PR:H/
                    UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H)
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: pirateclip-at-protonmail.com
          Reporter: andrea.mattiazzo-at-suse.com
        QA Contact: security-team-at-suse.de
            Blocks: 1230682
  Target Milestone: ---
          Found By: ---
           Blocker: ---

`gix-path` is a crate of the `gitoxide` project (an implementation of `git`
written in Rust) dealing paths and their conversions. Prior to version 0.10=
.11,
`gix-path` runs `git` to find the path of a configuration file associated w=
ith
the `git` installation, but improperly resolves paths containing unusual or
non-ASCII characters, in rare cases enabling a local attacker to inject
configuration leading to code execution. Version 0.10.11 contains a patch f=
or
the issue.

In `gix_path::env`, the underlying implementation of the `installation_conf=
ig`
and `installation_config_prefix` functions calls `git config -l --show-orig=
in`
to find the path of a file to treat as belonging to the `git` installation.
Affected versions of `gix-path` do not pass `-z`/`--null` to cause `git` to
report literal paths. Instead, to cover the occasional case that `git` outp=
uts
a quoted path, they attempt to parse the path by stripping the quotation ma=
rks.
The problem is that, when a path is quoted, it may change in substantial wa=
ys
beyond the concatenation of quotation marks. If not reversed, these changes=
 can
result in another valid path that is not equivalent to the original.

On a single-user system, it is not possible to exploit this, unless
`GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` have been set to unusual values=
 or
Git has been installed in an unusual way. Such a scenario is not expected.
Exploitation is unlikely even on a multi-user system, though it is plausibl=
e in
some uncommon configurations or use cases. In general, exploitation is more
likely to succeed if users are expected to install `git` themselves, and are
likely to do so in predictable locations; locations where `git` is installe=
d,
whether due to usernames in their paths or otherwise, contain characters th=
at
`git` quotes by default in paths, such as non-English letters and accented
letters; a custom `system`-scope configuration file is specified with the
`GIT_CONFIG_SYSTEM` environment variable, and its path is in an unusual
location or has strangely named components; or a `system`-scope configurati=
on
file is absent, empty, or suppressed by means other than `GIT_CONFIG_NOSYST=
EM`.
Currently, `gix-path` can treat a `global`-scope configuration file as
belonging to the installation if no higher scope configuration file is
available. This increases the likelihood of exploitation even on a system w=
here
`git` is installed system-wide in an ordinary way. However, exploitation is
expected to be very difficult even under any combination of those factors.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45405
https://bugzilla.redhat.com/show_bug.cgi?id=3D2310412
https://www.cve.org/CVERecord?id=3DCVE-2024-45405
https://github.com/Byron/gitoxide/blob/1cfe577d461293879e91538dbc4bbfe01722=
e1e8/gix-path/src/env/git/mod.rs#L138-L142
https://github.com/Byron/gitoxide/commit/650a1b5cf25e086197cc55a68525a411e1=
c28031
https://github.com/Byron/gitoxide/security/advisories/GHSA-m8rp-vv92-46c7
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17266462536.3D8eDd01.173
Date: Wed, 18 Sep 2024 07:57:33 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1230690

          Summary
          VUL-0: CVE-2024-45405: sile: gix-path: gix-path improperly re=
solves configuration path reported by Git

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Whiteboard
          CVSSv3.1:SUSE:CVE-2024-45405:6.4:(AV:L/AC:H/PR:H/UI:N/S:U/C:H=
/I:H/A:H) CVSSv4.0:SUSE:CVE-2024-45405:7.0:(AV:L/AC:H/AT:P/PR:H/UI:N/VC:N/V=
I:H/VA:N/SC:H/SI:H/SA:H)=20

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          pirateclip@protonmail.com

          Reporter
          andrea.mattiazzo@suse.com

          QA Contact
          security-team@suse.de

          Blocks
          1230682

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

`gix-path` is a crate of the `gitoxide` project (an implemen=
tation of `git`
written in Rust) dealing paths and their conversions. Prior to version 0.10=
.11,
`gix-path` runs `git` to find the path of a configuration file associated w=
ith
the `git` installation, but improperly resolves paths containing unusual or
non-ASCII characters, in rare cases enabling a local attacker to inject
configuration leading to code execution. Version 0.10.11 contains a patch f=
or
the issue.

In `gix_path::env`, the underlying implementation of the `installation_conf=
ig`
and `installation_config_prefix` functions calls `git config -l --show-orig=
in`
to find the path of a file to treat as belonging to the `git` installation.
Affected versions of `gix-path` do not pass `-z`/`--null` to cause `git` to
report literal paths. Instead, to cover the occasional case that `git` outp=
uts
a quoted path, they attempt to parse the path by stripping the quotation ma=
rks.
The problem is that, when a path is quoted, it may change in substantial wa=
ys
beyond the concatenation of quotation marks. If not reversed, these changes=
 can
result in another valid path that is not equivalent to the original.

On a single-user system, it is not possible to exploit this, unless
`GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` have been set to unusual values=
 or
Git has been installed in an unusual way. Such a scenario is not expected.
Exploitation is unlikely even on a multi-user system, though it is plausibl=
e in
some uncommon configurations or use cases. In general, exploitation is more
likely to succeed if users are expected to install `git` themselves, and are
likely to do so in predictable locations; locations where `git` is installe=
d,
whether due to usernames in their paths or otherwise, contain characters th=
at
`git` quotes by default in paths, such as non-English letters and accented
letters; a custom `system`-scope configuration file is specified with the
`GIT_CONFIG_SYSTEM` environment variable, and its path is in an unusual
location or has strangely named components; or a `system`-scope configurati=
on
file is absent, empty, or suppressed by means other than `GIT_CONFIG_NOSYST=
EM`.
Currently, `gix-path` can treat a `global`-scope configuration file as
belonging to the installation if no higher scope configuration file is
available. This increases the likelihood of exploitation even on a system w=
here
`git` is installed system-wide in an ordinary way. However, exploitation is
expected to be very difficult even under any combination of those factors.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45405
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2310412
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-45405
https://github.com/B=
yron/gitoxide/blob/1cfe577d461293879e91538dbc4bbfe01722e1e8/gix-path/src/en=
v/git/mod.rs#L138-L142
https://github.com/Byron/gitoxide/commit/650a1b5cf25e086=
197cc55a68525a411e1c28031
https://github.com/Byron/gitoxide/security/advisories/GHSA-m8rp-=
vv92-46c7

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

You are on the CC list for the bug.

=

--17266462536.3D8eDd01.173--


--17267451750.f49d.101
Date: Thu, 19 Sep 2024 11:26:15 +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=3D1230797

            Bug ID: 1230797
           Summary: [RPi] brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: ivan.ivanov-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I am seeing following errors with
openSUSE-Tumbleweed-Minimal-Image.aarch64-1.0.0-RaspberryPi-Snapshot2024091=
6.raw.xz

Connection to WiFi AP fails and kernel show these messages continuously.=20

Similar to bsc#1208900 and bsc#1215134 except that this time wireless-regdb=
 is
installed by default.

What is even more confusing is that
openSUSE-Tumbleweed-ARM-XFCE-raspberrypi.aarch64-2024.09.02-Snapshot2024091=
1.raw.xz
is working fine.

Minimal image have this frimware version:

i+ | kernel-firmware-brcm        | package | 20240912-1.1   | noarch |
openSUSE-Tumbleweed-Oss

While XFCE have:

i  | kernel-firmware-brcm        | package | 20240903-1.1   | noarch | (Sys=
tem
Packages)

Unfortunately downgrading kernel-firmware-brcm did not help.

---

[ 9817.315337][ T1475] net_ratelimit: 11 callbacks suppressed
[ 9817.315345][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0x100e fai=
l,
reason -52
[ 9817.328929][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd022 fai=
l,
reason -52
[ 9817.441983][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd026 fai=
l,
reason -52
[ 9817.551982][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd02a fai=
l,
reason -52
[ 9817.661985][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd02e fai=
l,
reason -52
[ 9817.771986][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd034 fai=
l,
reason -52
[ 9817.780047][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd038 fai=
l,
reason -52
[ 9817.788108][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd03c fai=
l,
reason -52
[ 9817.796162][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd040 fai=
l,
reason -52
[ 9817.804215][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd064 fai=
l,
reason -52
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17267451750.f49d.101
Date: Thu, 19 Sep 2024 11:26:15 +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
          1230797

          Summary
          [RPi] brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, =
reason -52

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          aarch64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          ivan.ivanov@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I am seeing following errors with
openSUSE-Tumbleweed-Minimal-Image.aarch64-1.0.0-RaspberryPi-Snapshot2024091=
6.raw.xz

Connection to WiFi AP fails and kernel show these messages continuously.=20

Similar to b=
sc#1208900 and bsc#1215134 except that this time wireless-regdb is
installed by default.

What is even more confusing is that
openSUSE-Tumbleweed-ARM-XFCE-raspberrypi.aarch64-2024.09.02-Snapshot2024091=
1.raw.xz
is working fine.

Minimal image have this frimware version:

i+ | kernel-firmware-brcm        | package | 20240912-1.1   | noarch |
openSUSE-Tumbleweed-Oss

While XFCE have:

i  | kernel-firmware-brcm        | package | 20240903-1.1   | noarch | (Sys=
tem
Packages)

Unfortunately downgrading kernel-firmware-brcm did not help.

---

[ 9817.315337][ T1475] net_ratelimit: 11 callbacks suppressed
[ 9817.315345][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0x100e fai=
l,
reason -52
[ 9817.328929][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd022 fai=
l,
reason -52
[ 9817.441983][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd026 fai=
l,
reason -52
[ 9817.551982][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd02a fai=
l,
reason -52
[ 9817.661985][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd02e fai=
l,
reason -52
[ 9817.771986][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd034 fai=
l,
reason -52
[ 9817.780047][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd038 fai=
l,
reason -52
[ 9817.788108][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd03c fai=
l,
reason -52
[ 9817.796162][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd040 fai=
l,
reason -52
[ 9817.804215][ T1475] brcmfmac: brcmf_set_channel: set chanspec 0xd064 fai=
l,
reason -52

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

You are on the CC list for the bug.

=

--17267451750.f49d.101--


--17268373951.1dbFe72e.1443
Date: Fri, 20 Sep 2024 13:03:15 +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=3D1230858

            Bug ID: 1230858
           Summary: Images are missing /boot/vmlinuz + /boot/initrd symlinks
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Bootloader
          Assignee: martin.wilck-at-suse.com
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: aplanas-at-suse.com, iforster-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

In Tumbleweed images like
https://download.opensuse.org/tumbleweed/appliances/openSUSE-MicroOS.x86_64=
-kvm-and-xen.qcow2,
/boot/vmlinuz and /boot/initrd are missing.

FWICT /usr/lib/module-init-tools/kernel-scriptlets/rpm-post simply doesn't =
add
those if it's inside a kiwi build env. Is that something that suse-module-t=
ools
could just do anyway or does this need some cooperation with kiwi?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17268373951.1dbFe72e.1443
Date: Fri, 20 Sep 2024 13:03:15 +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
          1230858

          Summary
          Images are missing /boot/vmlinuz + /boot/initrd symlinks

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Bootloader

          Assignee
          martin.wilck@suse.com

          Reporter
          fvogt@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          aplanas@suse.com, iforster@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

In Tumbleweed images like
https://download.opensuse.org/tumbleweed/app=
liances/openSUSE-MicroOS.x86_64-kvm-and-xen.qcow2,
/boot/vmlinuz and /boot/initrd are missing.

FWICT /usr/lib/module-init-tools/kernel-scriptlets/rpm-post simply doesn't =
add
those if it's inside a kiwi build env. Is that something that suse-module-t=
ools
could just do anyway or does this need some cooperation with kiwi?

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

You are on the CC list for the bug.

=

--17268373951.1dbFe72e.1443--


--17270821055.dbAe3.791
Date: Mon, 23 Sep 2024 09:01:45 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1230906
           Summary: python312: has some mtime based .pyc files
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Python
          Assignee: python-maintainers-at-suse.com
          Reporter: bwiedemann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: Development
           Blocker: ---

With the fixes from bug 1227999 and PGO disabled, there is only one minor i=
ssue
left with python312-tools
I found that=20
/usr/share/doc/packages/python312-core/Tools/build/__pycache__/generate_glo=
bal_objects.cpython-312.pyc
/usr/share/doc/packages/python312-core/Tools/build/__pycache__/umarshal.cpy=
thon-312.pyc
are mtime-based pyc files and thus vary between builds in offset 8-11 (32 b=
it
UNIX epoch value).

I tried
export PYTHONDONTWRITEBYTECODE=3D1
but it did not help.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17270821055.dbAe3.791
Date: Mon, 23 Sep 2024 09:01:45 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1230906

          Summary
          python312: has some mtime based .pyc files

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          All

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Python

          Assignee
          python-maintainers@suse.com

          Reporter
          bwiedemann@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          Development

          Blocker
          ---

With the fixes from bug 1227999 and PGO disabled, the=
re is only one minor issue
left with python312-tools
I found that=20
/usr/share/doc/packages/python312-core/Tools/build/__pycache__/generate_glo=
bal_objects.cpython-312.pyc
/usr/share/doc/packages/python312-core/Tools/build/__pycache__/umarshal.cpy=
thon-312.pyc
are mtime-based pyc files and thus vary between builds in offset 8-11 (32 b=
it
UNIX epoch value).

I tried
export PYTHONDONTWRITEBYTECODE=3D1
but it did not help.

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

You are on the CC list for the bug.

=

--17270821055.dbAe3.791--


body:
--17270964771.7AEA9C5D.1478
Date: Mon, 23 Sep 2024 13:01:17 +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=3D1230912

            Bug ID: 1230912
           Summary: zypper hangs if no network connection
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: libzypp
          Assignee: zypp-maintainers-at-suse.de
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 877505
  --> https://bugzilla.suse.com/attachment.cgi?id=3D877505&action=3Dedit
log of combustion and zypper.log

Recently, the disk-encryption-tool CI started failing reproducibly because =
the
image no longer boots within 5min. Some logging showed that it's stuck in
transactional-update's selfupdate during the combustion phase in the initrd.

I was able to collect zypper.log of such a hang. Last few lines:

2024-09-23 12:02:15 <1> localhost(840) [zypp::media]
MediaHandler.cc(attach):654 Attached: https://download.opensuse.org/ attach=
ed;
localRoot "/var/tmp/AP_0xMm8N8v"
2024-09-23 12:02:15 <1> localhost(840) [zypp::media++]
MediaManager.cc(checkDesired):155 checkDesired(1): desired (report by
zypp::media::NoVerifier)
2024-09-23 12:02:15 <1> localhost(840) [zypp::media++]
MediaManager.cc(checkDesired):157 checkDesired(1): desired (cached)
2024-09-23 12:02:15 <1> localhost(840) [zypp::media++]
MediaMultiCurl.cc(doGetFileCopy):1502 dest: /var/tmp/AP_0xMm8N8v/geoip
2024-09-23 12:02:15 <1> localhost(840) [zypp::media++]
MediaMultiCurl.cc(doGetFileCopy):1503 temp:
/var/tmp/AP_0xMm8N8v/geoip.new.zypp.p9Et4x
2024-09-23 12:02:15 <1> localhost(840) [zypp::media++]
MediaCurl.cc(doGetFileCopyFile):1204 /geoip
2024-09-23 12:02:15 <1> localhost(840) [zypp::media++]
MediaCurl.cc(doGetFileCopyFile):1214 URL: https://download.opensuse.org/geo=
ip

There is no /etc/resolv.conf, so I'd expect this to fail immediately. Maybe
this is a race condition, where curl fails before zypper sets up waiting?

I wasn't able to reproduce this locally in a container.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17270964771.7AEA9C5D.1478
Date: Mon, 23 Sep 2024 13:01:17 +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
          1230912

          Summary
          zypper hangs if no network connection

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          libzypp

          Assignee
          zypp-maintainers@suse.de

          Reporter
          fvogt@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attac=
hment 877505 [details]
log of combustion and zypper.log

Recently, the disk-encryption-tool CI started failing reproducibly because =
the
image no longer boots within 5min. Some logging showed that it's stuck in
transactional-update's selfupdate during the combustion phase in the initrd.

I was able to collect zypper.log of such a hang. Last few lines:

2024-09-23 12:02:15 <1> localhost(840) [zypp::media]
MediaHandler.cc(attach):654 Attached: https://download.opensuse.org/ attached;
localRoot "/var/tmp/AP_0xMm8N8v"
2024-09-23 12:02:15 <1> localhost(840) [zypp::media++]
MediaManager.cc(checkDesired):155 checkDesired(1): desired (report by
zypp::media::NoVerifier)
2024-09-23 12:02:15 <1> localhost(840) [zypp::media++]
MediaManager.cc(checkDesired):157 checkDesired(1): desired (cached)
2024-09-23 12:02:15 <1> localhost(840) [zypp::media++]
MediaMultiCurl.cc(doGetFileCopy):1502 dest: /var/tmp/AP_0xMm8N8v/geoip
2024-09-23 12:02:15 <1> localhost(840) [zypp::media++]
MediaMultiCurl.cc(doGetFileCopy):1503 temp:
/var/tmp/AP_0xMm8N8v/geoip.new.zypp.p9Et4x
2024-09-23 12:02:15 <1> localhost(840) [zypp::media++]
MediaCurl.cc(doGetFileCopyFile):1204 /geoip
2024-09-23 12:02:15 <1> localhost(840) [zypp::media++]
MediaCurl.cc(doGetFileCopyFile):1214 URL: https://download.opensuse.org/geoip

There is no /etc/resolv.conf, so I'd expect this to fail immediately. Maybe
this is a race condition, where curl fails before zypper sets up waiting?

I wasn't able to reproduce this locally in a container.

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

You are on the CC list for the bug.

=

--17270964771.7AEA9C5D.1478--

summary: zypper hangs if no network connection


--17271565320.f6dfbB.401
Date: Tue, 24 Sep 2024 05:42:12 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1230925
           Summary: 6.11: Failed to write ATTR{/sys/devices/virtual/block/loop1/queue/scheduler} =3D"none"
    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: ---

In 6.11, udev cannot write loop's queue/scheduler:
> loop1: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write ATT=
R{/sys/devices/virtual/block/loop1/queue/scheduler}=3D"none", ignoring: No =
such file or directory
> loop0: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write ATT=
R{/sys/devices/virtual/block/loop0/queue/scheduler}=3D"none", ignoring: No =
such file or directory
> loop5: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write ATT=
R{/sys/devices/virtual/block/loop5/queue/scheduler}=3D"none", ignoring: No =
such file or directory
> loop3: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write ATT=
R{/sys/devices/virtual/block/loop3/queue/scheduler}=3D"none", ignoring: No =
such file or directory
> loop2: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write ATT=
R{/sys/devices/virtual/block/loop2/queue/scheduler}=3D"none", ignoring: No =
such file or directory
> loop7: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write ATT=
R{/sys/devices/virtual/block/loop7/queue/scheduler}=3D"none", ignoring: No =
such file or directory
> loop4: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write ATT=
R{/sys/devices/virtual/block/loop4/queue/scheduler}=3D"none", ignoring: No =
such file or directory
> loop6: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write ATT=
R{/sys/devices/virtual/block/loop6/queue/scheduler}=3D"none", ignoring: No =
such file or directory

This makes some openQA tests to fail:
## Observation

openQA test in scenario
microos-Staging:M-Staging-DVD-x86_64-microos@uefi-staging fails in
[journal_check](https://openqa.opensuse.org/tests/4502974/modules/journal_c=
heck/steps/22)

## Test suite description

## Reproducible

Fails since (at least) Build [M.6.1](https://openqa.opensuse.org/tests/4502=
718)

## Expected result

Last good: [M.5.1](https://openqa.opensuse.org/tests/4496549) (or more rece=
nt)

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=3Dx86_64&distri=3Dmi=
croos&flavor=3DStaging-DVD&machine=3Duefi-staging&test=3Dmicroos&version=3D=
Staging%3AM)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17271565320.f6dfbB.401
Date: Tue, 24 Sep 2024 05:42:12 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1230925

          Summary
          6.11: Failed to write ATTR{/sys/devices/virtual/block/loop1/q=
ueue/scheduler}=3D"none"

          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
          ---

In 6.11, udev cannot write loop's queue/scheduler:
> loop1: /usr/lib/udev/rules.d/60-io-scheduler.rul=
es:25 Failed to write ATTR{/sys/devices/virtual/block/loop1/queue/scheduler=
}=3D"none", ignoring: No such file or directory
> loop0: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write =
ATTR{/sys/devices/virtual/block/loop0/queue/scheduler}=3D"none", =
ignoring: No such file or directory
> loop5: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write =
ATTR{/sys/devices/virtual/block/loop5/queue/scheduler}=3D"none", =
ignoring: No such file or directory
> loop3: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write =
ATTR{/sys/devices/virtual/block/loop3/queue/scheduler}=3D"none", =
ignoring: No such file or directory
> loop2: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write =
ATTR{/sys/devices/virtual/block/loop2/queue/scheduler}=3D"none", =
ignoring: No such file or directory
> loop7: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write =
ATTR{/sys/devices/virtual/block/loop7/queue/scheduler}=3D"none", =
ignoring: No such file or directory
> loop4: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write =
ATTR{/sys/devices/virtual/block/loop4/queue/scheduler}=3D"none", =
ignoring: No such file or directory
> loop6: /usr/lib/udev/rules.d/60-io-scheduler.rules:25 Failed to write =
ATTR{/sys/devices/virtual/block/loop6/queue/scheduler}=3D"none", =
ignoring: No such file or directory

This makes some openQA tests to fail:
## Observation

openQA test in scenario
microos-Staging:M-Staging-DVD-x86_64-microos@uefi-staging fails in
[journal_check](https://openqa.opensuse.org/tests/4502974/modules=
/journal_check/steps/22)

## Test suite description

## Reproducible

Fails since (at least) Build [M.6.1](https://openqa.opensuse.org/tests/4502718)

## Expected result

Last good: [M.5.1](ht=
tps://openqa.opensuse.org/tests/4496549) (or more recent)

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tes=
ts/latest?arch=3Dx86_64&distri=3Dmicroos&flavor=3DStaging-DVD&m=
achine=3Duefi-staging&test=3Dmicroos&version=3DStaging%3AM)</pr=
e>

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

You are on the CC list for the bug.

=

--17271565320.f6dfbB.401--


--17271668644.0e92E3.446
Date: Tue, 24 Sep 2024 08:34: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=3D1230938

            Bug ID: 1230938
           Summary: SELinux: Broken httpd_can_network_connect policy on older MicroOS server
    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: felix.niederwanger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

On an older MicroOS server we see that the httpd_can_network_connect policy
cannot be loaded anymore. I cannot reporduce the issue on a fresh MicroOS V=
M.

We see the following:

> larry:~ # setsebool -P httpd_can_network_connect on
> libsepol.context_from_record: type systemd_udev_trigger_generator_exec_t =
is not defined
> libsepol.context_from_record: could not create context structure
> libsepol.context_from_string: could not create context structure
> libsepol.sepol_context_to_sid: could not convert system_u:object_r:system=
d_udev_trigger_generator_exec_t:s0 to sid
> invalid context system_u:object_r:systemd_udev_trigger_generator_exec_t:s0
> Failed to commit changes to booleans: Success

> larry:~ # semanage boolean -m --on httpd_can_network_connect
> libsepol.context_from_record: type systemd_udev_trigger_generator_exec_t =
is not defined
> libsepol.context_from_record: could not create context structure
> libsepol.context_from_string: could not create context structure
> libsepol.sepol_context_to_sid: could not convert system_u:object_r:system=
d_udev_trigger_generator_exec_t:s0 to sid
> invalid context system_u:object_r:systemd_udev_trigger_generator_exec_t:s0
> libsemanage.semanage_validate_and_compile_fcontexts: setfiles returned er=
ror code 255.
> OSError: Error

On request of Cathy Hu, we have been running `sepolgen-ifgen` there with the
following output:

> larry:~ # sepolgen-ifgen
> /usr/share/selinux/devel/include/contrib/virt.if: Syntax error on line 16=
9 ` [type=3DTICK]
> /usr/share/selinux/devel/include/contrib/virt.if: Syntax error on line 22=
0 ' [type=3DSQUOTE]
> larry:~ # setsebool -P httpd_can_network_connect on
> libsepol.context_from_record: type systemd_udev_trigger_generator_exec_t =
is not defined
> libsepol.context_from_record: could not create context structure
> libsepol.context_from_string: could not create context structure
> libsepol.sepol_context_to_sid: could not convert system_u:object_r:system=
d_udev_trigger_generator_exec_t:s0 to sid
> invalid context system_u:object_r:systemd_udev_trigger_generator_exec_t:s0
> Failed to commit changes to booleans: Success

We are using the SELinux system defaults for MicroOS on that server, provid=
ed
by the `patterns-microos-selinux` pattern.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17271668644.0e92E3.446
Date: Tue, 24 Sep 2024 08:34: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
          1230938

          Summary
          SELinux: Broken httpd_can_network_connect policy on older Mic=
roOS server

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

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

On an older MicroOS server we see that the httpd_can_network=
_connect policy
cannot be loaded anymore. I cannot reporduce the issue on a fresh MicroOS V=
M.

We see the following:

> larry:~ # setsebool -P httpd_can_network_connect=
 on
> libsepol.context_from_record: type systemd_udev_trigger_generator_exec=
_t is not defined
> libsepol.context_from_record: could not create context structure
> libsepol.context_from_string: could not create context structure
> libsepol.sepol_context_to_sid: could not convert system_u:object_r:sys=
temd_udev_trigger_generator_exec_t:s0 to sid
> invalid context system_u:object_r:systemd_udev_trigger_generator_exec_=
t:s0
> Failed to commit changes to booleans: Success

> larry:~ # semanage boolean -m --on httpd_can_net=
work_connect
> libsepol.context_from_record: type systemd_udev_trigger_generator_exec=
_t is not defined
> libsepol.context_from_record: could not create context structure
> libsepol.context_from_string: could not create context structure
> libsepol.sepol_context_to_sid: could not convert system_u:object_r:sys=
temd_udev_trigger_generator_exec_t:s0 to sid
> invalid context system_u:object_r:systemd_udev_trigger_generator_exec_=
t:s0
> libsemanage.semanage_validate_and_compile_fcontexts: setfiles returned=
 error code 255.
> OSError: Error

On request of Cathy Hu, we have been running `sepolgen-ifgen` there with the
following output:

> larry:~ # sepolgen-ifgen
> /usr/share/selinux/devel/include/contrib/virt.if: Syntax error on line=
 169 ` [type=3DTICK]
> /usr/share/selinux/devel/include/contrib/virt.if: Syntax error on line=
 220 ' [type=3DSQUOTE]
> larry:~ # setsebool -P httpd_can_network_connect on
> libsepol.context_from_record: type systemd_udev_trigger_generator_exec=
_t is not defined
> libsepol.context_from_record: could not create context structure
> libsepol.context_from_string: could not create context structure
> libsepol.sepol_context_to_sid: could not convert system_u:object_r:sys=
temd_udev_trigger_generator_exec_t:s0 to sid
> invalid context system_u:object_r:systemd_udev_trigger_generator_exec_=
t:s0
> Failed to commit changes to booleans: Success

We are using the SELinux system defaults for MicroOS on that server, provid=
ed
by the `patterns-microos-selinux` pattern.

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

You are on the CC list for the bug.

=

--17271668644.0e92E3.446--


body:
--17272711861.354c8.1590
Date: Wed, 25 Sep 2024 13:33:06 +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=3D1230983

            Bug ID: 1230983
           Summary: libmfx update break ffmpeg-6
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: sndirsch-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Date: Wed, 25 Sep 2024 13:22:12 +0200
From: "thomas.mott-at-web.de" <thomas.mott-at-web.de>
To: sndirsch-at-suse.com
Subject: new libmfx1 conflict with libavcodec60

Since 19.09.2024 the new

"openSUSE-SLE-15.5-2024-3339(1)
Security update for libmfx"

conflicts with libavcodec60 :
Message:
"the installed libavcodec60-6.1.1-150500.11.pm.1.x86_64 requires
=C2=A0'libmfx.so.1()(64bit)', but this requirement cannot be provided "

Where is the bug ?
I really don't know !=C2=A0 =F0=9F=98=B3
Please take a look at this problem !

Thanks for all time !!!

Thomas Mott

#### YaST2 conflicts list - generated 2024-09-25 12:32:28 ####

das installierte libavcodec60-6.1.1-150500.11.pm.1.x86_64 erfordert
'libmfx.so.1()(64bit)', aber diese Anforderung kann nicht bereitgestellt we=
rden
Nicht installierbare Anbieter: libmfx1-22.6.1-150500.1.16.x86_64[repo-oss]
    [ ] libmfx1-22.6.1-150500.3.5.1.x86_64 nicht installieren

    [ ] Folgende Aktionen werden ausgef=C3=BChrt:
Deinstallation von libavcodec60-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libavutil58-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libavfilter9-6.1.1-150500.11.pm.1.x86_64
Deinstallation von ffmpeg-6-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libswresample4-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libswscale7-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libavdevice60-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libpostproc57-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libavformat60-6.1.1-150500.11.pm.1.x86_64
    [ ] libavcodec60-6.1.1-150500.11.pm.1.x86_64 durch Ignorieren einiger
Abh=C3=A4ngigkeiten brechen

#### YaST2 conflicts list END ###
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17272711861.354c8.1590
Date: Wed, 25 Sep 2024 13:33:06 +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
          1230983

          Summary
          libmfx update break ffmpeg-6

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          sndirsch@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Date: Wed, 25 Sep 2024 13:22:12 +0200
From: "thomas.mott@web.d=
e" <thomas.mott@w=
eb.de>
To: sndirsch@suse.com
Subject: new libmfx1 conflict with libavcodec60

Since 19.09.2024 the new

"openSUSE-SLE-15.5-2024-3339(1)
Security update for libmfx"

conflicts with libavcodec60 :
Message:
"the installed libavcodec60-6.1.1-150500.11.pm.1.x86_64 requires
=C2=A0'libmfx.so.1()(64bit)', but this requirement cannot be provided "

Where is the bug ?
I really don't know !=C2=A0 =F0=9F=98=B3
Please take a look at this problem !

Thanks for all time !!!

Thomas Mott

#### YaST2 conflicts list - generated 2024-09-25 12:32:28 ####

das installierte libavcodec60-6.1.1-150500.11.pm.1.x86_64 erfordert
'libmfx.so.1()(64bit)', aber diese Anforderung kann nicht bereitgestellt we=
rden
Nicht installierbare Anbieter: libmfx1-22.6.1-150500.1.16.x86_64[repo-oss]
    [ ] libmfx1-22.6.1-150500.3.5.1.x86_64 nicht installieren

    [ ] Folgende Aktionen werden ausgef=C3=BChrt:
Deinstallation von libavcodec60-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libavutil58-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libavfilter9-6.1.1-150500.11.pm.1.x86_64
Deinstallation von ffmpeg-6-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libswresample4-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libswscale7-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libavdevice60-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libpostproc57-6.1.1-150500.11.pm.1.x86_64
Deinstallation von libavformat60-6.1.1-150500.11.pm.1.x86_64
    [ ] libavcodec60-6.1.1-150500.11.pm.1.x86_64 durch Ignorieren einiger
Abh=C3=A4ngigkeiten brechen

#### YaST2 conflicts list END ###

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

You are on the CC list for the bug.

=

--17272711861.354c8.1590--

summary: libmfx update break ffmpeg-6


body:
--17274247173.56Bfc.304
Date: Fri, 27 Sep 2024 08:11: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=3D1231027

            Bug ID: 1231027
           Summary: Remove /srv/www from filesystem package
    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: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

The /srv/www hierarchy is outside of the root subvolume and only used by a =
few
packages, which are not part of MicroOS/SLE Micro. But the directories are =
part
of the filesystem package. This requires some special hacks in the filesyst=
em
package and changes to this directories or files added to them are not visi=
ble
on MicroOS/SL Micro.

The /srv/www directories should be moved to the packages which really uses
them, like we did already with all other directories in /srv.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17274247173.56Bfc.304
Date: Fri, 27 Sep 2024 08:11: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
          1231027

          Summary
          Remove /srv/www from filesystem package

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

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

The /srv/www hierarchy is outside of the root subvolume and =
only used by a few
packages, which are not part of MicroOS/SLE Micro. But the directories are =
part
of the filesystem package. This requires some special hacks in the filesyst=
em
package and changes to this directories or files added to them are not visi=
ble
on MicroOS/SL Micro.

The /srv/www directories should be moved to the packages which really uses
them, like we did already with all other directories in /srv.

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

You are on the CC list for the bug.

=

--17274247173.56Bfc.304--

pkgs: apache2-mod_perl cgit munin nginx python-postorius

summary: Remove /srv/www from filesystem package


--17274411263.BDEaf14a9.952
Date: Fri, 27 Sep 2024 12:45:26 +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=3D1231040

            Bug ID: 1231040
           Summary: [Build 20240926] kdump_and_crash: mkdumprd reports 'Kernel not found' with 6.11
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/4516150/modules/kdum
                    p_and_crash/steps/45
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

## Observation

The kernel has been updated to version 6.11.0 in snapshot 0926
the kdump_and_crash test fails, as seen in openQA

The log file referenced contains only this text:

  Kernel not found.

openQA test in scenario
opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G
fails in
[kdump_and_crash](https://openqa.opensuse.org/tests/4516150/modules/kdump_a=
nd_crash/steps/45)

## Test suite description
Same as jeos, plus some more tests.

## Reproducible

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

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=3Dx86_64&distri=3Dop=
ensuse&flavor=3DJeOS-for-kvm-and-xen&machine=3D64bit_virtio-2G&test=3Djeos-=
extra&version=3DTumbleweed)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17274411263.BDEaf14a9.952
Date: Fri, 27 Sep 2024 12:45:26 +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
          1231040

          Summary
          [Build 20240926] kdump_and_crash: mkdumprd reports 'Kernel no=
t found' with 6.11

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          URL
          https://openqa.opensuse.org/tests/4516150/modules/kdump_and_c=
rash/steps/45

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          dimstar@opensuse.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

## Observation

The kernel has been updated to version 6.11.0 in snapshot 0926
the kdump_and_crash test fails, as seen in openQA

The log file referenced contains only this text:

  Kernel not found.

openQA test in scenario
opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio=
-2G
fails in
[kdump_and_crash](https://openqa.opensuse.org/tests/4516150/mod=
ules/kdump_and_crash/steps/45)

## Test suite description
Same as jeos, plus some more tests.

## Reproducible

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

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.o=
pensuse.org/tests/latest?arch=3Dx86_64&distri=3Dopensuse&flavor=3DJ=
eOS-for-kvm-and-xen&machine=3D64bit_virtio-2G&test=3Djeos-extra&amp=
;version=3DTumbleweed)

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

You are on the CC list for the bug.

=

--17274411263.BDEaf14a9.952--


--17274495104.7DFc7AA7C.1252
Date: Fri, 27 Sep 2024 15:05:10 +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=3D1231048

            Bug ID: 1231048
           Summary: systemd-experimental: error message about homed
    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: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

If I install systemd-experimental I get the following error message:

Failed to preset unit: Unit systemd-homed.service does not exist

systemd-homed is not part of systemd-experimental.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17274495104.7DFc7AA7C.1252
Date: Fri, 27 Sep 2024 15:05:10 +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
          1231048

          Summary
          systemd-experimental: error message about homed

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

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

If I install systemd-experimental I get the following error =
message:

Failed to preset unit: Unit systemd-homed.service does not exist

systemd-homed is not part of systemd-experimental.

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

You are on the CC list for the bug.

=

--17274495104.7DFc7AA7C.1252--


--17275212611.9E19EbD85.107
Date: Sat, 28 Sep 2024 11:01:01 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1231060
           Summary: Wicked does not pick up unreachable/blackhole static routes
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: srid-at-rkmail.ru
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I have a static unreachable route configured in /etc/sysconfig/network/rout=
es.
The network is brought up with wicked. It seems that at some point it stopp=
ed
picking up unreachable or blackhole routes.

The contents of /etc/sysconfig/network/routes are:

0.0.0.0/0 - - - table next0 type unreachable metric 127

I tried moving it into /etc/sysconfig/network/ifroute-eth0, but it did not
change anything, 'ip route show table next0' still does not show the
unreachable route.=20

Adding it manually works fine.

openSUSE Leap 15.5, latest updates as for 09/28/2024

zypper info wicked
Loading repository data...
Reading installed packages...

Information for package wicked:
-------------------------------
Repository     : Update repository with updates from SUSE Linux Enterprise =
15
Name           : wicked
Version        : 0.6.76-150500.3.33.1
Arch           : x86_64
Vendor         : SUSE LLC <https://www.suse.com/>
Installed Size : 3.9 MiB
Installed      : Yes (automatically)
Status         : up-to-date
Source package : wicked-0.6.76-150500.3.33.1.src
Upstream URL   : https://github.com/openSUSE/wicked
Summary        : Network configuration infrastructure
Description    :=20
    Wicked is a network configuration infrastructure incorporating a number
    of existing frameworks into a unified architecture, providing a DBUS
    interface to network configuration.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17275212611.9E19EbD85.107
Date: Sat, 28 Sep 2024 11:01:01 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1231060

          Summary
          Wicked does not pick up unreachable/blackhole static routes

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          srid@rkmail.ru

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I have a static unreachable route configured in /etc/sysconf=
ig/network/routes.
The network is brought up with wicked. It seems that at some point it stopp=
ed
picking up unreachable or blackhole routes.

The contents of /etc/sysconfig/network/routes are:

0.0.0.0/0 - - - table next0 type unreachable metric 127

I tried moving it into /etc/sysconfig/network/ifroute-eth0, but it did not
change anything, 'ip route show table next0' still does not show the
unreachable route.=20

Adding it manually works fine.

openSUSE Leap 15.5, latest updates as for 09/28/2024

zypper info wicked
Loading repository data...
Reading installed packages...

Information for package wicked:
-------------------------------
Repository     : Update repository with updates from SUSE Linux Enterprise =
15
Name           : wicked
Version        : 0.6.76-150500.3.33.1
Arch           : x86_64
Vendor         : SUSE LLC <https://www=
.suse.com/>
Installed Size : 3.9 MiB
Installed      : Yes (automatically)
Status         : up-to-date
Source package : wicked-0.6.76-150500.3.33.1.src
Upstream URL   : https://git=
hub.com/openSUSE/wicked
Summary        : Network configuration infrastructure
Description    :=20
    Wicked is a network configuration infrastructure incorporating a number
    of existing frameworks into a unified architecture, providing a DBUS
    interface to network configuration.

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

You are on the CC list for the bug.

=

--17275212611.9E19EbD85.107--


--17276976911.77ed7700c.77
Date: Mon, 30 Sep 2024 12:01: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=3D1231127

            Bug ID: 1231127
           Summary: SELinux: health-checker change causes denial
    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: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: fcrozat-at-suse.com, iforster-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

With https://github.com/openSUSE/health-checker/pull/21/files, health-check=
er
calls rpm --verifydb with a custom lock path because /usr/ is not writable.

The modified check fails now because SELinux blocks rpm from writing to
/run/rpmdb:

type=3DAVC msg=3Daudit(1727697272.028:122): avc:  denied  { open } for  pid=
=3D2368
comm=3D"rpmdb" path=3D"/run/rpmdb" dev=3D"tmpfs" ino=3D2281
scontext=3Dunconfined_u:unconfined_r:rpmdb_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:var_run_t:s0 tclass=3Dfile permissive=3D0
type=3DAVC msg=3Daudit(1727697272.028:123): avc:  denied  { open } for  pid=
=3D2368
comm=3D"rpmdb" path=3D"/run/rpmdb" dev=3D"tmpfs" ino=3D2281
scontext=3Dunconfined_u:unconfined_r:rpmdb_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:var_run_t:s0 tclass=3Dfile permissive=3D0
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17276976911.77ed7700c.77
Date: Mon, 30 Sep 2024 12:01: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
          1231127

          Summary
          SELinux: health-checker change causes denial

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

          QA Contact
          qa-bugs@suse.de

          CC
          fcrozat@suse.com, iforster@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

With https://github.com/openSUSE/health-checker/pull/21/files,=
 health-checker
calls rpm --verifydb with a custom lock path because /usr/ is not writable.

The modified check fails now because SELinux blocks rpm from writing to
/run/rpmdb:

type=3DAVC msg=3Daudit(1727697272.028:122): avc:  denied  { open } for  pid=
=3D2368
comm=3D"rpmdb" path=3D"/run/rpmdb" dev=3D"tmpfs&qu=
ot; ino=3D2281
scontext=3Dunconfined_u:unconfined_r:rpmdb_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:var_run_t:s0 tclass=3Dfile permissive=3D0
type=3DAVC msg=3Daudit(1727697272.028:123): avc:  denied  { open } for  pid=
=3D2368
comm=3D"rpmdb" path=3D"/run/rpmdb" dev=3D"tmpfs&qu=
ot; ino=3D2281
scontext=3Dunconfined_u:unconfined_r:rpmdb_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:var_run_t:s0 tclass=3Dfile permissive=3D0

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

You are on the CC list for the bug.

=

--17276976911.77ed7700c.77--


body:
--17276990030.2DB0d.143
Date: Mon, 30 Sep 2024 12:23:23 +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=3D1231128

            Bug ID: 1231128
           Summary: procps disappeared from Leap containers
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: openSUSE Leap 15.5
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Containers
          Assignee: containers-bugowner-at-suse.de
          Reporter: andrii.nikitin-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

>> podman run --rm opensuse/leap:15.6.5.634 /usr/bin/ps
>    PID TTY          TIME CMD
>      1 ?        00:00:00 ps
>> podman run --rm opensuse/leap:15.6.5.643 /usr/bin/ps
> Error: crun: executable file `/usr/bin/ps` not found in $PATH: No such fi=
le or directory: OCI runtime attempted to invoke a command that was not fou=
nd
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17276990030.2DB0d.143
Date: Mon, 30 Sep 2024 12:23:23 +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
          1231128

          Summary
          procps disappeared from Leap containers

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          openSUSE Leap 15.5

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Containers

          Assignee
          containers-bugowner@suse.de

          Reporter
          andrii.nikitin@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

>> podman run --rm opensuse/leap=
:15.6.5.634 /usr/bin/ps
>    PID TTY          TIME CMD
>      1 ?        00:00:00 ps
>> podman run --rm opensuse/leap:15.6.5.643 /usr/bin/ps
> Error: crun: executable file `/usr/bin/ps` not found in $PATH: No such=
 file or directory: OCI runtime attempted to invoke a command that was not =
found

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

You are on the CC list for the bug.

=

--17276990030.2DB0d.143--

summary: procps disappeared from Leap containers


--17277478730.99afaB.122
Date: Tue, 1 Oct 2024 01:57:53 +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=3D1231167

            Bug ID: 1231167
           Summary: Enable CONFIG_SCSI_UFS_QCOM for UFS support on QCOM platforms
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: rsalveti-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 877673
  --> https://bugzilla.suse.com/attachment.cgi?id=3D877673&action=3Dedit
kernel config diff

Hi,

I'm validating openSUSE Tumbleweed on QCOM-based arm64 platforms (e.g. rb3g=
en2)
and noticed the installer can't find the UFS controller. This patch enables
CONFIG_SCSI_UFS_QCOM as module so it can identify UFS controllers on QCOM
platforms.

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

--17277478730.99afaB.122
Date: Tue, 1 Oct 2024 01:57:53 +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
          1231167

          Summary
          Enable CONFIG_SCSI_UFS_QCOM for UFS support on QCOM platforms

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          aarch64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          rsalveti@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 877673</=
a> [details]
kernel config diff

Hi,

I'm validating openSUSE Tumbleweed on QCOM-based arm64 platforms (e.g. rb3g=
en2)
and noticed the installer can't find the UFS controller. This patch enables
CONFIG_SCSI_UFS_QCOM as module so it can identify UFS controllers on QCOM
platforms.

Patch attached.

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

You are on the CC list for the bug.

=

--17277478730.99afaB.122--


--17278194252.E9c0.2020
Date: Tue, 1 Oct 2024 21:50:25 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1231225
           Summary: Virtualbox 7.1.0 cannot install extension pack
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: zzq1015-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Command I used:

sudo VBoxManage extpack install --replace
~/Downloads/virtualbox/Oracle_VirtualBox_Extension_Pack-7.1.0.vbox-extpack

Result:

0%=E2=80=A6NS_ERROR_FAILURE
VBoxManage: error: Failed to install
=E2=80=9C/home/username/Downloads/virtualbox/Oracle_VirtualBox_Extension_Pa=
ck-7.1.0.vbox-extpack=E2=80=9D
VBoxManage: error: Failed to load the main module
(=E2=80=98/usr/lib/virtualbox/ExtensionPacks/Oracle_VirtualBox_Extension_Pa=
ck/linux.amd64/VBoxPuelMain.so=E2=80=99):
VERR_FILE_NOT_FOUND -
/usr/lib/virtualbox/ExtensionPacks/Oracle_VirtualBox_Extension_Pack/linux.a=
md64/VBoxPuelMain.so:
undefined symbol:
_ZN21RTCRestBinaryResponse19setConsumerCallbackEPFiPS_PKvmjmmEPv
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
ExtPackManagerWrap, interface IExtPackManager
VBoxManage: error: Context: =E2=80=9CRTEXITCODE handleExtPack(HandlerArg*)=
=E2=80=9D at line
2099 of file VBoxManageMisc.cpp
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17278194252.E9c0.2020
Date: Tue, 1 Oct 2024 21:50:25 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1231225

          Summary
          Virtualbox 7.1.0 cannot install extension pack

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Virtualization:Tools

          Assignee
          virt-bugs@suse.de

          Reporter
          zzq1015@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Command I used:

sudo VBoxManage extpack install --replace
~/Downloads/virtualbox/Oracle_VirtualBox_Extension_Pack-7.1.0.vbox-extpack

Result:

0%=E2=80=A6NS_ERROR_FAILURE
VBoxManage: error: Failed to install
=E2=80=9C/home/username/Downloads/virtualbox/Oracle_VirtualBox_Extension_Pa=
ck-7.1.0.vbox-extpack=E2=80=9D
VBoxManage: error: Failed to load the main module
(=E2=80=98/usr/lib/virtualbox/ExtensionPacks/Oracle_VirtualBox_Extension_Pa=
ck/linux.amd64/VBoxPuelMain.so=E2=80=99):
VERR_FILE_NOT_FOUND -
/usr/lib/virtualbox/ExtensionPacks/Oracle_VirtualBox_Extension_Pack/linux.a=
md64/VBoxPuelMain.so:
undefined symbol:
_ZN21RTCRestBinaryResponse19setConsumerCallbackEPFiPS_PKvmjmmEPv
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
ExtPackManagerWrap, interface IExtPackManager
VBoxManage: error: Context: =E2=80=9CRTEXITCODE handleExtPack(HandlerArg*)=
=E2=80=9D at line
2099 of file VBoxManageMisc.cpp

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

You are on the CC list for the bug.

=

--17278194252.E9c0.2020--


--17278575200.8202cD7.578
Date: Wed, 2 Oct 2024 08:25:20 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1231232
           Summary: VUL-0: chromium: multiple vulnerabilities fixed in 129.0.6668.89
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: ro-at-suse.com
          Reporter: gianluca.gabrielli-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

[$10000][367764861] High CVE-2024-7025: Integer overflow in Layout. Reporte=
d by
Tashita Software Security on 2024-09-18

[TBD][368208152] High CVE-2024-9369: Insufficient data validation in Mojo.
Reported by Xiantong Hou and Pisanbao of Wuheng Lab on 2024-09-19

[TBD][368311899] High CVE-2024-9370: Inappropriate implementation in V8.
Reported by Nguy=E1=BB=85n Ho=C3=A0ng Th=E1=BA=A1ch, =C4=90=E1=BB=97 Minh T=
u=E1=BA=A5n, and Wu JinLin of STAR Labs SG
Pte. Ltd. on 2024-09-19

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

--17278575200.8202cD7.578
Date: Wed, 2 Oct 2024 08:25:20 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1231232

          Summary
          VUL-0: chromium: multiple vulnerabilities fixed in 129.0.6668=
.89

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          ro@suse.com

          Reporter
          gianluca.gabrielli@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          security-team@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

[$10000][367764861] High CVE-2024-7025: Integer overflow in =
Layout. Reported by
Tashita Software Security on 2024-09-18

[TBD][368208152] High CVE-2024-9369: Insufficient data validation in Mojo.
Reported by Xiantong Hou and Pisanbao of Wuheng Lab on 2024-09-19

[TBD][368311899] High CVE-2024-9370: Inappropriate implementation in V8.
Reported by Nguy=E1=BB=85n Ho=C3=A0ng Th=E1=BA=A1ch, =C4=90=E1=BB=97 Minh T=
u=E1=BA=A5n, and Wu JinLin of STAR Labs SG
Pte. Ltd. on 2024-09-19

https://chromereleases.googleblog.com/2024/10/stable-=
channel-update-for-desktop.html

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

You are on the CC list for the bug.

=

--17278575200.8202cD7.578--


--17278583972.f613f6beF.623
Date: Wed, 2 Oct 2024 08:39: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=3D1231235

            Bug ID: 1231235
           Summary: Please backport 6.12 snapdragon lenovo t14s gen6 drivers to 6.11 kernel
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: rosuna-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

These 3 commits seem to be available for 6.12-rc1. Would it be possible to
backport them into the freshly released 6.11 kernel?

7ad660f9991d dt-bindings: arm: qcom: Add Lenovo ThinkPad T14s Gen 6
e6b5a4c3ae3b firmware: qcom: scm: Allow QSEECOM on ThinkPad T14s=20
7d1cbe2f4985 arm64: dts: qcom: Add X1E78100 ThinkPad T14s Gen 6

Sources:

https://www.phoronix.com/news/Linux-X1E-ThinkPad-T14s-Gen-6
"The Linux DT patches for the ThinkPad T14s Gen 6 can be found on the kernel
mailing list. Here's to hoping the addition is ready to go later this year =
into
the Linux v6.12 kernel"
https://lore.kernel.org/lkml/20240719-topic-t14s_upstream-v1-0-d7d97fdebb28=
-at-linaro.org/
https://patchew.org/linux/20240828-topic-t14s._5Fupstream-v2-0-49faea18de84=
-at-quicinc.com/

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

--17278583972.f613f6beF.623
Date: Wed, 2 Oct 2024 08:39: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
          1231235

          Summary
          Please backport 6.12 snapdragon lenovo t14s gen6 drivers to 6=
.11 kernel

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          aarch64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          rosuna@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

These 3 commits seem to be available for 6.12-rc1. Would it =
be possible to
backport them into the freshly released 6.11 kernel?

7ad660f9991d dt-bindings: arm: qcom: Add Lenovo ThinkPad T14s Gen 6
e6b5a4c3ae3b firmware: qcom: scm: Allow QSEECOM on ThinkPad T14s=20
7d1cbe2f4985 arm64: dts: qcom: Add X1E78100 ThinkPad T14s Gen 6

Sources:

htt=
ps://www.phoronix.com/news/Linux-X1E-ThinkPad-T14s-Gen-6
"The Linux DT patches for the ThinkPad T14s Gen 6 can be found on the =
kernel
mailing list. Here's to hoping the addition is ready to go later this year =
into
the Linux v6.12 kernel"
https://lore.kernel.org/lkml/20240719-topic-t1=
4s_upstream-v1-0-d7d97fdebb28@linaro.org/
https://patchew.org/linux/20240828-topic-t14s=
._5Fupstream-v2-0-49faea18de84@quicinc.com/

Thanks in advance!

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

You are on the CC list for the bug.

=

--17278583972.f613f6beF.623--