--17232775080.C666BC696.1648
Date: Sat, 10 Aug 2024 08:11:48 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1229047
           Summary: Any tpm2 command kills tpm2-abrmd service with status 74.
    Classification: openSUSE
           Product: openSUSE Aeon
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Base
          Assignee: matthias.gerstner-at-suse.com
          Reporter: opensuse-at-radok.me
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Hello,

I'm aware of bug 1187925 and know this was marked as resolved fixed.
But somehow I still have this issue with the current version of Aeon (20240=
808)

After boot the service is already in the failed status.
I can start it but any tpm2 commands kill it with status 74.

systemctl status --full tpm2-abrmd
=C3=97 tpm2-abrmd.service - TPM2 Access Broker and Resource Management Daem=
on
     Loaded: loaded (/usr/lib/systemd/system/tpm2-abrmd.service; disabled;
preset: disabled)
     Active: failed (Result: exit-code) since Sat 2024-08-10 09:36:48 CEST;
22min ago
   Duration: 10.713s
 Invocation: 2aa670ffc6774ffcbf8c4e8d037ea303
    Process: 5522 ExecStart=3D/usr/sbin/tpm2-abrmd (code=3Dexited, status=
=3D74)
   Main PID: 5522 (code=3Dexited, status=3D74)
        CPU: 41ms

Aug 10 09:36:37 localhost.localdomain systemd[1]: Starting TPM2 Access Brok=
er
and Resource Management Daemon...
Aug 10 09:36:37 localhost.localdomain systemd[1]: Started TPM2 Access Broker
and Resource Management Daemon.
Aug 10 09:36:48 localhost.localdomain systemd[1]: tpm2-abrmd.service: Main
process exited, code=3Dexited, status=3D74/IOERR
Aug 10 09:36:48 localhost.localdomain systemd[1]: tpm2-abrmd.service: Failed
with result 'exit-code'.

tpm2-abrmd --version
tpm2-abrmd version 3.0.0

ls /dev | grep tpm
tpm0
tpmrm0
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17232775080.C666BC696.1648
Date: Sat, 10 Aug 2024 08:11:48 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1229047

          Summary
          Any tpm2 command kills tpm2-abrmd service with status 74.

          Classification
          openSUSE

          Product
          openSUSE Aeon

          Version
          Current

          Hardware
          x86-64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Base

          Assignee
          matthias.gerstner@suse.com

          Reporter
          opensuse@radok.me

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Hello,

I'm aware of bug 1187925 and know this was mar=
ked as resolved fixed.
But somehow I still have this issue with the current version of Aeon (20240=
808)

After boot the service is already in the failed status.
I can start it but any tpm2 commands kill it with status 74.

systemctl status --full tpm2-abrmd
=C3=97 tpm2-abrmd.service - TPM2 Access Broker and Resource Management Daem=
on
     Loaded: loaded (/usr/lib/systemd/system/tpm2-abrmd.service; disabled;
preset: disabled)
     Active: failed (Result: exit-code) since Sat 2024-08-10 09:36:48 CEST;
22min ago
   Duration: 10.713s
 Invocation: 2aa670ffc6774ffcbf8c4e8d037ea303
    Process: 5522 ExecStart=3D/usr/sbin/tpm2-abrmd (code=3Dexited, status=
=3D74)
   Main PID: 5522 (code=3Dexited, status=3D74)
        CPU: 41ms

Aug 10 09:36:37 localhost.localdomain systemd[1]: Starting TPM2 Access Brok=
er
and Resource Management Daemon...
Aug 10 09:36:37 localhost.localdomain systemd[1]: Started TPM2 Access Broker
and Resource Management Daemon.
Aug 10 09:36:48 localhost.localdomain systemd[1]: tpm2-abrmd.service: Main
process exited, code=3Dexited, status=3D74/IOERR
Aug 10 09:36:48 localhost.localdomain systemd[1]: tpm2-abrmd.service: Failed
with result 'exit-code'.

tpm2-abrmd --version
tpm2-abrmd version 3.0.0

ls /dev | grep tpm
tpm0
tpmrm0

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

You are on the CC list for the bug.

=

--17232775080.C666BC696.1648--


--17233575952.08eA26d.1860
Date: Sun, 11 Aug 2024 06:26:35 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1229054
           Summary: Error probing device: Error sending ATA command IDENTIFY DEVICE to...
    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: alexvkaam-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I updated the 7th to kernel 6.10.3-1 from 6.9.9-1 but did not start the sys=
tem
after that till today.
As of today I am seeing:

Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY PACKET DEVICE to '/dev/sr0': Unexpected sense data returne=
d:
Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sdc': Unexpected sense data returned:
Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sdb': Unexpected sense data returned:
Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
Aug 11 07:56:56 caladan udisksd[3635]: udisks daemon version 2.10.1 starting
Aug 11 07:54:37 caladan udisksd[4655]: Error probing device: Error sending =
ATA
command IDENTIFY PACKET DEVICE to '/dev/sr0': Unexpected sense data returne=
d:
Aug 11 07:54:37 caladan udisksd[4655]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sdc': Unexpected sense data returned:
Aug 11 07:54:37 caladan udisksd[4655]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sdb': Unexpected sense data returned:
Aug 11 07:54:37 caladan udisksd[4655]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
Aug 11 07:54:37 caladan udisksd[4655]: udisks daemon version 2.10.1 starting
Aug 07 19:32:36 caladan udisksd[3675]: udisks daemon version 2.10.1 exiting
Aug 07 17:16:48 caladan udisksd[3675]: Acquired the name
org.freedesktop.UDisks2 on the system message bus
Aug 07 17:16:47 caladan udisksd[3675]: udisks daemon version 2.10.1 starting
Jul 29 17:50:42 caladan udisksd[3665]: Acquired the name
org.freedesktop.UDisks2 on the system message bus

in detail:

Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sdc': Unexpected sense data returned:
                                       0000: f0 00 01 00  50 00 01 0a  00 0=
0 00
00  00 1d 00 00    ....P...........
                                       0010: 00 00 00 00  00 00 00 00  00 0=
0 00
00  00 00 00 00    ................
                                        (g-io-error-quark, 0)
Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sdb': Unexpected sense data returned:
                                       0000: f0 00 01 00  50 00 01 0a  00 0=
0 00
00  00 1d 00 00    ....P...........
                                       0010: 00 00 00 00  00 00 00 00  00 0=
0 00
00  00 00 00 00    ................
                                        (g-io-error-quark, 0)
Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
                                       0000: f0 00 01 00  50 00 01 0a  00 0=
0 00
00  00 1d 00 00    ....P...........
                                       0010: 00 00 00 00  00 00 00 00  00 0=
0 00
00  00 00 00 00    ................
                                        (g-io-error-quark, 0)

Everything with the system runs fine, just these errors.

when doing a

hdparm -C /dev/sda

/dev/sda:
SG_IO: bad/missing sense data, sb[]:  f0 00 01 00 50 40 ff 0a 00 00 00 00 0=
0 1d
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 drive state is:  unknown

I rebooted into 6.9.9-1 and there errors don't show up and hdparm works als=
o.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17233575952.08eA26d.1860
Date: Sun, 11 Aug 2024 06:26:35 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1229054

          Summary
          Error probing device: Error sending ATA command IDENTIFY DEVI=
CE to...

          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
          alexvkaam@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I updated the 7th to kernel 6.10.3-1 from 6.9.9-1 but did no=
t start the system
after that till today.
As of today I am seeing:

Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY PACKET DEVICE to '/dev/sr0': Unexpected sense data returne=
d:
Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sdc': Unexpected sense data returned:
Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sdb': Unexpected sense data returned:
Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
Aug 11 07:56:56 caladan udisksd[3635]: udisks daemon version 2.10.1 starting
Aug 11 07:54:37 caladan udisksd[4655]: Error probing device: Error sending =
ATA
command IDENTIFY PACKET DEVICE to '/dev/sr0': Unexpected sense data returne=
d:
Aug 11 07:54:37 caladan udisksd[4655]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sdc': Unexpected sense data returned:
Aug 11 07:54:37 caladan udisksd[4655]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sdb': Unexpected sense data returned:
Aug 11 07:54:37 caladan udisksd[4655]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
Aug 11 07:54:37 caladan udisksd[4655]: udisks daemon version 2.10.1 starting
Aug 07 19:32:36 caladan udisksd[3675]: udisks daemon version 2.10.1 exiting
Aug 07 17:16:48 caladan udisksd[3675]: Acquired the name
org.freedesktop.UDisks2 on the system message bus
Aug 07 17:16:47 caladan udisksd[3675]: udisks daemon version 2.10.1 starting
Jul 29 17:50:42 caladan udisksd[3665]: Acquired the name
org.freedesktop.UDisks2 on the system message bus

in detail:

Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sdc': Unexpected sense data returned:
                                       0000: f0 00 01 00  50 00 01 0a  00 0=
0 00
00  00 1d 00 00    ....P...........
                                       0010: 00 00 00 00  00 00 00 00  00 0=
0 00
00  00 00 00 00    ................
                                        (g-io-error-quark, 0)
Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sdb': Unexpected sense data returned:
                                       0000: f0 00 01 00  50 00 01 0a  00 0=
0 00
00  00 1d 00 00    ....P...........
                                       0010: 00 00 00 00  00 00 00 00  00 0=
0 00
00  00 00 00 00    ................
                                        (g-io-error-quark, 0)
Aug 11 07:56:56 caladan udisksd[3635]: Error probing device: Error sending =
ATA
command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
                                       0000: f0 00 01 00  50 00 01 0a  00 0=
0 00
00  00 1d 00 00    ....P...........
                                       0010: 00 00 00 00  00 00 00 00  00 0=
0 00
00  00 00 00 00    ................
                                        (g-io-error-quark, 0)

Everything with the system runs fine, just these errors.

when doing a

hdparm -C /dev/sda

/dev/sda:
SG_IO: bad/missing sense data, sb[]:  f0 00 01 00 50 40 ff 0a 00 00 00 00 0=
0 1d
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 drive state is:  unknown

I rebooted into 6.9.9-1 and there errors don't show up and hdparm works als=
o.

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

You are on the CC list for the bug.

=

--17233575952.08eA26d.1860--


--17235345980.bcd6A82.431
Date: Tue, 13 Aug 2024 07:36:38 +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=3D1229098

            Bug ID: 1229098
           Summary: systemd: container networkd config files need to be in network subpackage
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: systemd-maintainers-at-suse.de
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

https://build.opensuse.org/package/rdiff/openSUSE:Factory/systemd?linkrev=
=3Dbase&rev=3D428
moved 80-container-host0.network from the network subpackage to the contain=
er
subpackage. This breaks networking in machined containers. The file is need=
ed
inside the containers, not on the host. Inside containers, machined etc tha=
t is
in the systemd-containers package is not required.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17235345980.bcd6A82.431
Date: Tue, 13 Aug 2024 07:36:38 +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
          1229098

          Summary
          systemd: container networkd config files need to be in networ=
k subpackage

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          systemd-maintainers@suse.de

          Reporter
          lnussel@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

https://build.opensuse.org/p=
ackage/rdiff/openSUSE:Factory/systemd?linkrev=3Dbase&rev=3D428
moved 80-container-host0.network from the network subpackage to the contain=
er
subpackage. This breaks networking in machined containers. The file is need=
ed
inside the containers, not on the host. Inside containers, machined etc tha=
t is
in the systemd-containers package is not required.

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

You are on the CC list for the bug.

=

--17235345980.bcd6A82.431--


--17235661601.634FC.1636
Date: Tue, 13 Aug 2024 16:22:40 +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=3D1229119

            Bug ID: 1229119
           Summary: Netdata is partially closed source and thus should not be in the main repos
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: waffshappen-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Netdata ships a "v2" Dashboard that uses closed source blobs built from a
private repo licensed under a new (non FLOSS) NCUL1 License

License
https://github.com/netdata/netdata/blob/master/src/web/gui/v2/LICENSE.md
Blobs https://github.com/netdata/netdata/tree/master/src/web/gui/v2

which are required to build.

Thus it should not be included in the openSUSE repos.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17235661601.634FC.1636
Date: Tue, 13 Aug 2024 16:22:40 +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
          1229119

          Summary
          Netdata is partially closed source and thus should not be in =
the main repos

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Network

          Assignee
          screening-team-bugs@suse.de

          Reporter
          waffshappen@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Netdata ships a "v2" Dashboard that uses closed so=
urce blobs built from a
private repo licensed under a new (non FLOSS) NCUL1 License

License
https://github.com/netdata/netdata/blob/master/src/web/gui/v2/LIC=
ENSE.md
Blobs https://github.com/netdata/netdata/tree/master/src/web/gui/v2

which are required to build.

Thus it should not be included in the openSUSE repos.

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

You are on the CC list for the bug.

=

--17235661601.634FC.1636--


body:
--17235770231.eEcC4Ad.1900
Date: Tue, 13 Aug 2024 19:23:43 +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=3D1229122

            Bug ID: 1229122
           Summary: go1.23 release tracking
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: jkowalczyk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

go1.23 (expected August 2024) is a major release of Go.
Minor releases of go1.23.x will be provided through August 2025.
This issue tracks go1.23.x releases packaged and submitted initially
to openSUSE:Factory and can be referenced in submissions to
additional repositories.

Go Release Cycle
https://github.com/golang/go/wiki/Go-Release-Cycle

Go Release history
https://golang.org/doc/devel/release.html
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17235770231.eEcC4Ad.1900
Date: Tue, 13 Aug 2024 19:23:43 +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
          1229122

          Summary
          go1.23 release tracking

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Development

          Assignee
          screening-team-bugs@suse.de

          Reporter
          jkowalczyk@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

go1.23 (expected August 2024) is a major release of Go.
Minor releases of go1.23.x will be provided through August 2025.
This issue tracks go1.23.x releases packaged and submitted initially
to openSUSE:Factory and can be referenced in submissions to
additional repositories.

Go Release Cycle
https://gith=
ub.com/golang/go/wiki/Go-Release-Cycle

Go Release history
https://golang.org/do=
c/devel/release.html

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

You are on the CC list for the bug.

=

--17235770231.eEcC4Ad.1900--

summary: go1.23 release tracking


--17235865412.3EC10aE.2002
Date: Tue, 13 Aug 2024 22:02:21 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1229123
           Summary: Severe Graphics Regression On AMDGPU 6.10.3
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Kernel:Drivers
          Assignee: kernel-bugs-at-suse.de
          Reporter: mcdonald.w-at-icloud.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

There seems to be something very odd happening in the AMDGPU driver in
Tumbleweed's kernel as of 6.10.x.

The easiest and fastest path to see this bug is to use a last or current
generation AMDGPU card. Fire up a fresh install of Tumbleweed and install G=
IMP
or Hexchat.

Using HexChat as an example - open terminal let top run. Then go to HexChat=
 and
resize the "Connect to server window" a couple of times. You'll start to no=
tice
the "XWayland" CPU usage begin to steadily climb till it reaches 80-90% of =
the
CPU and RAM. Video performance will be - to put it bluntly; 1990s AOL lite.=
 The
issue will not stop until you reboot.

Running virtually any GPU intensive app such as Doom Eternal on Steam will =
see
the GPU performance crawl to virtual uselessness. It's at least a 30-40%
degradation in performance. Again, the first few seconds will be fine - then
it'll start.

I'm not an engineer so I don't know how to provide any relevant data to pro=
blem
such as this but I'm amenable to helping if there's data that needs to be
grabbed.

In the meantime, the only workable solution is to install the LTS kernel 6.=
6.x
and use that.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17235865412.3EC10aE.2002
Date: Tue, 13 Aug 2024 22:02:21 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1229123

          Summary
          Severe Graphics Regression On AMDGPU 6.10.3

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Kernel:Drivers

          Assignee
          kernel-bugs@suse.de

          Reporter
          mcdonald.w@icloud.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

There seems to be something very odd happening in the AMDGPU=
 driver in
Tumbleweed's kernel as of 6.10.x.

The easiest and fastest path to see this bug is to use a last or current
generation AMDGPU card. Fire up a fresh install of Tumbleweed and install G=
IMP
or Hexchat.

Using HexChat as an example - open terminal let top run. Then go to HexChat=
 and
resize the "Connect to server window" a couple of times. You'll s=
tart to notice
the "XWayland" CPU usage begin to steadily climb till it reaches =
80-90% of the
CPU and RAM. Video performance will be - to put it bluntly; 1990s AOL lite.=
 The
issue will not stop until you reboot.

Running virtually any GPU intensive app such as Doom Eternal on Steam will =
see
the GPU performance crawl to virtual uselessness. It's at least a 30-40%
degradation in performance. Again, the first few seconds will be fine - then
it'll start.

I'm not an engineer so I don't know how to provide any relevant data to pro=
blem
such as this but I'm amenable to helping if there's data that needs to be
grabbed.

In the meantime, the only workable solution is to install the LTS kernel 6.=
6.x
and use that.

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

You are on the CC list for the bug.

=

--17235865412.3EC10aE.2002--


--17236522710.f7b0aB.769
Date: Wed, 14 Aug 2024 16:17:51 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1229150
           Summary: mysql-connector-java: nullpointer exception after upgrade to 8.4.0 with package provided by sle repo
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: x86-64
                OS: openSUSE Leap 15.5
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: eduard-at-rysavy.net
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

After upgrading mysql-connector-java from 8.0.33 to 8.4.0-150200.3.21.1 (fr=
om
repo http://download.opensuse.org/update/leap/15.5/sle/), initializing a
database connection (w/o configuring telemetry) using this JDBC driver lead=
s to
the following error message:

java.lang.NullPointerException: Cannot invoke
"com.mysql.cj.telemetry.TelemetryHandler.startSpan(com.mysql.cj.telemetry.T=
elemetrySpanName,
Object[])" because the return value of
"com.mysql.cj.NativeSession.getTelemetryHandler()" is null
        at com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:392)
        at
com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:234)
        at
com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:18=
0)
        at
java.sql/java.sql.DriverManager.getConnection(DriverManager.java:683)
        at
java.sql/java.sql.DriverManager.getConnection(DriverManager.java:253)
        at MysqlConnTest.main(MysqlConnTest.java:8)

Replacing the file /usr/share/java/mysql-connector-j.jar provided by the
package by the latest version of 8.4.0 found in the maven repository (dated
April 30, 2024) resolves the issue
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17236522710.f7b0aB.769
Date: Wed, 14 Aug 2024 16:17:51 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1229150

          Summary
          mysql-connector-java: nullpointer exception after upgrade to =
8.4.0 with package provided by sle repo

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          x86-64

          OS
          openSUSE Leap 15.5

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          eduard@rysavy.net

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

After upgrading mysql-connector-java from 8.0.33 to 8.4.0-15=
0200.3.21.1 (from
repo http://=
download.opensuse.org/update/leap/15.5/sle/), initializing a
database connection (w/o configuring telemetry) using this JDBC driver lead=
s to
the following error message:

java.lang.NullPointerException: Cannot invoke
"com.mysql.cj.telemetry.TelemetryHandler.startSpan(com.mysql.cj.teleme=
try.TelemetrySpanName,
Object[])" because the return value of
"com.mysql.cj.NativeSession.getTelemetryHandler()" is null
        at com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.jav=
a:392)
        at
com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:234)
        at
com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:18=
0)
        at
java.sql/java.sql.DriverManager.getConnection(DriverManager.java:683)
        at
java.sql/java.sql.DriverManager.getConnection(DriverManager.java:253)
        at MysqlConnTest.main(MysqlConnTest.java:8)

Replacing the file /usr/share/java/mysql-connector-j.jar provided by the
package by the latest version of 8.4.0 found in the maven repository (dated
April 30, 2024) resolves the issue

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

You are on the CC list for the bug.

=

--17236522710.f7b0aB.769--


body:
--17236560942.9Fe5C1c.1228
Date: Wed, 14 Aug 2024 17:21:34 +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=3D1229153

            Bug ID: 1229153
           Summary: [SELinux] syslog-ng AVCs
    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: pallaswept-at-proton.me
        QA Contact: security-team-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Operating System: openSUSE Tumbleweed
SELinux status, mode and policy name: Enabled, enforcing. targeted
SELinux policy version and repository: 20240809-1.1 repo-oss
The software (incl. version) that is affected by the SELinux issue and the
error message: syslog-ng 4.8.0
SELinux Audit log:=20

Relevant AVCs (duplicates removed)

type=3DAVC msg=3Daudit(1723653703.528:658): avc:  denied  { write } for  pi=
d=3D9081
comm=3D"syslog-ng" path=3D"/dev/xconsole" dev=3D"devtmpfs" ino=3D1366
scontext=3Dsystem_u:system_r:syslogd_t:s0 tcontext=3Dsystem_u:object_r:devi=
ce_t:s0
tclass=3Dfifo_file permissive=3D0
type=3DAVC msg=3Daudit(1723653849.582:66): avc:  denied  { execmem } for  p=
id=3D9013
comm=3D"syslog-ng" scontext=3Dsystem_u:system_r:syslogd_t:s0
tcontext=3Dsystem_u:system_r:syslogd_t:s0 tclass=3Dprocess permissive=3D0
type=3DAVC msg=3Daudit(1723653849.977:72): avc:  denied  { watch } for  pid=
=3D9013
comm=3D"syslog-ng" path=3D"/etc/syslog-ng" dev=3D"nvme0n1p2" ino=3D544444
scontext=3Dsystem_u:system_r:syslogd_t:s0 tcontext=3Dsystem_u:object_r:etc_=
t:s0
tclass=3Ddir permissive=3D0
type=3DAVC msg=3Daudit(1723653849.980:73): avc:  denied  { getattr } for  p=
id=3D9013
comm=3D"syslog-ng" path=3D"/dev/xconsole" dev=3D"devtmpfs" ino=3D1372
scontext=3Dsystem_u:system_r:syslogd_t:s0 tcontext=3Dsystem_u:object_r:devi=
ce_t:s0
tclass=3Dfifo_file permissive=3D0
type=3DAVC msg=3Daudit(1723653909.985:166): avc:  denied  { getattr } for  =
pid=3D9013
comm=3D"syslog-ng" path=3D"/dev/xconsole" dev=3D"devtmpfs" ino=3D1372
scontext=3Dsystem_u:system_r:syslogd_t:s0 tcontext=3Dsystem_u:object_r:devi=
ce_t:s0
tclass=3Dfifo_file permissive=3D0

Any other important details: You have an awesome day
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17236560942.9Fe5C1c.1228
Date: Wed, 14 Aug 2024 17:21:34 +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
          1229153

          Summary
          [SELinux] syslog-ng AVCs

          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
          pallaswept@proton.me

          QA Contact
          security-team@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Operating System: openSUSE Tumbleweed
SELinux status, mode and policy name: Enabled, enforcing. targeted
SELinux policy version and repository: 20240809-1.1 repo-oss
The software (incl. version) that is affected by the SELinux issue and the
error message: syslog-ng 4.8.0
SELinux Audit log:=20

Relevant AVCs (duplicates removed)

type=3DAVC msg=3Daudit(1723653703.528:658): avc:  denied  { write } for  pi=
d=3D9081
comm=3D"syslog-ng" path=3D"/dev/xconsole" dev=3D"d=
evtmpfs" ino=3D1366
scontext=3Dsystem_u:system_r:syslogd_t:s0 tcontext=3Dsystem_u:object_r:devi=
ce_t:s0
tclass=3Dfifo_file permissive=3D0
type=3DAVC msg=3Daudit(1723653849.582:66): avc:  denied  { execmem } for  p=
id=3D9013
comm=3D"syslog-ng" scontext=3Dsystem_u:system_r:syslogd_t:s0
tcontext=3Dsystem_u:system_r:syslogd_t:s0 tclass=3Dprocess permissive=3D0
type=3DAVC msg=3Daudit(1723653849.977:72): avc:  denied  { watch } for  pid=
=3D9013
comm=3D"syslog-ng" path=3D"/etc/syslog-ng" dev=3D"=
nvme0n1p2" ino=3D544444
scontext=3Dsystem_u:system_r:syslogd_t:s0 tcontext=3Dsystem_u:object_r:etc_=
t:s0
tclass=3Ddir permissive=3D0
type=3DAVC msg=3Daudit(1723653849.980:73): avc:  denied  { getattr } for  p=
id=3D9013
comm=3D"syslog-ng" path=3D"/dev/xconsole" dev=3D"d=
evtmpfs" ino=3D1372
scontext=3Dsystem_u:system_r:syslogd_t:s0 tcontext=3Dsystem_u:object_r:devi=
ce_t:s0
tclass=3Dfifo_file permissive=3D0
type=3DAVC msg=3Daudit(1723653909.985:166): avc:  denied  { getattr } for  =
pid=3D9013
comm=3D"syslog-ng" path=3D"/dev/xconsole" dev=3D"d=
evtmpfs" ino=3D1372
scontext=3Dsystem_u:system_r:syslogd_t:s0 tcontext=3Dsystem_u:object_r:devi=
ce_t:s0
tclass=3Dfifo_file permissive=3D0

Any other important details: You have an awesome day

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

You are on the CC list for the bug.

=

--17236560942.9Fe5C1c.1228--

summary: [SELinux] syslog-ng AVCs


--17236930572.D825aaf.1585
Date: Thu, 15 Aug 2024 03:37:37 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1229161
           Summary: opensuse/microos-docserv broken, fails on 70-create-self-signed-certificates.sh due to missing `hostname` binary
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Containers
          Assignee: containers-bugowner-at-suse.de
          Reporter: io-at-mikelpr.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

opensuse/microos-docserv:latest (:20240320) is currently broken, as
docker-entrypoint.sh executes
/docker-entrypoint.d/70-create-self-signed-certificates.sh (from the
docserv-config-nginx package) on startup which tries to call `hostname` whi=
ch
is not included in the image.

fix could be either docserv-config-nginx requiring hostname (seems more
proper), or installing hostname on the zypper install step of
microos-docserv-image's Dockerfile

output:
$ podman run -it --rm -p 8000:80
registry.opensuse.org/opensuse/microos-docserv:latest
/usr/local/bin/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, wi=
ll
attempt to perform configuration
/usr/local/bin/docker-entrypoint.sh: Looking for shell scripts in
/docker-entrypoint.d/
/usr/local/bin/docker-entrypoint.sh: Launching
/docker-entrypoint.d/20-envsubst-on-templates.sh
/usr/local/bin/docker-entrypoint.sh: Launching
/docker-entrypoint.d/30-tune-worker-processes.sh
/usr/local/bin/docker-entrypoint.sh: Launching
/docker-entrypoint.d/70-create-self-signed-certificates.sh
/docker-entrypoint.d/70-create-self-signed-certificates.sh: line 18: hostna=
me:
command not found
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17236930572.D825aaf.1585
Date: Thu, 15 Aug 2024 03:37:37 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          <a class=3D"bz_bug_link=20
          bz_status_NEW "
   title=3D"NEW - opensuse/microos-docserv broken, fails on 70-create-self-=
signed-certificates.sh due to missing `hostname` binary"
   href=3D"https://bugzilla.suse.com/show_bug.cgi?id=3D1229161">1229161

          Summary
          opensuse/microos-docserv broken, fails on 70-create-self-sign=
ed-certificates.sh due to missing `hostname` binary

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          All

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Containers

          Assignee
          containers-bugowner@suse.de

          Reporter
          io@mikelpr.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

opensuse/microos-docserv:latest (:20240320) is currently bro=
ken, as
docker-entrypoint.sh executes
/docker-entrypoint.d/70-create-self-signed-certificates.sh (from the
docserv-config-nginx package) on startup which tries to call `hostname` whi=
ch
is not included in the image.

fix could be either docserv-config-nginx requiring hostname (seems more
proper), or installing hostname on the zypper install step of
microos-docserv-image's Dockerfile

output:
$ podman run -it --rm -p 8000:80
registry.opensuse.org/opensuse/microos-docserv:latest
/usr/local/bin/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, wi=
ll
attempt to perform configuration
/usr/local/bin/docker-entrypoint.sh: Looking for shell scripts in
/docker-entrypoint.d/
/usr/local/bin/docker-entrypoint.sh: Launching
/docker-entrypoint.d/20-envsubst-on-templates.sh
/usr/local/bin/docker-entrypoint.sh: Launching
/docker-entrypoint.d/30-tune-worker-processes.sh
/usr/local/bin/docker-entrypoint.sh: Launching
/docker-entrypoint.d/70-create-self-signed-certificates.sh
/docker-entrypoint.d/70-create-self-signed-certificates.sh: line 18: hostna=
me:
command not found

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

You are on the CC list for the bug.

=

--17236930572.D825aaf.1585--


body:
--17238514831.E2beF.619
Date: Fri, 16 Aug 2024 23:38:03 +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=3D1229268

            Bug ID: 1229268
           Summary: Screen reader support
    Classification: openSUSE
           Product: openSUSE Aeon
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: Base
          Assignee: rbrown-at-suse.com
          Reporter: ab.serv-at-mailbox.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

This is a helpful accessibility option for those who may have difficulty
reading text.

Examples of screen readers:
- Terminal: 'speakup'
- GUI: Orca

TTS:
- Speech dispatcher
- Festival
- Piper/Pied
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17238514831.E2beF.619
Date: Fri, 16 Aug 2024 23:38:03 +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
          1229268

          Summary
          Screen reader support

          Classification
          openSUSE

          Product
          openSUSE Aeon

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Enhancement

          Priority
          P5 - None

          Component
          Base

          Assignee
          rbrown@suse.com

          Reporter
          ab.serv@mailbox.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

This is a helpful accessibility option for those who may hav=
e difficulty
reading text.

Examples of screen readers:
- Terminal: 'speakup'
- GUI: Orca

TTS:
- Speech dispatcher
- Festival
- Piper/Pied

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

You are on the CC list for the bug.

=

--17238514831.E2beF.619--

pkgs: patterns-aeon patterns-tik

summary: Screen reader support


--17239297932.0c3E442D.163
Date: Sat, 17 Aug 2024 21:23:13 +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=3D1229277

            Bug ID: 1229277
           Summary: Package fakechroot does not build with GCC 14 because of new errors (that were previously warnings)
    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: mjambor-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: aavindraa-at-gmail.com
            Blocks: 1220571
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Package fakechroot fails to build with GCC 14 because of various C99
violations which previously just generated warning s but which cause
errors with GCC 14 by default.  For more information see
https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571.

BuildService failures are available online at:
https://build.opensuse.org/package/live_build_log/home:rguenther:plgrnd/fak=
echroot/openSUSE_Factory/x86_64

The build with GCC 14 can now be tried locally with:
osc build --clean --alternative-project home:rguenther:nextgcc

The (first) error that stops the build is:

[   45s] libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3D3 -fstack-protector-strong=20
-funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection
-Werror=3Dreturn-type -g -c ftw64.c  -fPIC -DPIC -o .libs/ftw6
4.o
[   45s] ftw.c: In function =E2=80=98process_entry=E2=80=99:
[   45s] ftw64.c:37:20: error: implicit declaration of function =E2=80=98__=
fxstatat64=E2=80=99;
did you mean =E2=80=98fstatat64=E2=80=99? [-Wimplicit-function-dec
laration]
[   45s]    37 | #  define FXSTATAT __fxstatat64
[   45s]       |                    ^~~~~~~~~~~~
[   45s] ftw.c:466:15: note: in expansion of macro =E2=80=98FXSTATAT=E2=80=
=99
[   45s]   466 |     statres =3D FXSTATAT (_STAT_VER, dir->streamfd, name, =
&st,
[   45s]       |               ^~~~~~~~
[   45s] ftw64.c:35:18: error: implicit declaration of function =E2=80=98__=
lxstat64=E2=80=99;
did you mean =E2=80=98lstat64=E2=80=99? [-Wimplicit-function-declaration]
[   45s]    35 | #  define LXSTAT __lxstat64
[   45s]       |                  ^~~~~~~~~~
[   45s] ftw.c:474:20: note: in expansion of macro =E2=80=98LXSTAT=E2=80=99
[   45s]   474 |                  ? LXSTAT (_STAT_VER, name, &st)
[   45s]       |                    ^~~~~~
[   45s] ftw64.c:36:17: error: implicit declaration of function =E2=80=98__=
xstat64=E2=80=99;
did you mean =E2=80=98lstat64=E2=80=99? [-Wimplicit-function-declaration]
[   45s]    36 | #  define XSTAT __xstat64
[   45s]       |                 ^~~~~~~~~
[   45s] ftw.c:475:20: note: in expansion of macro =E2=80=98XSTAT=E2=80=99
[   45s]   475 |                  : XSTAT (_STAT_VER, name, &st));
[   45s]       |                    ^~~~~
[   45s] make[2]: *** [Makefile:904: ftw64.lo] Error 1
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17239297932.0c3E442D.163
Date: Sat, 17 Aug 2024 21:23:13 +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
          1229277

          Summary
          Package fakechroot does not build with GCC 14 because of new =
errors (that were previously warnings)

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

          QA Contact
          qa-bugs@suse.de

          CC
          aavindraa@gmail.com

          Blocks
          1220571

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Package fakechroot fails to build with GCC 14 because of var=
ious C99
violations which previously just generated warning s but which cause
errors with GCC 14 by default.  For more information see
https://gcc.gnu.org/=
gcc-14/porting_to.html and meta bug #1220571.

BuildService failures are available online at:
https://build.opensuse.org/pack=
age/live_build_log/home:rguenther:plgrnd/fakechroot/openSUSE_Factory/x86_64=

The build with GCC 14 can now be tried locally with:
osc build --clean --alternative-project home:rguenther:nextgcc

The (first) error that stops the build is:

[   45s] libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3D3 -fstack-protector-strong=20
-funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection
-Werror=3Dreturn-type -g -c ftw64.c  -fPIC -DPIC -o .libs/ftw6
4.o
[   45s] ftw.c: In function =E2=80=98process_entry=E2=80=99:
[   45s] ftw64.c:37:20: error: implicit declaration of function =E2=80=98__=
fxstatat64=E2=80=99;
did you mean =E2=80=98fstatat64=E2=80=99? [-Wimplicit-function-dec
laration]
[   45s]    37 | #  define FXSTATAT __fxstatat64
[   45s]       |                    ^~~~~~~~~~~~
[   45s] ftw.c:466:15: note: in expansion of macro =E2=80=98FXSTATAT=E2=80=
=99
[   45s]   466 |     statres =3D FXSTATAT (_STAT_VER, dir->streamfd, nam=
e, &st,
[   45s]       |               ^~~~~~~~
[   45s] ftw64.c:35:18: error: implicit declaration of function =E2=80=98__=
lxstat64=E2=80=99;
did you mean =E2=80=98lstat64=E2=80=99? [-Wimplicit-function-declaration]
[   45s]    35 | #  define LXSTAT __lxstat64
[   45s]       |                  ^~~~~~~~~~
[   45s] ftw.c:474:20: note: in expansion of macro =E2=80=98LXSTAT=E2=80=99
[   45s]   474 |                  ? LXSTAT (_STAT_VER, name, &st)
[   45s]       |                    ^~~~~~
[   45s] ftw64.c:36:17: error: implicit declaration of function =E2=80=98__=
xstat64=E2=80=99;
did you mean =E2=80=98lstat64=E2=80=99? [-Wimplicit-function-declaration]
[   45s]    36 | #  define XSTAT __xstat64
[   45s]       |                 ^~~~~~~~~
[   45s] ftw.c:475:20: note: in expansion of macro =E2=80=98XSTAT=E2=80=99
[   45s]   475 |                  : XSTAT (_STAT_VER, name, &st));
[   45s]       |                    ^~~~~
[   45s] make[2]: *** [Makefile:904: ftw64.lo] Error 1

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

You are on the CC list for the bug.

=

--17239297932.0c3E442D.163--


body:
--17240591562.7f5CfA.227
Date: Mon, 19 Aug 2024 09:19:16 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1229338
           Summary: ffmpeg fails to build on 32bit arm
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/4414868/modules/star
                    t_install/steps/3
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: jengelh-at-inai.de
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

ffmpeg-6 and ffmpeg-7 fail to build on armv6hl as well as armv7hl, turning
desktops uninstallable.

This patch should fix it:

https://git.videolan.org/?p=3Dffmpeg.git;a=3Dpatch;h=3D654bd47716c4f36719fb=
0f3f7fd8386d5ed0b916

## Observation

openQA test in scenario opensuse-Tumbleweed-NET-arm-install_only@aarch32 fa=
ils
in
[start_install](https://openqa.opensuse.org/tests/4414868/modules/start_ins=
tall/steps/3)

## Test suite description
set HDDSIZE=3D40 as required for ppc64le (failed w/o it on
https://openqa.opensuse.org/tests/390330#step/install_and_reboot/21

## Reproducible

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

## Expected result

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

## Further details

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

--17240591562.7f5CfA.227
Date: Mon, 19 Aug 2024 09:19:16 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1229338

          Summary
          ffmpeg fails to build on 32bit arm

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          URL
          https://openqa.opensuse.org/tests/4414868/modules/start_insta=
ll/steps/3

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          jengelh@inai.de

          Reporter
          fvogt@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

ffmpeg-6 and ffmpeg-7 fail to build on armv6hl as well as ar=
mv7hl, turning
desktops uninstallable.

This patch should fix it:

https://git.videolan.org/?p=3Dffmpeg.git;a=
=3Dpatch;h=3D654bd47716c4f36719fb0f3f7fd8386d5ed0b916

## Observation

openQA test in scenario opensuse-Tumbleweed-NET-arm-install_only@aarch3=
2 fails
in
[start_install](https://openqa.opensuse.org/tests/4414868/modules/=
start_install/steps/3)

## Test suite description
set HDDSIZE=3D40 as required for ppc64le (failed w/o it on
https://openqa.opensuse.org/tests/390330#step/install_and_reboot/21

## Reproducible

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

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?a=
rch=3Darm&distri=3Dopensuse&flavor=3DNET&machine=3Daarch32&=
test=3Dinstall_only&version=3DTumbleweed)

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

You are on the CC list for the bug.

=

--17240591562.7f5CfA.227--

summary: ffmpeg fails to build on 32bit arm


body:
--17240763781.a21cD.2387
Date: Mon, 19 Aug 2024 14:06:18 +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=3D1229426

            Bug ID: 1229426
           Summary: chromium 128 track
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: ro-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

fyi opening bug for communication

started work on a chromium-128 in=20
home:oertel:branches:network:chromium/chromium-beta

patching is done, compile is running.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17240763781.a21cD.2387
Date: Mon, 19 Aug 2024 14:06:18 +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
          1229426

          Summary
          chromium 128 track

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X11 Applications

          Assignee
          screening-team-bugs@suse.de

          Reporter
          ro@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

fyi opening bug for communication

started work on a chromium-128 in=20
home:oertel:branches:network:chromium/chromium-beta

patching is done, compile is running.

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

You are on the CC list for the bug.

=

--17240763781.a21cD.2387--

summary: chromium 128 track


--17241327050.647BF.185
Date: Tue, 20 Aug 2024 05:45:04 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1229450
           Summary: libbpf: failed to find '.BTF' ELF section in vmlinux
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 876820
  --> https://bugzilla.suse.com/attachment.cgi?id=3D876820&action=3Dedit
Devel:Kernel:master/kernel-source:kernel-vanilla/LEGACYX86/i586 build log

The kernel builds result in random build failures while creating BTF.

For example
https://build.opensuse.org/package/live_build_log/Kernel:vanilla/kernel-sou=
rce-vanilla:kernel-vanilla/ARM/armv7l:
> libbpf: failed to find '.BTF' ELF section in vmlinux
> FAILED: load BTF from vmlinux: No data available
> make[2]: *** [../scripts/Makefile.vmlinux:34: vmlinux] Error 255
> make[2]: *** Deleting file 'vmlinux'
> make[1]: *** [/home/abuild/rpmbuild/BUILD/kernel-vanilla-6.11~rc3.338.gc3=
f2d783a459/linux-6.11-rc3-338-gc3f2d783a459/Makefile:1158: vmlinux] Error 2
> make: *** [../Makefile:224: __sub-make] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.olf5Nu (%build)

arm seems to fail reliably.

But for example in
ibs://Devel:Kernel:master/kernel-source:kernel-vanilla/LEGACYX86/i586, it l=
ooks
like it is sort of random. kernel-debug and kernel-vanilla fails for i586, =
but
-default and -pae are built currently. See the job history for kernel-vanil=
la
in there (the failed boot log is attached):
> time                 package                       reason           code =
      build time      worker=20
> 2024-07-15 07:41:48  kernel-source:kernel-vanilla  source change    succe=
eded        47m 53s   h01-ch5a:3=20=20=20=20=20=20
> 2024-07-15 23:56:48  kernel-source:kernel-vanilla  source change    succe=
eded        47m 57s   h01-ch5b:5=20=20=20=20=20=20
> 2024-07-18 11:12:40  kernel-source:kernel-vanilla  source change    succe=
eded        48m 46s   h01-ch5b:2=20=20=20=20=20=20
> 2024-07-26 20:01:29  kernel-source:kernel-vanilla  source change    succe=
eded        52m 40s   h01-ch4b:2=20=20=20=20=20=20
> 2024-07-29 09:07:35  kernel-source:kernel-vanilla  source change    succe=
eded        52m 53s   h01-ch4a:6=20=20=20=20=20=20
> 2024-08-03 11:38:55  kernel-source:kernel-vanilla  source change    faile=
d           25m 16s   h01-ch4b:8=20=20=20=20=20=20
> 2024-08-04 23:48:15  kernel-source:kernel-vanilla  source change    faile=
d           25m 14s   h01-ch4b:7=20=20=20=20=20=20
> 2024-08-06 16:37:35  kernel-source:kernel-vanilla  source change    succe=
eded        53m 25s   h01-ch4b:4=20=20=20=20=20=20
> 2024-08-09 19:44:44  kernel-source:kernel-vanilla  source change    faile=
d           26m  4s   h01-ch5a:2=20=20=20=20=20=20
> 2024-08-11 22:48:56  kernel-source:kernel-vanilla  source change    faile=
d            0m 38s   h01-ch4b:6=20=20=20=20=20=20
> 2024-08-12 16:44:52  kernel-source:kernel-vanilla  source change    succe=
eded        54m  0s   h01-ch5b:5=20=20=20=20=20=20
> 2024-08-15 21:49:11  kernel-source:kernel-vanilla  source change    faile=
d           25m 25s   h01-ch4b:1=20=20=20=20=20=20
> 2024-08-19 01:53:01  kernel-source:kernel-vanilla  source change    succe=
eded        50m  9s   h01-ch4a:5=20=20=20=20=20=20
> 2024-08-19 11:33:50  kernel-source:kernel-vanilla  source change    succe=
eded        55m  9s   h01-ch5b:1=20=20=20=20=20=20
> 2024-08-19 17:23:59  kernel-source:kernel-vanilla  source change    faile=
d           25m 16s   h01-ch5a:3
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17241327050.647BF.185
Date: Tue, 20 Aug 2024 05:45:05 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1229450

          Summary
          libbpf: failed to find '.BTF' ELF section in vmlinux

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          jslaby@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 876820 [details]
Devel:Kernel:master/kernel-source:kernel-vanilla/LEGACYX86/i586 build log

The kernel builds result in random build failures while creating BTF.

For example
https://build.opensuse.or=
g/package/live_build_log/Kernel:vanilla/kernel-source-vanilla:kernel-vanill=
a/ARM/armv7l:
> libbpf: failed to find '.BTF' ELF section in vml=
inux
> FAILED: load BTF from vmlinux: No data available
> make[2]: *** [../scripts/Makefile.vmlinux:34: vmlinux] Error 255
> make[2]: *** Deleting file 'vmlinux'
> make[1]: *** [/home/abuild/rpmbuild/BUILD/kernel-vanilla-6.11~rc3.338.=
gc3f2d783a459/linux-6.11-rc3-338-gc3f2d783a459/Makefile:1158: vmlinux] Erro=
r 2
> make: *** [../Makefile:224: __sub-make] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.olf5Nu (%build)

arm seems to fail reliably.

But for example in
ibs://Devel:Kernel:master/kernel-source:kernel-vanilla/LEGACYX86/i586, it l=
ooks
like it is sort of random. kernel-debug and kernel-vanilla fails for i586, =
but
-default and -pae are built currently. See the job history for kernel-vanil=
la
in there (the failed boot log is attached):
> time                 package                    =
   reason           code       build time      worker=20
> 2024-07-15 07:41:48  kernel-source:kernel-vanilla  source change    su=
cceeded        47m 53s   h01-ch5a:3=20=20=20=20=20=20
> 2024-07-15 23:56:48  kernel-source:kernel-vanilla  source change    su=
cceeded        47m 57s   h01-ch5b:5=20=20=20=20=20=20
> 2024-07-18 11:12:40  kernel-source:kernel-vanilla  source change    su=
cceeded        48m 46s   h01-ch5b:2=20=20=20=20=20=20
> 2024-07-26 20:01:29  kernel-source:kernel-vanilla  source change    su=
cceeded        52m 40s   h01-ch4b:2=20=20=20=20=20=20
> 2024-07-29 09:07:35  kernel-source:kernel-vanilla  source change    su=
cceeded        52m 53s   h01-ch4a:6=20=20=20=20=20=20
> 2024-08-03 11:38:55  kernel-source:kernel-vanilla  source change    fa=
iled           25m 16s   h01-ch4b:8=20=20=20=20=20=20
> 2024-08-04 23:48:15  kernel-source:kernel-vanilla  source change    fa=
iled           25m 14s   h01-ch4b:7=20=20=20=20=20=20
> 2024-08-06 16:37:35  kernel-source:kernel-vanilla  source change    su=
cceeded        53m 25s   h01-ch4b:4=20=20=20=20=20=20
> 2024-08-09 19:44:44  kernel-source:kernel-vanilla  source change    fa=
iled           26m  4s   h01-ch5a:2=20=20=20=20=20=20
> 2024-08-11 22:48:56  kernel-source:kernel-vanilla  source change    fa=
iled            0m 38s   h01-ch4b:6=20=20=20=20=20=20
> 2024-08-12 16:44:52  kernel-source:kernel-vanilla  source change    su=
cceeded        54m  0s   h01-ch5b:5=20=20=20=20=20=20
> 2024-08-15 21:49:11  kernel-source:kernel-vanilla  source change    fa=
iled           25m 25s   h01-ch4b:1=20=20=20=20=20=20
> 2024-08-19 01:53:01  kernel-source:kernel-vanilla  source change    su=
cceeded        50m  9s   h01-ch4a:5=20=20=20=20=20=20
> 2024-08-19 11:33:50  kernel-source:kernel-vanilla  source change    su=
cceeded        55m  9s   h01-ch5b:1=20=20=20=20=20=20
> 2024-08-19 17:23:59  kernel-source:kernel-vanilla  source change    fa=
iled           25m 16s   h01-ch5a:3

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

You are on the CC list for the bug.

=

--17241327050.647BF.185--


--17242353732.a7DF1Cc.1118
Date: Wed, 21 Aug 2024 10:16:13 +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=3D1229555

            Bug ID: 1229555
           Summary: Wicked dummy interfaces no longer come up / "no-device"
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: georg.pfuetzenreuter-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 876866
  --> https://bugzilla.suse.com/attachment.cgi?id=3D876866&action=3Dedit
asgard2.i.o.o journal after boot

Hi,

we have various interfaces of type `dummy` configured on our openSUSE
infrastructure firewall VMs, so far with no issues.

They are all configured equally, here is one example:

```
# more /etc/sysconfig/network/ifcfg-d-os-code
# ... comments ...
STARTMODE=3D'auto'
BOOTPROTO=3D'none'
INTERFACETYPE=3D'dummy'
```

Since installing updates and rebooting today, they no longer come up (neith=
er
automatically nor manually through ifup), returning "no-device".

I will attach some information which I hope is useful ..
.. from after boot:
- `journalctl`
.. from after enabling WICKED_DEBUG=3Dall/WICKED_LOG_LEVEL=3Ddebug and rest=
arting
wickedd:
- `wicked --debug all ifup d-os-code`  # again just one example interface
- `wicked show-config`
- `wicked ifstatus --verbose all`
- `grep 2024-08-21 /var/log/zypp/history`

Let me know if anything of interest is missing.

Would appreciate any ideas! I'm reluctant to update the second machine in t=
he
pair with this issue.

There is another (presumably kernel) issue after the update, which I think =
is
not related and hence reported separately at
https://bugzilla.opensuse.org/show_bug.cgi?id=3D1229552.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17242353732.a7DF1Cc.1118
Date: Wed, 21 Aug 2024 10:16:13 +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
          1229555

          Summary
          Wicked dummy interfaces no longer come up / "no-device&q=
uot;

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Network

          Assignee
          screening-team-bugs@suse.de

          Reporter
          georg.pfuetzenreuter@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attac=
hment 876866 [details]
asgard2.i.o.o journal after boot

Hi,

we have various interfaces of type `dummy` configured on our openSUSE
infrastructure firewall VMs, so far with no issues.

They are all configured equally, here is one example:

```
# more /etc/sysconfig/network/ifcfg-d-os-code
# ... comments ...
STARTMODE=3D'auto'
BOOTPROTO=3D'none'
INTERFACETYPE=3D'dummy'
```

Since installing updates and rebooting today, they no longer come up (neith=
er
automatically nor manually through ifup), returning "no-device".

I will attach some information which I hope is useful ..
.. from after boot:
- `journalctl`
.. from after enabling WICKED_DEBUG=3Dall/WICKED_LOG_LEVEL=3Ddebug and rest=
arting
wickedd:
- `wicked --debug all ifup d-os-code`  # again just one example interface
- `wicked show-config`
- `wicked ifstatus --verbose all`
- `grep 2024-08-21 /var/log/zypp/history`

Let me know if anything of interest is missing.

Would appreciate any ideas! I'm reluctant to update the second machine in t=
he
pair with this issue.

There is another (presumably kernel) issue after the update, which I think =
is
not related and hence reported separately at
https:/=
/bugzilla.opensuse.org/show_bug.cgi?id=3D1229552.

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

You are on the CC list for the bug.

=

--17242353732.a7DF1Cc.1118--


body:
--17242584901.5fFc1DEd1.2002
Date: Wed, 21 Aug 2024 16:41:30 +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=3D1229587

            Bug ID: 1229587
           Summary: SELinux Audit log errors
    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: pj.opensuse-at-gmx.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 876880
  --> https://bugzilla.suse.com/attachment.cgi?id=3D876880&action=3Dedit
SELinux day audit log

Hi, noticing some errors in the SELinux audit log today. Can you please hel=
p me
decipher what's going on?

openSUSE Tumbleweed

sestatus
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   enforcing
Mode from config file:          enforcing
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Memory protection checking:     actual (secure)
Max kernel policy version:      33

zypper info selinux-policy
Loading repository data...
Reading installed packages...

Information for package selinux-policy:
---------------------------------------
Repository     : repo-oss
Name           : selinux-policy
Version        : 20240816-1.1
Arch           : noarch
Vendor         : openSUSE
Installed Size : 24.8 KiB
Installed      : Yes (automatically)
Status         : up-to-date
Source package : selinux-policy-20240816-1.1.src
Upstream URL   : https://github.com/fedora-selinux/selinux-policy.git
Summary        : SELinux policy configuration
Description    :=20
    A complete SELinux policy that can be used as the system policy for a
variety
    of systems and used as the basis for creating other policies.

ausearch -ts today -m avc

Log is attached to this report >=20

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

--17242584901.5fFc1DEd1.2002
Date: Wed, 21 Aug 2024 16:41:30 +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
          1229587

          Summary
          SELinux Audit log errors

          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
          pj.opensuse@gmx.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 87688=
0 [details]
SELinux day audit log

Hi, noticing some errors in the SELinux audit log today. Can you please hel=
p me
decipher what's going on?

openSUSE Tumbleweed

sestatus
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   enforcing
Mode from config file:          enforcing
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Memory protection checking:     actual (secure)
Max kernel policy version:      33

zypper info selinux-policy
Loading repository data...
Reading installed packages...

Information for package selinux-policy:
---------------------------------------
Repository     : repo-oss
Name           : selinux-policy
Version        : 20240816-1.1
Arch           : noarch
Vendor         : openSUSE
Installed Size : 24.8 KiB
Installed      : Yes (automatically)
Status         : up-to-date
Source package : selinux-policy-20240816-1.1.src
Upstream URL   : https://github.com/fedora-selinux/selinux-policy.git
Summary        : SELinux policy configuration
Description    :=20
    A complete SELinux policy that can be used as the system policy for a
variety
    of systems and used as the basis for creating other policies.

ausearch -ts today -m avc

Log is attached to this report >=20

-THanks

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

You are on the CC list for the bug.

=

--17242584901.5fFc1DEd1.2002--

summary: SELinux Audit log errors


--17242718503.BAC32aE9.86
Date: Wed, 21 Aug 2024 20:24: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=3D1229591

            Bug ID: 1229591
           Summary: VUL-0: chromium: multiple vulnerabilities fixed in 128.0.6613.84
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: Andreas.Stieger-at-gmx.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: gmbr3-at-opensuse.org, ro-at-suse.com, security-team-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

From
https://chromereleases.googleblog.com/2024/08/stable-channel-update-for-des=
ktop_21.html

CVE-2024-7964: Use after free in Passwords
CVE-2024-7965: Inappropriate implementation in V8
CVE-2024-7966: Out of bounds memory access in Skia
CVE-2024-7967: Heap buffer overflow in Fonts
CVE-2024-7968: Use after free in Autofill
CVE-2024-7969: Type Confusion in V8
CVE-2024-7971: Type confusion in V8
CVE-2024-7972: Inappropriate implementation in V8
CVE-2024-7973: Heap buffer overflow in PDFium
CVE-2024-7974: Insufficient data validation in V8 API
CVE-2024-7975: Inappropriate implementation in Permissions
CVE-2024-7976: Inappropriate implementation in FedCM
CVE-2024-7977: Insufficient data validation in Installer
CVE-2024-7978: Insufficient policy enforcement in Data Transfer
CVE-2024-7979: Insufficient data validation in Installer
CVE-2024-7980: Insufficient data validation in Installer
CVE-2024-7981: Inappropriate implementation in Views
CVE-2024-8033: Inappropriate implementation in WebApp Installs
CVE-2024-8034: Inappropriate implementation in Custom Tabs
CVE-2024-8035: Inappropriate implementation in Extensions
Various fixes from internal audits, fuzzing and other initiatives

Google is aware that an exploit for CVE-2024-7971 exists in the wild.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17242718503.BAC32aE9.86
Date: Wed, 21 Aug 2024 20:24: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
          1229591

          Summary
          VUL-0: chromium: multiple vulnerabilities fixed in 128.0.6613=
.84

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Security

          Assignee
          Andreas.Stieger@gmx.de

          Reporter
          Andreas.Stieger@gmx.de

          QA Contact
          qa-bugs@suse.de

          CC
          gmbr3@opensuse.org, ro@suse.com, security-team@su=
se.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

From
https://chromereleases.googleblog.com/2024/08/stab=
le-channel-update-for-desktop_21.html

CVE-2024-7964: Use after free in Passwords
CVE-2024-7965: Inappropriate implementation in V8
CVE-2024-7966: Out of bounds memory access in Skia
CVE-2024-7967: Heap buffer overflow in Fonts
CVE-2024-7968: Use after free in Autofill
CVE-2024-7969: Type Confusion in V8
CVE-2024-7971: Type confusion in V8
CVE-2024-7972: Inappropriate implementation in V8
CVE-2024-7973: Heap buffer overflow in PDFium
CVE-2024-7974: Insufficient data validation in V8 API
CVE-2024-7975: Inappropriate implementation in Permissions
CVE-2024-7976: Inappropriate implementation in FedCM
CVE-2024-7977: Insufficient data validation in Installer
CVE-2024-7978: Insufficient policy enforcement in Data Transfer
CVE-2024-7979: Insufficient data validation in Installer
CVE-2024-7980: Insufficient data validation in Installer
CVE-2024-7981: Inappropriate implementation in Views
CVE-2024-8033: Inappropriate implementation in WebApp Installs
CVE-2024-8034: Inappropriate implementation in Custom Tabs
CVE-2024-8035: Inappropriate implementation in Extensions
Various fixes from internal audits, fuzzing and other initiatives

Google is aware that an exploit for CVE-2024-7971 exists in the wild.

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

You are on the CC list for the bug.

=

--17242718503.BAC32aE9.86--


--17243133384.cDeC96d4.683
Date: Thu, 22 Aug 2024 07:55:38 +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=3D1229627

            Bug ID: 1229627
           Summary: black screen during and after startup in VMware-WebConsole
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: dirk.datzert-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

MicroOS-release-appliance-20240819-3058.1.x86_64
MicroOS-release-20240819-3058.1.x86_64
libvmtools0-12.4.5-1.2.x86_64

I did a daily update and via network. I switched my view to a Google Chrome=
 and
VMware-WebConsole to see boot prozess going forwarding and after some secon=
ds
the screen goes black. System self is running
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17243133384.cDeC96d4.683
Date: Thu, 22 Aug 2024 07:55:38 +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
          1229627

          Summary
          black screen during and after startup in VMware-WebConsole

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Virtualization:Tools

          Assignee
          virt-bugs@suse.de

          Reporter
          dirk.datzert@gmx.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

MicroOS-release-appliance-20240819-3058.1.x86_64
MicroOS-release-20240819-3058.1.x86_64
libvmtools0-12.4.5-1.2.x86_64

I did a daily update and via network. I switched my view to a Google Chrome=
 and
VMware-WebConsole to see boot prozess going forwarding and after some secon=
ds
the screen goes black. System self is running

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

You are on the CC list for the bug.

=

--17243133384.cDeC96d4.683--


body:
--17243216966.82454c3aC.1163
Date: Thu, 22 Aug 2024 10:14:56 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1229650
           Summary: openssh 9.8p1 issues
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: ana.guerrero-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

openssh 9.8p1 was accepted in Factory yesterday (SR#1194679).=20
While in Staging, a small update in the staging openQA was required
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/20010) but
sadly, after accepting the package in Factory, some of the openQA test to m=
ove
from Factory to Tumbleweed failed.=20

In these tests sshd / sshd-session seem to have issues with selinux:

* https://openqa.opensuse.org/tests/4422288#step/crypto_policies_tests/45=20
(Failed to start OpenSSH Daemon)
* https://openqa.opensuse.org/tests/4422289#step/aulast/27  (security audit
test fails)

There is also another one in microos test "journal_check"  where I'm not so
sure about selinux involvement:
https://openqa.opensuse.org/tests/4422252#step/journal_check/20
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17243216966.82454c3aC.1163
Date: Thu, 22 Aug 2024 10:14:56 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1229650

          Summary
          openssh 9.8p1 issues

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          ana.guerrero@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

openssh 9.8p1 was accepted in Factory yesterday (SR#1194679)=
.=20
While in Staging, a small update in the staging openQA was required
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2001=
0) but
sadly, after accepting the package in Factory, some of the openQA test to m=
ove
from Factory to Tumbleweed failed.=20

In these tests sshd / sshd-session seem to have issues with selinux:

* https://openqa.opensuse.org/tests/4422288#step/crypto_policies_t=
ests/45=20
(Failed to start OpenSSH Daemon)
* http=
s://openqa.opensuse.org/tests/4422289#step/aulast/27  (security audit
test fails)

There is also another one in microos test "journal_check"  where =
I'm not so
sure about selinux involvement:
https://openqa.opensuse.org/tests/4422252#step/journal_check/20

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

You are on the CC list for the bug.

=

--17243216966.82454c3aC.1163--

summary: openssh 9.8p1 issues


--17243442321.6d18a.181
Date: Thu, 22 Aug 2024 16:30: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=3D1229672

            Bug ID: 1229672
           Summary: VUL-0: CVE-2024-43785: gitoxide: newlines, backspaces and control characters that appear in metadata written to terminals are not neutralized
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/418576/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: dmueller-at-suse.com
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: camila.matos-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

gitoxide An idiomatic, lean, fast & safe pure Rust implementation of Git.
gitoxide-core, which provides most underlying functionality of the gix and =
ein
commands, does not neutralize newlines, backspaces, or control
characters=E2=80=94including those that form ANSI escape sequences=E2=80=94=
that appear in a
repository's paths, author and committer names, commit messages, or other
metadata. Such text may be written as part of the output of a command, as w=
ell
as appearing in error messages when an operation fails. This sometimes allo=
ws
an untrusted repository to misrepresent its contents and to alter or concoct
error messages.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-43785
https://www.cve.org/CVERecord?id=3DCVE-2024-43785
https://github.com/Byron/gitoxide/security/advisories/GHSA-88g2-r9rw-g55h
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17243442321.6d18a.181
Date: Thu, 22 Aug 2024 16:30: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
          1229672

          Summary
          VUL-0: CVE-2024-43785: gitoxide: newlines, backspaces and con=
trol characters that appear in metadata written to terminals are not neutra=
lized

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          dmueller@suse.com

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          camila.matos@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

gitoxide An idiomatic, lean, fast & safe pure Rust imple=
mentation of Git.
gitoxide-core, which provides most underlying functionality of the gix and =
ein
commands, does not neutralize newlines, backspaces, or control
characters=E2=80=94including those that form ANSI escape sequences=E2=80=94=
that appear in a
repository's paths, author and committer names, commit messages, or other
metadata. Such text may be written as part of the output of a command, as w=
ell
as appearing in error messages when an operation fails. This sometimes allo=
ws
an untrusted repository to misrepresent its contents and to alter or concoct
error messages.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-43785
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-43785
https://github.com/Byron/gitoxide/security/advisories/GHSA-88g2-=
r9rw-g55h

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

You are on the CC list for the bug.

=

--17243442321.6d18a.181--


body:
--17244457961.E47ee7.1579
Date: Fri, 23 Aug 2024 20:43:16 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1229714
           Summary: Kernel panic when saving via NFS
    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: Bugs.opensuse.2024.sw-at-muenzburg.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I use a current tumbleweed VM as NFS server with version 4.2.
Nearly every time a client (also opensuse tumbleweed) saves a document via =
NFS
share or moves files, the kernel crashes and I have to force reboot of the =
VM.

Waht information do you need?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17244457961.E47ee7.1579
Date: Fri, 23 Aug 2024 20:43:16 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1229714

          Summary
          Kernel panic when saving via NFS

          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
          Bugs.opensuse.2024.sw@muenzburg.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I use a current tumbleweed VM as NFS server with version 4.2.
Nearly every time a client (also opensuse tumbleweed) saves a document via =
NFS
share or moves files, the kernel crashes and I have to force reboot of the =
VM.

Waht information do you need?

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

You are on the CC list for the bug.

=

--17244457961.E47ee7.1579--

summary: Kernel panic when saving via NFS


--17246762082.a3Ba5a.926
Date: Mon, 26 Aug 2024 12:43:28 +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=3D1229745

            Bug ID: 1229745
           Summary: [Build 20240825] dbus-broker: no network after switchjing from NM to wicked
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/4434925/modules/prep
                    are_test_data/steps/13
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

## Observation

We have a few tests, that install a default GNOME setup (based on
NetworkManager), then switch to wicked:

After wicked has been started, the network stack seems not to be operational
though

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ui_devel@64bit
fails in
[prepare_test_data](https://openqa.opensuse.org/tests/4434925/modules/prepa=
re_test_data/steps/13)

## Test suite description
Maintainer: zluo

yast2 upstream test suites.

https://progress.opensuse.org/issues/20206

## Reproducible

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

## Expected result

Last good: [20240823](https://openqa.opensuse.org/tests/4430444) (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=3DDVD&machine=3D64bit&test=3Dyast2_ui_devel&version=3DTumblew=
eed)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17246762082.a3Ba5a.926
Date: Mon, 26 Aug 2024 12:43:28 +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
          1229745

          Summary
          [Build 20240825] dbus-broker: no network after switchjing fro=
m NM to wicked

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          URL
          https://openqa.opensuse.org/tests/4434925/modules/prepare_tes=
t_data/steps/13

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          dimstar@opensuse.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

## Observation

We have a few tests, that install a default GNOME setup (based on
NetworkManager), then switch to wicked:

After wicked has been started, the network stack seems not to be operational
though

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ui_devel@6=
4bit
fails in
[prepare_test_data](https://openqa.opensuse.org/tests/4434925=
/modules/prepare_test_data/steps/13)

## Test suite description
Maintainer: zluo

yast2 upstream test suites.

https://progress.ope=
nsuse.org/issues/20206

## Reproducible

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

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/lates=
t?arch=3Dx86_64&distri=3Dopensuse&flavor=3DDVD&machine=3D64bit&=
amp;test=3Dyast2_ui_devel&version=3DTumbleweed)

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

You are on the CC list for the bug.

=

--17246762082.a3Ba5a.926--