--17394594033.806ce8aBf.1060
Date: Thu, 13 Feb 2025 15:10: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=3D1237161

            Bug ID: 1237161
           Summary: Microphone never working on new ASUS Zenbook S 14 UX5406SA Lunar Lake
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: dimitpyr-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 880329
  --> https://bugzilla.suse.com/attachment.cgi?id=3D880329&action=3Dedit
It is the output from sudo /usr/sbin/alsa-info.sh --upload

I have trying to update all apps to latest, chose different input methods a=
nd
tested on various softwares, mic input is not working, neither found someth=
ing
to work temporarily.

uname --all
Linux localhost.localdomain 6.13.1-1-default #1 SMP PREEMPT_DYNAMIC Mon Feb=
  3
05:33:25 UTC 2025 (1918d13) x86_64 x86_64 x86_64 GNU/Linux

Full details on this link
http://alsa-project.org/db/?f=3D0511aaf3545c326ccf9ead00f9c004371fd8ad86 or=
 in
the attachment.=20

I would appriciate your input and contribution on this bug.
This issue prevent many users from having online meetings.=20

If you need anything more I will provide more details
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17394594033.806ce8aBf.1060
Date: Thu, 13 Feb 2025 15:10: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
          1237161

          Summary
          Microphone never working on new ASUS Zenbook S 14 UX5406SA Lu=
nar Lake

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Critical

          Priority
          P5 - None

          Component
          Sound

          Assignee
          tiwai@suse.com

          Reporter
          dimitpyr@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 880329 [details]
It is the output from sudo /usr/sbin/alsa-info.sh --upload

I have trying to update all apps to latest, chose different input methods a=
nd
tested on various softwares, mic input is not working, neither found someth=
ing
to work temporarily.

uname --all
Linux localhost.localdomain 6.13.1-1-default #1 SMP PREEMPT_DYNAMIC Mon Feb=
  3
05:33:25 UTC 2025 (1918d13) x86_64 x86_64 x86_64 GNU/Linux

Full details on this link
http://alsa-project.org/db/?f=3D0511aaf3545c326ccf9ead00f9c004371=
fd8ad86 or in
the attachment.=20

I would appriciate your input and contribution on this bug.
This issue prevent many users from having online meetings.=20

If you need anything more I will provide more details

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

You are on the CC list for the bug.

=

--17394594033.806ce8aBf.1060--


--17395206530.AcEF2A0.2258
Date: Fri, 14 Feb 2025 08:10:53 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1237182
           Summary: openSUSE Leap (15.6): LibreOffice (openSUSE regular release): insure build settings (compared to other applications)
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LibreOffice
          Assignee: screening-team-bugs-at-suse.de
          Reporter: Gunner.Gewiss-at-posteo.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Dear all!

Please compare:

~> checksec --file=3D/usr/lib64/libreoffice/program/soffice.bin
RELRO           STACK CANARY      NX            PIE             RPATH=20=20=
=20=20=20
RUNPATH      Symbols         FORTIFY Fortified       Fortifiable     FILE
Full RELRO      No canary found   NX enabled    No PIE          No RPATH=20=
=20
RUNPATH     No Symbols       N/A     0               0=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20
/usr/lib64/libreoffice/program/soffice.bin

to:

~> checksec --file=3D/usr/lib64/firefox/firefox-bin
RELRO           STACK CANARY      NX            PIE             RPATH=20=20=
=20=20=20
RUNPATH      Symbols         FORTIFY Fortified       Fortifiable     FILE
Full RELRO      Canary found      NX enabled    PIE enabled     No RPATH   =
No
RUNPATH   No Symbols      Partial 5               15=20=20=20=20=20=20=20=
=20=20=20=20=20=20
/usr/lib64/firefox/firefox-bin

I want to point to:

* "STACK CANARY =3D No canary found"
* "PIE =3D No PIE"
* "RUNPATH =3D RUNPATH"

Most of the applications on my system look quite fine (similar to Firefox=
=E2=80=A6).
But LibreOffice is one of the major applications (often used and big impact
(loading/importing and storing/exporting data, working on data, able to run
skripts=E2=80=A6) that has these issues.

I would like to see the LibreOffice related bins with similar checksec resu=
lts
compared to Firefox.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17395206530.AcEF2A0.2258
Date: Fri, 14 Feb 2025 08:10:53 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1237182

          Summary
          openSUSE Leap (15.6): LibreOffice (openSUSE regular release):=
 insure build settings (compared to other applications)

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          x86-64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          LibreOffice

          Assignee
          screening-team-bugs@suse.de

          Reporter
          Gunner.Gewiss@posteo.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Dear all!

Please compare:

~> checksec --file=3D/usr/lib64/libreoffice/program/soffice.bin
RELRO           STACK CANARY      NX            PIE             RPATH=20=20=
=20=20=20
RUNPATH      Symbols         FORTIFY Fortified       Fortifiable     FILE
Full RELRO      No canary found   NX enabled    No PIE          No RPATH=20=
=20
RUNPATH     No Symbols       N/A     0               0=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20
/usr/lib64/libreoffice/program/soffice.bin

to:

~> checksec --file=3D/usr/lib64/firefox/firefox-bin
RELRO           STACK CANARY      NX            PIE             RPATH=20=20=
=20=20=20
RUNPATH      Symbols         FORTIFY Fortified       Fortifiable     FILE
Full RELRO      Canary found      NX enabled    PIE enabled     No RPATH   =
No
RUNPATH   No Symbols      Partial 5               15=20=20=20=20=20=20=20=
=20=20=20=20=20=20
/usr/lib64/firefox/firefox-bin

I want to point to:

* "STACK CANARY =3D No canary found"
* "PIE =3D No PIE"
* "RUNPATH =3D RUNPATH"

Most of the applications on my system look quite fine (similar to Firefox=
=E2=80=A6).
But LibreOffice is one of the major applications (often used and big impact
(loading/importing and storing/exporting data, working on data, able to run
skripts=E2=80=A6) that has these issues.

I would like to see the LibreOffice related bins with similar checksec resu=
lts
compared to Firefox.

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

You are on the CC list for the bug.

=

--17395206530.AcEF2A0.2258--


body:
--17396254330.06443dB.4129
Date: Sat, 15 Feb 2025 13:17: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=3D1237209

            Bug ID: 1237209
           Summary: file: buffer overrun detect
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: 64bit
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: fawz-at-use.startmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 880385
  --> https://bugzilla.suse.com/attachment.cgi?id=3D880385&action=3Dedit
Use with file to reproduce bug

Running file against some files may result in a buffer overrun, causing fil=
e to
crash.

Detected since this made extract Yocto SDKs fail in some cases.

Fixed upstream since 2024-12-05, but not in any release from upstream yet.

File to reproduce with is attached and can also be found in alpine issue ti=
cket
below.

Related links

- https://bugs.astron.com/view.php?id=3D579#history
- https://gitlab.alpinelinux.org/alpine/aports/-/issues/16797
-
https://github.com/yoctoproject/poky/commit/10dce263f0230f94a44a017b5614811=
e696c5ce9
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17396254330.06443dB.4129
Date: Sat, 15 Feb 2025 13:17: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
          1237209

          Summary
          file: buffer overrun detect

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          64bit

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          fawz@use.startmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachm=
ent 880385 [details]
Use with file to reproduce bug

Running file against some files may result in a buffer overrun, causing fil=
e to
crash.

Detected since this made extract Yocto SDKs fail in some cases.

Fixed upstream since 2024-12-05, but not in any release from upstream yet.

File to reproduce with is attached and can also be found in alpine issue ti=
cket
below.

Related links

- https://bug=
s.astron.com/view.php?id=3D579#history
- h=
ttps://gitlab.alpinelinux.org/alpine/aports/-/issues/16797
-
https://github.com/yoctoproject/poky/commit/10dce263f=
0230f94a44a017b5614811e696c5ce9

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

You are on the CC list for the bug.

=

--17396254330.06443dB.4129--

summary: file: buffer overrun detect


body:
--17396360041.f11DA.4224
Date: Sat, 15 Feb 2025 16:13:24 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1237210
           Summary: automount doesn't find lookup_nis.so
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel:Filesystems
          Assignee: kernel-fs-at-suse.de
          Reporter: oliver-at-schwabedissen.name
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

After updating autofs from 5.1.9-5.2 to 5.1.9-6.1 automount complains about=
 not
finding lookup_nis.so anymore. The following error message can be found in
/var/log/messages:

open_lookup:68: cannot open lookup module nis (/usr/lib64/autofs/lookup_nis=
.so:
cannot open shared object file: No such file or directory)

Solution:

Check /usr/etc/nsswitch.conf. If it contains "nis" for the "automount:" ent=
ry
then copy the file to /etc and remove "nis" in /etc/nsswitch.conf.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17396360041.f11DA.4224
Date: Sat, 15 Feb 2025 16:13:24 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1237210

          Summary
          automount doesn't find lookup_nis.so

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel:Filesystems

          Assignee
          kernel-fs@suse.de

          Reporter
          oliver@schwabedissen.name

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

After updating autofs from 5.1.9-5.2 to 5.1.9-6.1 automount =
complains about not
finding lookup_nis.so anymore. The following error message can be found in
/var/log/messages:

open_lookup:68: cannot open lookup module nis (/usr/lib64/autofs/lookup_nis=
.so:
cannot open shared object file: No such file or directory)

Solution:

Check /usr/etc/nsswitch.conf. If it contains "nis" for the "=
automount:" entry
then copy the file to /etc and remove "nis" in /etc/nsswitch.conf=
.

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

You are on the CC list for the bug.

=

--17396360041.f11DA.4224--

summary: automount doesn't find lookup_nis.so


--17397161862.fE20AE08.4473
Date: Sun, 16 Feb 2025 14:29:46 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1237219
           Summary: irqbalance segfaults at libnl-3.so.200.26.0[aa40,7f83d3117000+20000]
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: nettezzaumanaa-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 880388
  --> https://bugzilla.suse.com/attachment.cgi?id=3D880388&action=3Dedit
content described above

Hello,

I have up to date SUSE 15.6 and my irqbalance segfaults at every boot ++ of=
ten
afterwards like this

[   20.920327] irqbalance[1683]: segfault at 0 ip 00007f83d3121a40 sp
00007ffd96c76c18 error 4 in libnl-3.so.200.26.0[aa40,7f83d3117000+20000] li=
kely
on CPU 11 (core 15, socket 0)

I have no special configuration except of kernel from

https://download.opensuse.org/repositories/Kernel:/stable:/Backport/standar=
d/
https://download.opensuse.org/repositories/Kernel:/stable:/Backport:/KMP/st=
andard/

I am attaching some info, you will find included

coredump file
zypper -vv se -is
zypper -vv lr -dE
inxi -FxxxrzG
hwinfo

thank you very much in forward for your support ..

regards, ~dan
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17397161862.fE20AE08.4473
Date: Sun, 16 Feb 2025 14:29:46 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1237219

          Summary
          irqbalance segfaults at libnl-3.so.200.26.0[aa40,7f83d3117000=
+20000]

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          x86-64

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          nettezzaumanaa@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 880=
388 [details]
content described above

Hello,

I have up to date SUSE 15.6 and my irqbalance segfaults at every boot ++ of=
ten
afterwards like this

[   20.920327] irqbalance[1683]: segfault at 0 ip 00007f83d3121a40 sp
00007ffd96c76c18 error 4 in libnl-3.so.200.26.0[aa40,7f83d3117000+20000] li=
kely
on CPU 11 (core 15, socket 0)

I have no special configuration except of kernel from

https://download.opensuse.org/repositories/Kernel:/stable:/B=
ackport/standard/
https://download.opensuse.org/repositories/Kernel:/stab=
le:/Backport:/KMP/standard/

I am attaching some info, you will find included

coredump file
zypper -vv se -is
zypper -vv lr -dE
inxi -FxxxrzG
hwinfo

thank you very much in forward for your support ..

regards, ~dan

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

You are on the CC list for the bug.

=

--17397161862.fE20AE08.4473--


--17397232453.6D0886CdD.4542
Date: Sun, 16 Feb 2025 16:27:25 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1237220
           Summary: Enable CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER for Flicker-Free Boot
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: hadichokr-at-icloud.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I propose enabling CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in openSUSE=
=E2=80=99s
default kernel configuration to achieve a truly flicker-free boot experienc=
e.

Rationale

Modern UEFI firmware displays the vendor logo during boot until control is
handed over to the bootloader. Currently, openSUSE's kernel clears this logo
early in the boot process, causing an unnecessary flicker before Plymouth t=
akes
over.

Enabling CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER ensures that the vend=
or
logo remains visible until the framebuffer console needs to display text. W=
hen
combined with systemd-boot (which does not blank the screen when timeout 0 =
is
set) and the default Plymouth BGRT theme, this would result in a seamless,
flicker-free transition from firmware to the graphical boot splash.

Benefits

Eliminates unnecessary screen flickers during boot.

Improves aesthetics by retaining the vendor logo until Plymouth takes over.

Aligns openSUSE with other distributions like Arch Linux, which already ena=
bles
this option (CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=3Dy).

Complements the shift from GRUB to systemd-boot, as systemd-boot does not
forcibly blank the screen.

Implementation

Modify openSUSE=E2=80=99s kernel build configuration to set:

CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=3Dy

Ensure that the Plymouth BGRT theme remains the default for a smooth
transition.

By making this change, openSUSE can offer an improved, flicker-free boot
experience when used with Systemd-Boot that aligns with modern bootloader a=
nd
firmware expectations.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17397232453.6D0886CdD.4542
Date: Sun, 16 Feb 2025 16:27:25 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1237220

          Summary
          Enable CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER for Flick=
er-Free Boot

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Enhancement

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          hadichokr@icloud.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I propose enabling CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEO=
VER in openSUSE=E2=80=99s
default kernel configuration to achieve a truly flicker-free boot experienc=
e.

Rationale

Modern UEFI firmware displays the vendor logo during boot until control is
handed over to the bootloader. Currently, openSUSE's kernel clears this logo
early in the boot process, causing an unnecessary flicker before Plymouth t=
akes
over.

Enabling CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER ensures that the vend=
or
logo remains visible until the framebuffer console needs to display text. W=
hen
combined with systemd-boot (which does not blank the screen when timeout 0 =
is
set) and the default Plymouth BGRT theme, this would result in a seamless,
flicker-free transition from firmware to the graphical boot splash.

Benefits

Eliminates unnecessary screen flickers during boot.

Improves aesthetics by retaining the vendor logo until Plymouth takes over.

Aligns openSUSE with other distributions like Arch Linux, which already ena=
bles
this option (CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=3Dy).

Complements the shift from GRUB to systemd-boot, as systemd-boot does not
forcibly blank the screen.

Implementation

Modify openSUSE=E2=80=99s kernel build configuration to set:

CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=3Dy

Ensure that the Plymouth BGRT theme remains the default for a smooth
transition.

By making this change, openSUSE can offer an improved, flicker-free boot
experience when used with Systemd-Boot that aligns with modern bootloader a=
nd
firmware expectations.

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

You are on the CC list for the bug.

=

--17397232453.6D0886CdD.4542--


body:
--17397771840.c4dd.4902
Date: Mon, 17 Feb 2025 07:26:24 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1237231
           Summary: rpm-4.18+ embeds build machine CPU count
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: adrian.schroeter-at-suse.com
          Reporter: bwiedemann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: mls-at-suse.com
            Blocks: 1237212
  Target Milestone: ---
          Found By: Development
           Blocker: ---

We want to achieve bit-reproducible rpm builds for SLFO
and one blocker for this is that rpm 4.18 and later stores the expanded .sp=
ec
into the .src.rpm and the binary rpms reference the hash of it.

Previously discussed upstream at
https://github.com/rpm-software-management/rpm/issues/2343

Upstream rejected my
https://github.com/rpm-software-management/rpm/pull/2762

As an alternative we could adapt
https://github.com/openSUSE/obs-build/blob/3a949fd200b1a1c3b77d1cd3c3a96b92=
7565bad5/build-recipe#L262-L263
to not use constants but a variable as intended by upstream.

Then we would still have to change
https://github.com/openSUSE/hpc/blob/f2f3d8c/general/macros.hpc#L493
and probably a few other places.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17397771840.c4dd.4902
Date: Mon, 17 Feb 2025 07:26:24 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1237231

          Summary
          rpm-4.18+ embeds build machine CPU count

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          All

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          adrian.schroeter@suse.com

          Reporter
          bwiedemann@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          mls@suse.com

          Blocks
          1237212

          Target Milestone
          ---

          Found By
          Development

          Blocker
          ---

We want to achieve bit-reproducible rpm builds for SLFO
and one blocker for this is that rpm 4.18 and later stores the expanded .sp=
ec
into the .src.rpm and the binary rpms reference the hash of it.

Previously discussed upstream at
http=
s://github.com/rpm-software-management/rpm/issues/2343

Upstream rejected my
https:=
//github.com/rpm-software-management/rpm/pull/2762

As an alternative we could adapt
https://github.com/openSUSE/obs=
-build/blob/3a949fd200b1a1c3b77d1cd3c3a96b927565bad5/build-recipe#L262-L263=

to not use constants but a variable as intended by upstream.

Then we would still have to change
https://github.com/openSUSE/hpc/blob/f2f3d8c/general/macros.hpc#L493<=
/a>
and probably a few other places.

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

You are on the CC list for the bug.

=

--17397771840.c4dd.4902--

pkgs: MozillaThunderbird chromium firefox-esr libreoffice llvm15 llvm18 llvm20 luabind rpm-config-SUSE texlive


--17397877791.0F2fD.5502
Date: Mon, 17 Feb 2025 10:22:59 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1237250
           Summary: VUL-0: CVE-2025-1378: radare2: radare2 memory corruption
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/441130/
                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: emanuele.cappello-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

A vulnerability, which was classified as problematic, was found in radare2
5.9.9 33286. Affected is an unknown function in the library /libr/main/rasm=
2.c
of the component rasm2. The manipulation leads to memory corruption. An att=
ack
has to be approached locally. The exploit has been disclosed to the public =
and
may be used. Upgrading to version 6.0.0 is able to address this issue. The
patch is identified as c6c772d2eab692ce7ada5a4227afd50c355ad545. It is
recommended to upgrade the affected component.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-1378
https://www.cve.org/CVERecord?id=3DCVE-2025-1378
https://github.com/radareorg/radare2/commit/c6c772d2eab692ce7ada5a4227afd50=
c355ad545
https://github.com/radareorg/radare2/issues/23953
https://github.com/radareorg/radare2/issues/23953#issue-2844325926
https://github.com/radareorg/radare2/milestone/86
https://vuldb.com/?ctiid.295986
https://vuldb.com/?id.295986
https://vuldb.com/?submit.498499
https://bugzilla.redhat.com/show_bug.cgi?id=3D2346069
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17397877791.0F2fD.5502
Date: Mon, 17 Feb 2025 10:22:59 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1237250

          Summary
          VUL-0: CVE-2025-1378: radare2: radare2 memory corruption

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

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

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

A vulnerability, which was classified as problematic, was fo=
und in radare2
5.9.9 33286. Affected is an unknown function in the library /libr/main/rasm=
2.c
of the component rasm2. The manipulation leads to memory corruption. An att=
ack
has to be approached locally. The exploit has been disclosed to the public =
and
may be used. Upgrading to version 6.0.0 is able to address this issue. The
patch is identified as c6c772d2eab692ce7ada5a4227afd50c355ad545. It is
recommended to upgrade the affected component.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-1378
https://www.cv=
e.org/CVERecord?id=3DCVE-2025-1378
https://github.com/radareorg/radare2/commit/c6c772d2e=
ab692ce7ada5a4227afd50c355ad545
https://githu=
b.com/radareorg/radare2/issues/23953
https://github.com/radareorg/radare2/issues/23953#issue-2844325926
https://githu=
b.com/radareorg/radare2/milestone/86
https://vuldb.com/?ctiid.295986=

https://vuldb.com/?id.295986
https://vuldb.com/?submit.4984=
99
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2346069

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

You are on the CC list for the bug.

=

--17397877791.0F2fD.5502--


--17398594942.D9F0c.6800
Date: Tue, 18 Feb 2025 06:18:14 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1237276
           Summary: Building package fails for Tumbleweed but not Slowroll
    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: wardlawhunter-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 880413
  --> https://bugzilla.suse.com/attachment.cgi?id=3D880413&action=3Dedit
Tumbleweed build log

https://build.opensuse.org/package/show/Emulators/rpcs3

Is there a regression in Factory? The following appears in the failed
Tumbleweed build log.

make[2]: *** No rule to make target '/usr/lib64/libSM.so', needed by
'bin/rpcs3'.  Stop.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17398594942.D9F0c.6800
Date: Tue, 18 Feb 2025 06:18:14 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1237276

          Summary
          Building package fails for Tumbleweed but not Slowroll

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

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 880413=
 [details]
Tumbleweed build log

https:/=
/build.opensuse.org/package/show/Emulators/rpcs3

Is there a regression in Factory? The following appears in the failed
Tumbleweed build log.

make[2]: *** No rule to make target '/usr/lib64/libSM.so', needed by
'bin/rpcs3'.  Stop.

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

You are on the CC list for the bug.

=

--17398594942.D9F0c.6800--


--17398867001.2B38Df.8099
Date: Tue, 18 Feb 2025 13:51: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=3D1237308

            Bug ID: 1237308
           Summary: nvidia-open-driver-G06-signed KMP: broken ksym requires and missing hardware Supplements
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 3rd Party Driver
          Assignee: gfx-bugs-at-suse.de
          Reporter: sndirsch-at-suse.com
        QA Contact: sndirsch-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

nvidia-open-driver-G06-signed KMP:
ksym Requires are no longer created and hardware Supplements are also missi=
ng
now.  This regression came in with the following change.

-------------------------------------------------------------------
Tue Feb  4 07:39:11 UTC 2025 - Egbert Eich <eich-at-suse.com>

- Add a directory identifying the KMP and its version to the module
  install path - i.e.:
  <kernel_version>/nvidia-open-driver-G06-signed-<version>/updates
  instead of:
  <kernel_version>/updates
  This avoids conflicts when a new version is built against the
  same kernel release.

-


--17399175883.D128d.9169
Date: Tue, 18 Feb 2025 22:26: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=3D1237329

            Bug ID: 1237329
           Summary: AUDIT-0: apparmor: new polkit actions used by aa-notify
    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: suse-beta-at-cboltz.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

AppArmor 4.1 (currently beta5, packaged in
https://build.opensuse.org/package/show/home:cboltz/apparmor ) introduces
    /usr/share/polkit-1/actions/net.apparmor.pkexec.aa-notify.policy

The latest aa-notify allows users to extend a profile (based on events in
audit.log) via the gui, and calls a helper script to do so.

rpmlint told me to ask you for a review ;-)

If you need more information from me, feel free to ask.

I plan to submit AppArmor 4.1 to Factory when the final release arrives.
(beta releases will only be packaged in my home repo.)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17399175883.D128d.9169
Date: Tue, 18 Feb 2025 22:26: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
          1237329

          Summary
          AUDIT-0: apparmor: new polkit actions used by aa-notify

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

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

AppArmor 4.1 (currently beta5, packaged in
ht=
tps://build.opensuse.org/package/show/home:cboltz/apparmor ) introduces
    /usr/share/polkit-1/actions/net.apparmor.pkexec.aa-notify.policy

The latest aa-notify allows users to extend a profile (based on events in
audit.log) via the gui, and calls a helper script to do so.

rpmlint told me to ask you for a review ;-)

If you need more information from me, feel free to ask.

I plan to submit AppArmor 4.1 to Factory when the final release arrives.
(beta releases will only be packaged in my home repo.)

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

You are on the CC list for the bug.

=

--17399175883.D128d.9169--


--17399222763.Dad7Fa.9199
Date: Tue, 18 Feb 2025 23:44:36 +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=3D1237330

            Bug ID: 1237330
           Summary: hotplug feature lacks on nvidia v570.86.16
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 3rd Party Driver
          Assignee: gfx-bugs-at-suse.de
          Reporter: R_Nik_C-at-proton.me
        QA Contact: sndirsch-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

That feature should be enabled as it was in v550 earlier.

[DEBUG supergfxctl::pci_device] Laptop does not have a hotplug dgpu:
DgpuNotFound

dGPU founded but it's not enable hotplug functional... (as I guess it that
related also on suse-prime, because some people have some issue with suse-p=
rime
too on 570 driver.

And this issues appears with v570 so, maybe while packaging missed flag for
that feature?

I supposed that was supergfxctl problem... but seems not.
https://gitlab.com/asus-linux/supergfxctl/-/issues/156

FUll logs of supergfxd
> journalctl -b -u supergfxd
Feb 16 19:57:50 localhost systemd[1]: Starting SUPERGFX...
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxd] Daemon version:
5.2.7
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
DiscreetGpu::new: Rescanning PCI bus
Feb 16 19:57:50 localhost systemd[1]: Started SUPERGFX.
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:00:00.0"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:00:00.2"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:00:01.0"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:00:01.1"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:01:00.0"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Matched dGPU 10DE:2191 at "0000:01:00.0" by checking display connections
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Found dgpu 10DE:2191 at "0000:01:00.0"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Laptop does not have a hotplug dgpu: DgpuNotFound
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:01:00.1"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Matched dGPU 10DE:1AEB at "0000:01:00.1" by checking display connections
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Found ID_MODEL_FROM_DATABASE property 10DE:1AEB at "0000:01:00.1" : "TU116 =
High
Definition Audio Controller"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Found additional device 10DE:1AEB at "0000:01:00.1"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:01:00.2"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Matched dGPU 10DE:1AEC at "0000:01:00.2" by checking display connections
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Found ID_MODEL_FROM_DATABASE property 10DE:1AEC at "0000:01:00.2" : "TU116 =
USB
3.1 Host Controller"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Found additional device 10DE:1AEC at "0000:01:00.2"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:01:00.3"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Matched dGPU 10DE:1AED at "0000:01:00.3" by checking display connections
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Found ID_MODEL_FROM_DATABASE property 10DE:1AED at "0000:01:00.3" : "TU116 =
USB
Type-C UCSI Controller"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Found additional device 10DE:1AED at "0000:01:00.3"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:00:01.2"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl] supergfxd.mo=
de
not set, ignoring
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::controller]
do_mode_setup_tasks(mode:Hybrid, vfio_enable:true, asus_use_dgpu_disable: N=
one)
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::special_asus]
asus_reload: asus_use_dgpu_disable: false
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::config]
create_modprobe_conf: writing /etc/modprobe.d/supergfxd.conf
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::config]
check_vulkan_icd: checking for Vulkan ICD profiles...
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::actions]
do_rescan: Rescanning PCI bus
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
do_driver_action: action =3D modprobe, [Device { dev_path:
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0", hotplug_path: None,
vendor: Nvidia, is_dgpu: true, name: "0000:01:00.0", pci_id: "10DE:2191" },
Device { dev_path: "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.1",
hotplug_path: None, vendor: Nvidia, is_dgpu: false, name: "0000:01:00.1",
pci_id: "10DE:1AEB" }, Device { dev_path:
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.2", hotplug_path: None,
vendor: Nvidia, is_dgpu: false, name: "0000:01:00.2", pci_id: "10DE:1AEC" },
Device { dev_path: "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.3",
hotplug_path: None, vendor: Nvidia, is_dgpu: false, name: "0000:01:00.3",
pci_id: "10DE:1AED" }]
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl] Did modprobe=
 for
driver nvidia_drm
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl] Did modprobe=
 for
driver nvidia_modeset
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl] Did modprobe=
 for
driver nvidia_uvm
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl] Did modprobe=
 for
driver nvidia
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl] Did CommandA=
rgs
{ inner: ["start", "nvidia-powerd.service"] }
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
set_runtime_pm: pm =3D Auto, [Device { dev_path:
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0", hotplug_path: None,
vendor: Nvidia, is_dgpu: true, name: "0000:01:00.0", pci_id: "10DE:2191" },
Device { dev_path: "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.1",
hotplug_path: None, vendor: Nvidia, is_dgpu: false, name: "0000:01:00.1",
pci_id: "10DE:1AEB" }, Device { dev_path:
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.2", hotplug_path: None,
vendor: Nvidia, is_dgpu: false, name: "0000:01:00.2", pci_id: "10DE:1AEC" },
Device { dev_path: "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.3",
hotplug_path: None, vendor: Nvidia, is_dgpu: false, name: "0000:01:00.3",
pci_id: "10DE:1AED" }]
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
set_runtime_pm: Set PM on "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.=
0"
to Auto
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
set_runtime_pm: Set PM on "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.=
1"
to Auto
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
set_runtime_pm: Set PM on "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.=
2"
to Auto
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
set_runtime_pm: Set PM on "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.=
3"
to Auto
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::controller]
reload: Reloaded gfx mode: Hybrid
Feb 16 19:58:08 localhost.localdomain supergfxd[1398]: [INFO  supergfxctl]
nvidia-drm.modeset not set, ignoring
Feb 16 19:58:17 localhost.localdomain supergfxd[1398]: [INFO=20
supergfxctl::zbus_iface] Switching gfx mode to Integrated
Feb 16 19:58:17 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::controller] Doing action: WaitLogout
Feb 16 19:58:22 localhost.localdomain supergfxd[1398]: [WARN=20
supergfxctl::actions] graphical_user_sessions_exist: class:
FDO(IOError("manager is an invalid variant"))
Feb 16 19:58:22 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::actions] wait_logout: loop exited
Feb 16 19:58:22 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::controller] Doing action: StopDisplayManager
Feb 16 19:58:22 localhost.localdomain supergfxd[1398]: [INFO=20
supergfxctl::systemd] Running systemctl command Stop on display-manager.ser=
vice
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::controller] Doing action: DisableNvidiaPowerd
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [DEBUG supergfxctl] =
Did
CommandArgs { inner: ["stop", "nvidia-powerd.service"] }
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::controller] Doing action: KillNvidia
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [WARN  supergfxctl] =
pid
1402 (nvidia-pe) is holding /dev/nvidia0. Killing
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [WARN  supergfxctl] =
pid
1402 (nvidia-pe) is holding /dev/nvidia0. Killing
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [WARN  supergfxctl] =
pid
1402 (nvidia-pe) is holding /dev/nvidia0. Killing
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [WARN  supergfxctl] =
pid
1402 (nvidia-pe) is holding /dev/nvidia0. Killing
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::controller] Doing action: UnloadGpuDrivers
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::pci_device] do_driver_action: action =3D rmmod, [Device { dev_=
path:
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0", hotplug_path: None,
vendor: Nvidia, is_dgpu: true, name: "0000:01:00.0", pci_id: "10DE:2191" },
Device { dev_path: "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.1",
hotplug_path: None, vendor: Nvidia, is_dgpu: false, name: "0000:01:00.1",
pci_id: "10DE:1AEB" }, Device { dev_path:
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.2", hotplug_path: None,
vendor: Nvidia, is_dgpu: false, name: "0000:01:00.2", pci_id: "10DE:1AEC" },
Device { dev_path: "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.3",
hotplug_path: None, vendor: Nvidia, is_dgpu: false, name: "0000:01:00.3",
pci_id: "10DE:1AED" }]
Feb 16 19:58:30 localhost.localdomain supergfxd[1398]: [DEBUG supergfxctl] =
Did
rmmod for driver nvidia_drm
Feb 16 19:58:30 localhost.localdomain supergfxd[1398]: [ERROR
supergfxctl::controller] Action thread errored: Modprobe error: rmmod
nvidia_modeset failed: "rmmod: ERROR: Module nvidia_modeset is in use\n"
Feb 16 19:58:30 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::controller] Doing action: UnbindRemoveGpu
Feb 16 19:58:30 localhost.localdomain supergfxd[1398]: [INFO=20
supergfxctl::pci_device] Unbound
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.3"
Feb 16 19:58:30 localhost.localdomain supergfxd[1398]: [INFO=20
supergfxctl::pci_device] Unbound
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.2"
Feb 16 19:58:30 localhost.localdomain supergfxd[1398]: [INFO=20
supergfxctl::pci_device] Unbound
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.1"
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17399222763.Dad7Fa.9199
Date: Tue, 18 Feb 2025 23:44:36 +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
          1237330

          Summary
          hotplug feature lacks on nvidia v570.86.16

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X11 3rd Party Driver

          Assignee
          gfx-bugs@suse.de

          Reporter
          R_Nik_C@proton.me

          QA Contact
          sndirsch@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

That feature should be enabled as it was in v550 earlier.

[DEBUG supergfxctl::pci_device] Laptop does not have a hotplug dgpu:
DgpuNotFound

dGPU founded but it's not enable hotplug functional... (as I guess it that
related also on suse-prime, because some people have some issue with suse-p=
rime
too on 570 driver.

And this issues appears with v570 so, maybe while packaging missed flag for
that feature?

I supposed that was supergfxctl problem... but seems not.
https://=
gitlab.com/asus-linux/supergfxctl/-/issues/156

FUll logs of supergfxd
> journalctl -b -u supergfxd
Feb 16 19:57:50 localhost systemd[1]: Starting SUPERGFX...
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxd] Daemon version:
5.2.7
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
DiscreetGpu::new: Rescanning PCI bus
Feb 16 19:57:50 localhost systemd[1]: Started SUPERGFX.
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:00:00.0"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:00:00.2"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:00:01.0"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:00:01.1"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:01:00.0"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Matched dGPU 10DE:2191 at "0000:01:00.0" by checking display conn=
ections
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Found dgpu 10DE:2191 at "0000:01:00.0"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Laptop does not have a hotplug dgpu: DgpuNotFound
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:01:00.1"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Matched dGPU 10DE:1AEB at "0000:01:00.1" by checking display conn=
ections
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Found ID_MODEL_FROM_DATABASE property 10DE:1AEB at "0000:01:00.1"=
 : "TU116 High
Definition Audio Controller"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Found additional device 10DE:1AEB at "0000:01:00.1"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:01:00.2"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Matched dGPU 10DE:1AEC at "0000:01:00.2" by checking display conn=
ections
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Found ID_MODEL_FROM_DATABASE property 10DE:1AEC at "0000:01:00.2"=
 : "TU116 USB
3.1 Host Controller"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Found additional device 10DE:1AEC at "0000:01:00.2"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:01:00.3"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Matched dGPU 10DE:1AED at "0000:01:00.3" by checking display conn=
ections
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Found ID_MODEL_FROM_DATABASE property 10DE:1AED at "0000:01:00.3"=
 : "TU116 USB
Type-C UCSI Controller"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
Found additional device 10DE:1AED at "0000:01:00.3"
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
Looking at PCI device "0000:00:01.2"
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl] supergfxd.mo=
de
not set, ignoring
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::controller]
do_mode_setup_tasks(mode:Hybrid, vfio_enable:true, asus_use_dgpu_disable: N=
one)
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::special_asus]
asus_reload: asus_use_dgpu_disable: false
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::config]
create_modprobe_conf: writing /etc/modprobe.d/supergfxd.conf
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::config]
check_vulkan_icd: checking for Vulkan ICD profiles...
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::actions]
do_rescan: Rescanning PCI bus
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
do_driver_action: action =3D modprobe, [Device { dev_path:
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0", hotplug_path=
: None,
vendor: Nvidia, is_dgpu: true, name: "0000:01:00.0", pci_id: &quo=
t;10DE:2191" },
Device { dev_path: "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.1&=
quot;,
hotplug_path: None, vendor: Nvidia, is_dgpu: false, name: "0000:01:00.=
1",
pci_id: "10DE:1AEB" }, Device { dev_path:
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.2", hotplug_path=
: None,
vendor: Nvidia, is_dgpu: false, name: "0000:01:00.2", pci_id: &qu=
ot;10DE:1AEC" },
Device { dev_path: "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.3&=
quot;,
hotplug_path: None, vendor: Nvidia, is_dgpu: false, name: "0000:01:00.=
3",
pci_id: "10DE:1AED" }]
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl] Did modprobe=
 for
driver nvidia_drm
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl] Did modprobe=
 for
driver nvidia_modeset
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl] Did modprobe=
 for
driver nvidia_uvm
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl] Did modprobe=
 for
driver nvidia
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl] Did CommandA=
rgs
{ inner: ["start", "nvidia-powerd.service"] }
Feb 16 19:57:50 localhost supergfxd[1398]: [DEBUG supergfxctl::pci_device]
set_runtime_pm: pm =3D Auto, [Device { dev_path:
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0", hotplug_path=
: None,
vendor: Nvidia, is_dgpu: true, name: "0000:01:00.0", pci_id: &quo=
t;10DE:2191" },
Device { dev_path: "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.1&=
quot;,
hotplug_path: None, vendor: Nvidia, is_dgpu: false, name: "0000:01:00.=
1",
pci_id: "10DE:1AEB" }, Device { dev_path:
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.2", hotplug_path=
: None,
vendor: Nvidia, is_dgpu: false, name: "0000:01:00.2", pci_id: &qu=
ot;10DE:1AEC" },
Device { dev_path: "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.3&=
quot;,
hotplug_path: None, vendor: Nvidia, is_dgpu: false, name: "0000:01:00.=
3",
pci_id: "10DE:1AED" }]
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
set_runtime_pm: Set PM on "/sys/devices/pci0000:00/0000:00:01.1/0000:0=
1:00.0"
to Auto
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
set_runtime_pm: Set PM on "/sys/devices/pci0000:00/0000:00:01.1/0000:0=
1:00.1"
to Auto
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
set_runtime_pm: Set PM on "/sys/devices/pci0000:00/0000:00:01.1/0000:0=
1:00.2"
to Auto
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::pci_device]
set_runtime_pm: Set PM on "/sys/devices/pci0000:00/0000:00:01.1/0000:0=
1:00.3"
to Auto
Feb 16 19:57:50 localhost supergfxd[1398]: [INFO  supergfxctl::controller]
reload: Reloaded gfx mode: Hybrid
Feb 16 19:58:08 localhost.localdomain supergfxd[1398]: [INFO  supergfxctl]
nvidia-drm.modeset not set, ignoring
Feb 16 19:58:17 localhost.localdomain supergfxd[1398]: [INFO=20
supergfxctl::zbus_iface] Switching gfx mode to Integrated
Feb 16 19:58:17 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::controller] Doing action: WaitLogout
Feb 16 19:58:22 localhost.localdomain supergfxd[1398]: [WARN=20
supergfxctl::actions] graphical_user_sessions_exist: class:
FDO(IOError("manager is an invalid variant"))
Feb 16 19:58:22 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::actions] wait_logout: loop exited
Feb 16 19:58:22 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::controller] Doing action: StopDisplayManager
Feb 16 19:58:22 localhost.localdomain supergfxd[1398]: [INFO=20
supergfxctl::systemd] Running systemctl command Stop on display-manager.ser=
vice
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::controller] Doing action: DisableNvidiaPowerd
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [DEBUG supergfxctl] =
Did
CommandArgs { inner: ["stop", "nvidia-powerd.service"] }
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::controller] Doing action: KillNvidia
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [WARN  supergfxctl] =
pid
1402 (nvidia-pe) is holding /dev/nvidia0. Killing
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [WARN  supergfxctl] =
pid
1402 (nvidia-pe) is holding /dev/nvidia0. Killing
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [WARN  supergfxctl] =
pid
1402 (nvidia-pe) is holding /dev/nvidia0. Killing
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [WARN  supergfxctl] =
pid
1402 (nvidia-pe) is holding /dev/nvidia0. Killing
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::controller] Doing action: UnloadGpuDrivers
Feb 16 19:58:29 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::pci_device] do_driver_action: action =3D rmmod, [Device { dev_=
path:
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0", hotplug_path=
: None,
vendor: Nvidia, is_dgpu: true, name: "0000:01:00.0", pci_id: &quo=
t;10DE:2191" },
Device { dev_path: "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.1&=
quot;,
hotplug_path: None, vendor: Nvidia, is_dgpu: false, name: "0000:01:00.=
1",
pci_id: "10DE:1AEB" }, Device { dev_path:
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.2", hotplug_path=
: None,
vendor: Nvidia, is_dgpu: false, name: "0000:01:00.2", pci_id: &qu=
ot;10DE:1AEC" },
Device { dev_path: "/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.3&=
quot;,
hotplug_path: None, vendor: Nvidia, is_dgpu: false, name: "0000:01:00.=
3",
pci_id: "10DE:1AED" }]
Feb 16 19:58:30 localhost.localdomain supergfxd[1398]: [DEBUG supergfxctl] =
Did
rmmod for driver nvidia_drm
Feb 16 19:58:30 localhost.localdomain supergfxd[1398]: [ERROR
supergfxctl::controller] Action thread errored: Modprobe error: rmmod
nvidia_modeset failed: "rmmod: ERROR: Module nvidia_modeset is in use\=
n"
Feb 16 19:58:30 localhost.localdomain supergfxd[1398]: [DEBUG
supergfxctl::controller] Doing action: UnbindRemoveGpu
Feb 16 19:58:30 localhost.localdomain supergfxd[1398]: [INFO=20
supergfxctl::pci_device] Unbound
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.3"
Feb 16 19:58:30 localhost.localdomain supergfxd[1398]: [INFO=20
supergfxctl::pci_device] Unbound
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.2"
Feb 16 19:58:30 localhost.localdomain supergfxd[1398]: [INFO=20
supergfxctl::pci_device] Unbound
"/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.1"

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

You are on the CC list for the bug.

=

--17399222763.Dad7Fa.9199--


--17399488831.f8246.9637
Date: Wed, 19 Feb 2025 07:08: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=3D1237343

            Bug ID: 1237343
           Summary: VUL-0: chromium: security update to 133.0.6943.98
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: ro-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

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

Fixed in 133.0.6943.126:

CVE-2025-0999: Heap buffer overflow in V8
CVE-2025-1426: Heap buffer overflow in GPU
CVE-2025-1006: Use after free in Network
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17399488831.f8246.9637
Date: Wed, 19 Feb 2025 07:08: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
          1237343

          Summary
          VUL-0: chromium: security update to 133.0.6943.98

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          ro@suse.com

          Reporter
          Andreas.Stieger@gmx.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

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

Fixed in 133.0.6943.126:

CVE-2025-0999: Heap buffer overflow in V8
CVE-2025-1426: Heap buffer overflow in GPU
CVE-2025-1006: Use after free in Network

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

You are on the CC list for the bug.

=

--17399488831.f8246.9637--


--17399582850.eBaB.10168
Date: Wed, 19 Feb 2025 09:44:45 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1237355
           Summary: VUL-0: CVE-2025-25475: dcmtk: Denial of Service (DoS) via a crafted DICOM file.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/441341/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: kde-maintainers-at-suse.de
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: emanuele.cappello-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

A NULL pointer dereference in the component /libsrc/dcrleccd.cc of DCMTK
v3.6.9+ DEV allows attackers to cause a Denial of Service (DoS) via a craft=
ed
DICOM file.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-25475
https://www.cve.org/CVERecord?id=3DCVE-2025-25475
https://git.dcmtk.org/?p=3Ddcmtk.git;a=3Dcommit;h=3Dbffa3e9116abb7038b43244=
3f16b1bd390e80245
https://github.com/DCMTK/dcmtk/commit/bffa3e9116abb7038b432443f16b1bd390e80=
245
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17399582850.eBaB.10168
Date: Wed, 19 Feb 2025 09:44:45 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1237355

          Summary
          VUL-0: CVE-2025-25475: dcmtk: Denial of Service (DoS) via a c=
rafted DICOM file.

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          kde-maintainers@suse.de

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          emanuele.cappello@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

A NULL pointer dereference in the component /libsrc/dcrleccd=
.cc of DCMTK
v3.6.9+ DEV allows attackers to cause a Denial of Service (DoS) via a craft=
ed
DICOM file.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-25475
https://www.c=
ve.org/CVERecord?id=3DCVE-2025-25475
https://git.dcmtk.org/?p=3Ddcmtk.git;a=3Dcomm=
it;h=3Dbffa3e9116abb7038b432443f16b1bd390e80245
https://github.com/DCMTK/dcmtk/commit/bffa3e9116abb7038b432=
443f16b1bd390e80245

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

You are on the CC list for the bug.

=

--17399582850.eBaB.10168--


--17399653359.dC3fBB87.10546
Date: Wed, 19 Feb 2025 11:42:15 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1237365
           Summary: VUL-0: CVE-2025-25474: dcmtk: Buffer overflow via the component /dcmimgle/diinpxt.h.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/441340/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: kde-maintainers-at-suse.de
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: emanuele.cappello-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

DCMTK v3.6.9+ DEV was discovered to contain a buffer overflow via the compo=
nent
/dcmimgle/diinpxt.h.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-25474
https://www.cve.org/CVERecord?id=3DCVE-2025-25474
https://git.dcmtk.org/?p=3Ddcmtk.git;a=3Dcommit;h=3D1d205bcd307164c99e0d4bb=
f412110372658d847
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17399653359.dC3fBB87.10546
Date: Wed, 19 Feb 2025 11:42:15 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1237365

          Summary
          VUL-0: CVE-2025-25474: dcmtk: Buffer overflow via the compone=
nt /dcmimgle/diinpxt.h.

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Minor

          Priority
          P5 - None

          Component
          Security

          Assignee
          kde-maintainers@suse.de

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          emanuele.cappello@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

DCMTK v3.6.9+ DEV was discovered to contain a buffer overflo=
w via the component
/dcmimgle/diinpxt.h.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-25474
https://www.c=
ve.org/CVERecord?id=3DCVE-2025-25474
https://git.dcmtk.org/?p=3Ddcmtk.git;a=3Dcomm=
it;h=3D1d205bcd307164c99e0d4bbf412110372658d847

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

You are on the CC list for the bug.

=

--17399653359.dC3fBB87.10546--


--17399657905.df7FA.10579
Date: Wed, 19 Feb 2025 11:49:50 +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=3D1237369

            Bug ID: 1237369
           Summary: VUL-0: CVE-2025-25472: dcmtk: Denial of Service (DoS) via a crafted DCM file.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/441338/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: kde-maintainers-at-suse.de
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: emanuele.cappello-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

A buffer overflow in DCMTK git master v3.6.9+ DEV allows attackers to cause=
 a
Denial of Service (DoS) via a crafted DCM file.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-25472
https://www.cve.org/CVERecord?id=3DCVE-2025-25472
https://git.dcmtk.org/?p=3Ddcmtk.git;a=3Dcommit;h=3D410ffe2019b9db6a8f4036d=
aac742a6f5e4d36c2
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17399657905.df7FA.10579
Date: Wed, 19 Feb 2025 11:49:50 +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
          1237369

          Summary
          VUL-0: CVE-2025-25472: dcmtk: Denial of Service (DoS) via a c=
rafted DCM file.

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Minor

          Priority
          P5 - None

          Component
          Security

          Assignee
          kde-maintainers@suse.de

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          emanuele.cappello@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

A buffer overflow in DCMTK git master v3.6.9+ DEV allows att=
ackers to cause a
Denial of Service (DoS) via a crafted DCM file.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-25472
https://www.c=
ve.org/CVERecord?id=3DCVE-2025-25472
https://git.dcmtk.org/?p=3Ddcmtk.git;a=3Dcomm=
it;h=3D410ffe2019b9db6a8f4036daac742a6f5e4d36c2

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

You are on the CC list for the bug.

=

--17399657905.df7FA.10579--


body:
--17399711884.0da4D1c.10849
Date: Wed, 19 Feb 2025 13:19:48 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1237375
           Summary: [SELinux] blocks tor and privoxy
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: robby.engelmann@r-engelmann.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Tor & Privoxy units fail to start:

> systemctl status tor.service=20
=C3=97 tor.service - Anonymizing overlay network for TCP
     Loaded: loaded (/usr/lib/systemd/system/tor.service; enabled; preset:
disabled)
     Active: failed (Result: exit-code) since Wed 2025-02-19 14:02:44 CET; =
2min
58s ago
 Invocation: c11cb882185c4e58a7b00d8082ba5302
    Process: 2923 ExecStartPre=3D/usr/bin/tor --runasdaemon 0 --defaults-to=
rrc
/usr/share/tor/defaults-torrc -f /etc/tor/torrc --verify-config --user tor
--hush (code=3Dexited, status=3D0/SUCCESS)
    Process: 2925 ExecStart=3D/usr/bin/tor --runasdaemon 0 --defaults-torrc
/usr/share/tor/defaults-torrc -f /etc/tor/torrc --user tor --hush (code=3De=
xited,
status=3D1/FAILURE)
   Main PID: 2925 (code=3Dexited, status=3D1/FAILURE)

Feb 19 14:02:44 localhost.localdomain systemd[1]: tor.service: Scheduled
restart job, restart counter is at 5.
Feb 19 14:02:44 localhost.localdomain systemd[1]: tor.service: Start request
repeated too quickly.
Feb 19 14:02:44 localhost.localdomain systemd[1]: tor.service: Failed with
result 'exit-code'.
Feb 19 14:02:44 localhost.localdomain systemd[1]: Failed to start Anonymizi=
ng
overlay network for TCP.

> systemctl status privoxy.service=20
=C3=97 privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabili=
ties
     Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; pres=
et:
disabled)
     Active: failed (Result: exit-code) since Wed 2025-02-19 14:02:39 CET; =
3min
7s ago
 Invocation: d812718b573040f69a476f53b788e1d6
    Process: 1947 ExecStartPre=3D/usr/bin/cp -upf /etc/resolv.conf /etc/hos=
t.conf
/etc/hosts /etc/localtime /var/lib/privoxy/etc/ (code=3Dexited, status=3D0/=
SUCCESS)
    Process: 1990 ExecStartPre=3D/usr/bin/cp -upf /lib64/libresolv.so.2
/lib64/libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=3Dexited, status=3D0/S=
UCCESS)
    Process: 2035 ExecStart=3D/usr/sbin/privoxy --chroot --pidfile
/run/privoxy.pid --user privoxy /etc/config (code=3Dexited, status=3D1/FAIL=
URE)
        CPU: 126ms

Feb 19 14:02:38 localhost.localdomain systemd[1]: Starting Privoxy Web Proxy
With Advanced Filtering Capabilities...
Feb 19 14:02:38 localhost.localdomain privoxy[2059]: 2025-02-19 14:02:38.925
7f17ffa11740 Fatal error: Cannot chroot to /var/lib/privoxy
Feb 19 14:02:39 localhost.localdomain systemd[1]: privoxy.service: Control
process exited, code=3Dexited, status=3D1/FAILURE
Feb 19 14:02:39 localhost.localdomain systemd[1]: privoxy.service: Failed w=
ith
result 'exit-code'.
Feb 19 14:02:39 localhost.localdomain systemd[1]: Failed to start Privoxy W=
eb
Proxy With Advanced Filtering Capabilities.
Feb 19 14:02:43 localhost.localdomain systemd[1]: privoxy.service: Unit can=
not
be reloaded because it is inactive.

probably because blocked by SELinux:
----
time->Wed Feb 19 14:02:38 2025
type=3DAVC msg=3Daudit(1739970158.870:60): avc:  denied  { nnp_transition }=
 for=20
pid=3D1989 comm=3D"(tor)" scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:system_r:tor_t:s0 tclass=3Dprocess2 permissive=3D0
----
time->Wed Feb 19 14:02:38 2025
type=3DAVC msg=3Daudit(1739970158.881:63): avc:  denied  { create } for  pi=
d=3D1989
comm=3D"tor" name=3D"lock" scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:object_r:tor_var_lib_t:s0 tclass=3Dfile permissive=3D0
----
time->Wed Feb 19 14:02:38 2025
type=3DAVC msg=3Daudit(1739970158.881:64): avc:  denied  { read write } for=
=20
pid=3D1989 comm=3D"tor" name=3D"lock" dev=3D"dm-1" ino=3D10144379
scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:object_r:tor_var_lib_t:s0 tclass=3Dfile permissive=3D0
----
time->Wed Feb 19 14:02:38 2025
type=3DAVC msg=3Daudit(1739970158.923:69): avc:  denied  { sys_chroot } for=
=20
pid=3D2059 comm=3D"privoxy" capability=3D18  scontext=3Dsystem_u:system_r:p=
rivoxy_t:s0
tcontext=3Dsystem_u:system_r:privoxy_t:s0 tclass=3Dcapability permissive=3D0
----
time->Wed Feb 19 14:02:39 2025
type=3DAVC msg=3Daudit(1739970159.968:99): avc:  denied  { nnp_transition }=
 for=20
pid=3D2313 comm=3D"(tor)" scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:system_r:tor_t:s0 tclass=3Dprocess2 permissive=3D0
----
time->Wed Feb 19 14:02:39 2025
type=3DAVC msg=3Daudit(1739970159.977:101): avc:  denied  { read write } fo=
r=20
pid=3D2313 comm=3D"tor" name=3D"lock" dev=3D"dm-1" ino=3D10144379
scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:object_r:tor_var_lib_t:s0 tclass=3Dfile permissive=3D0
----
time->Wed Feb 19 14:02:40 2025
type=3DAVC msg=3Daudit(1739970160.062:105): avc:  denied  { getattr } for  =
pid=3D2341
comm=3D"tlp" path=3D"/proc/sys/kernel/nmi_watchdog" dev=3D"proc" ino=3D15616
scontext=3Dsystem_u:system_r:tlp_t:s0
tcontext=3Dsystem_u:object_r:sysctl_nmi_watchdog_t:s0 tclass=3Dfile permiss=
ive=3D0
----
time->Wed Feb 19 14:02:41 2025
type=3DAVC msg=3Daudit(1739970161.313:108): avc:  denied  { nnp_transition =
} for=20
pid=3D2525 comm=3D"(tor)" scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:system_r:tor_t:s0 tclass=3Dprocess2 permissive=3D0
----
time->Wed Feb 19 14:02:41 2025
type=3DAVC msg=3Daudit(1739970161.318:110): avc:  denied  { read write } fo=
r=20
pid=3D2525 comm=3D"tor" name=3D"lock" dev=3D"dm-1" ino=3D10144379
scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:object_r:tor_var_lib_t:s0 tclass=3Dfile permissive=3D0
----
time->Wed Feb 19 14:02:42 2025
type=3DAVC msg=3Daudit(1739970162.489:115): avc:  denied  { nnp_transition =
} for=20
pid=3D2652 comm=3D"(tor)" scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:system_r:tor_t:s0 tclass=3Dprocess2 permissive=3D0
----
time->Wed Feb 19 14:02:42 2025
type=3DAVC msg=3Daudit(1739970162.495:117): avc:  denied  { read write } fo=
r=20
pid=3D2652 comm=3D"tor" name=3D"lock" dev=3D"dm-1" ino=3D10144379
scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:object_r:tor_var_lib_t:s0 tclass=3Dfile permissive=3D0
----
time->Wed Feb 19 14:02:43 2025
type=3DAVC msg=3Daudit(1739970163.861:122): avc:  denied  { nnp_transition =
} for=20
pid=3D2925 comm=3D"(tor)" scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:system_r:tor_t:s0 tclass=3Dprocess2 permissive=3D0
----
time->Wed Feb 19 14:02:43 2025
type=3DAVC msg=3Daudit(1739970163.869:124): avc:  denied  { read write } fo=
r=20
pid=3D2925 comm=3D"tor" name=3D"lock" dev=3D"dm-1" ino=3D10144379
scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:object_r:tor_var_lib_t:s0 tclass=3Dfile permissive=3D0
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17399711884.0da4D1c.10849
Date: Wed, 19 Feb 2025 13:19:48 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1237375

          Summary
          [SELinux] blocks tor and privoxy

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          robby.engelmann@r-engelmann.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Tor & Privoxy units fail to start:

> systemctl status tor.service
=C3=97 tor.service - Anonymizing overlay network for TCP
     Loaded: loaded (/usr/lib/systemd/system/tor.service; enabled; preset:
disabled)
     Active: failed (Result: exit-code) since Wed 2025-02-19 14:02:44 CET; =
2min
58s ago
 Invocation: c11cb882185c4e58a7b00d8082ba5302
    Process: 2923 ExecStartPre=3D/usr/bin/tor --runasdaemon 0 --defaults-to=
rrc
/usr/share/tor/defaults-torrc -f /etc/tor/torrc --verify-config --user tor
--hush (code=3Dexited, status=3D0/SUCCESS)
    Process: 2925 ExecStart=3D/usr/bin/tor --runasdaemon 0 --defaults-torrc
/usr/share/tor/defaults-torrc -f /etc/tor/torrc --user tor --hush (code=3De=
xited,
status=3D1/FAILURE)
   Main PID: 2925 (code=3Dexited, status=3D1/FAILURE)

Feb 19 14:02:44 localhost.localdomain systemd[1]: tor.service: Scheduled
restart job, restart counter is at 5.
Feb 19 14:02:44 localhost.localdomain systemd[1]: tor.service: Start request
repeated too quickly.
Feb 19 14:02:44 localhost.localdomain systemd[1]: tor.service: Failed with
result 'exit-code'.
Feb 19 14:02:44 localhost.localdomain systemd[1]: Failed to start Anonymizi=
ng
overlay network for TCP.

> systemctl status privoxy.service
=C3=97 privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabili=
ties
     Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; pres=
et:
disabled)
     Active: failed (Result: exit-code) since Wed 2025-02-19 14:02:39 CET; =
3min
7s ago
 Invocation: d812718b573040f69a476f53b788e1d6
    Process: 1947 ExecStartPre=3D/usr/bin/cp -upf /etc/resolv.conf /etc/hos=
t.conf
/etc/hosts /etc/localtime /var/lib/privoxy/etc/ (code=3Dexited, status=3D0/=
SUCCESS)
    Process: 1990 ExecStartPre=3D/usr/bin/cp -upf /lib64/libresolv.so.2
/lib64/libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=3Dexited, status=3D0/S=
UCCESS)
    Process: 2035 ExecStart=3D/usr/sbin/privoxy --chroot --pidfile
/run/privoxy.pid --user privoxy /etc/config (code=3Dexited, status=3D1/FAIL=
URE)
        CPU: 126ms

Feb 19 14:02:38 localhost.localdomain systemd[1]: Starting Privoxy Web Proxy
With Advanced Filtering Capabilities...
Feb 19 14:02:38 localhost.localdomain privoxy[2059]: 2025-02-19 14:02:38.925
7f17ffa11740 Fatal error: Cannot chroot to /var/lib/privoxy
Feb 19 14:02:39 localhost.localdomain systemd[1]: privoxy.service: Control
process exited, code=3Dexited, status=3D1/FAILURE
Feb 19 14:02:39 localhost.localdomain systemd[1]: privoxy.service: Failed w=
ith
result 'exit-code'.
Feb 19 14:02:39 localhost.localdomain systemd[1]: Failed to start Privoxy W=
eb
Proxy With Advanced Filtering Capabilities.
Feb 19 14:02:43 localhost.localdomain systemd[1]: privoxy.service: Unit can=
not
be reloaded because it is inactive.

probably because blocked by SELinux:
----
time->Wed Feb 19 14:02:38 2025
type=3DAVC msg=3Daudit(1739970158.870:60): avc:  denied  { nnp_transition }=
 for=20
pid=3D1989 comm=3D"(tor)" scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:system_r:tor_t:s0 tclass=3Dprocess2 permissive=3D0
----
time->Wed Feb 19 14:02:38 2025
type=3DAVC msg=3Daudit(1739970158.881:63): avc:  denied  { create } for  pi=
d=3D1989
comm=3D"tor" name=3D"lock" scontext=3Dsystem_u:system_r=
:init_t:s0
tcontext=3Dsystem_u:object_r:tor_var_lib_t:s0 tclass=3Dfile permissive=3D0
----
time->Wed Feb 19 14:02:38 2025
type=3DAVC msg=3Daudit(1739970158.881:64): avc:  denied  { read write } for=
=20
pid=3D1989 comm=3D"tor" name=3D"lock" dev=3D"dm-1&=
quot; ino=3D10144379
scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:object_r:tor_var_lib_t:s0 tclass=3Dfile permissive=3D0
----
time->Wed Feb 19 14:02:38 2025
type=3DAVC msg=3Daudit(1739970158.923:69): avc:  denied  { sys_chroot } for=
=20
pid=3D2059 comm=3D"privoxy" capability=3D18  scontext=3Dsystem_u:=
system_r:privoxy_t:s0
tcontext=3Dsystem_u:system_r:privoxy_t:s0 tclass=3Dcapability permissive=3D0
----
time->Wed Feb 19 14:02:39 2025
type=3DAVC msg=3Daudit(1739970159.968:99): avc:  denied  { nnp_transition }=
 for=20
pid=3D2313 comm=3D"(tor)" scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:system_r:tor_t:s0 tclass=3Dprocess2 permissive=3D0
----
time->Wed Feb 19 14:02:39 2025
type=3DAVC msg=3Daudit(1739970159.977:101): avc:  denied  { read write } fo=
r=20
pid=3D2313 comm=3D"tor" name=3D"lock" dev=3D"dm-1&=
quot; ino=3D10144379
scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:object_r:tor_var_lib_t:s0 tclass=3Dfile permissive=3D0
----
time->Wed Feb 19 14:02:40 2025
type=3DAVC msg=3Daudit(1739970160.062:105): avc:  denied  { getattr } for  =
pid=3D2341
comm=3D"tlp" path=3D"/proc/sys/kernel/nmi_watchdog" dev=
=3D"proc" ino=3D15616
scontext=3Dsystem_u:system_r:tlp_t:s0
tcontext=3Dsystem_u:object_r:sysctl_nmi_watchdog_t:s0 tclass=3Dfile permiss=
ive=3D0
----
time->Wed Feb 19 14:02:41 2025
type=3DAVC msg=3Daudit(1739970161.313:108): avc:  denied  { nnp_transition =
} for=20
pid=3D2525 comm=3D"(tor)" scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:system_r:tor_t:s0 tclass=3Dprocess2 permissive=3D0
----
time->Wed Feb 19 14:02:41 2025
type=3DAVC msg=3Daudit(1739970161.318:110): avc:  denied  { read write } fo=
r=20
pid=3D2525 comm=3D"tor" name=3D"lock" dev=3D"dm-1&=
quot; ino=3D10144379
scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:object_r:tor_var_lib_t:s0 tclass=3Dfile permissive=3D0
----
time->Wed Feb 19 14:02:42 2025
type=3DAVC msg=3Daudit(1739970162.489:115): avc:  denied  { nnp_transition =
} for=20
pid=3D2652 comm=3D"(tor)" scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:system_r:tor_t:s0 tclass=3Dprocess2 permissive=3D0
----
time->Wed Feb 19 14:02:42 2025
type=3DAVC msg=3Daudit(1739970162.495:117): avc:  denied  { read write } fo=
r=20
pid=3D2652 comm=3D"tor" name=3D"lock" dev=3D"dm-1&=
quot; ino=3D10144379
scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:object_r:tor_var_lib_t:s0 tclass=3Dfile permissive=3D0
----
time->Wed Feb 19 14:02:43 2025
type=3DAVC msg=3Daudit(1739970163.861:122): avc:  denied  { nnp_transition =
} for=20
pid=3D2925 comm=3D"(tor)" scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:system_r:tor_t:s0 tclass=3Dprocess2 permissive=3D0
----
time->Wed Feb 19 14:02:43 2025
type=3DAVC msg=3Daudit(1739970163.869:124): avc:  denied  { read write } fo=
r=20
pid=3D2925 comm=3D"tor" name=3D"lock" dev=3D"dm-1&=
quot; ino=3D10144379
scontext=3Dsystem_u:system_r:init_t:s0
tcontext=3Dsystem_u:object_r:tor_var_lib_t:s0 tclass=3Dfile permissive=3D0<=
/pre>

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

You are on the CC list for the bug.

=

--17399711884.0da4D1c.10849--

summary: [SELinux] blocks tor and privoxy


body:
--17400495701.8D6387.12981
Date: Thu, 20 Feb 2025 11:06: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=3D1237422

            Bug ID: 1237422
           Summary: grpc crashes consuming applications
    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: code-at-bnavigator.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Since the upgrade to grpc 1.70.1, there are at least two applications crash=
ing:

apache-arrow: FTBFS,
https://github.com/apache/arrow/issues/45120#issuecomment-2671149232

[ 2054s] Running arrow-flight-internals-test, redirecting output into
/home/abuild/rpmbuild/BUILD/apache-arrow-19.0.1-build/arrow-apache-arrow-19=
.0.1/cpp/build/build/test-logs/arrow-flight-internals-test.txt
(attempt 1/1)
[ 2054s]
/home/abuild/rpmbuild/BUILD/apache-arrow-19.0.1-build/arrow-apache-arrow-19=
.0.1/cpp/build-support/run-test.sh:
line 88: 23816 Aborted                 $TEST_EXECUTABLE "$@" > $LOGFILE.raw
2>&1
[ 2054s] WARNING: All log messages before absl::InitializeLog() is called a=
re
written to STDERR
[ 2054s] E0000 00:00:1740002057.224134   23816 metrics.cc:48] Metric name
grpc.lb.pick_first.disconnections has already been registered.

Bear: https://github.com/rizsotto/Bear/issues/619

WARNING: All log messages before absl::InitializeLog() is called are writte=
n to
STDERR
E0000 00:00:1740048296.077816 132475 metrics.cc:48] Metric name
grpc.lb.pick_first.disconnections has already been registered.

Upstream gRPC Bug: https://github.com/grpc/grpc/issues/37968
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17400495701.8D6387.12981
Date: Thu, 20 Feb 2025 11:06: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
          1237422

          Summary
          grpc crashes consuming applications

          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
          code@bnavigator.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Since the upgrade to grpc 1.70.1, there are at least two app=
lications crashing:

apache-arrow: FTBFS,
https://github.com/apache/arrow/issues/45120#issuecomment-2671149232<=
/a>

[ 2054s] Running arrow-flight-internals-test, redirecting output into
/home/abuild/rpmbuild/BUILD/apache-arrow-19.0.1-build/arrow-apache-arrow-19=
.0.1/cpp/build/build/test-logs/arrow-flight-internals-test.txt
(attempt 1/1)
[ 2054s]
/home/abuild/rpmbuild/BUILD/apache-arrow-19.0.1-build/arrow-apache-arrow-19=
.0.1/cpp/build-support/run-test.sh:
line 88: 23816 Aborted                 $TEST_EXECUTABLE "$@" =
> $LOGFILE.raw
2>&1
[ 2054s] WARNING: All log messages before absl::InitializeLog() is called a=
re
written to STDERR
[ 2054s] E0000 00:00:1740002057.224134   23816 metrics.cc:48] Metric name
grpc.lb.pick_first.disconnections has already been registered.

Bear: https://githu=
b.com/rizsotto/Bear/issues/619

WARNING: All log messages before absl::InitializeLog() is called are writte=
n to
STDERR
E0000 00:00:1740048296.077816 132475 metrics.cc:48] Metric name
grpc.lb.pick_first.disconnections has already been registered.

Upstream gRPC Bug: ht=
tps://github.com/grpc/grpc/issues/37968

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

You are on the CC list for the bug.

=

--17400495701.8D6387.12981--

summary: grpc crashes consuming applications


--17400625711.a305d45D9.13686
Date: Thu, 20 Feb 2025 14:42: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=3D1237440

            Bug ID: 1237440
           Summary: [SELinux] plymouth debug log files seem to have wrong context
    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: filippo.bonazzi-at-suse.com
        QA Contact: security-team-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

time->Wed Feb 19 20:33:09 2025
type=3DAVC msg=3Daudit(1739993589.246:359): avc:  denied  { write } for  pi=
d=3D25671
comm=3D"plymouthd" name=3D"plymouth-shutdown-debug.log" dev=3D"dm-1" ino=3D=
14375
scontext=3Dsystem_u:system_r:plymouthd_t:s0
tcontext=3Dsystem_u:object_r:var_log_t:s0 tclass=3Dfile permissive=3D0

Sure enough:
$ ls -1Z /var/log/plymouth-*
system_u:object_r:var_log_t:s0 /var/log/plymouth-debug.log
system_u:object_r:var_log_t:s0 /var/log/plymouth-shutdown-debug.log

That doesn't look right.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17400625711.a305d45D9.13686
Date: Thu, 20 Feb 2025 14:42: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
          1237440

          Summary
          [SELinux] plymouth debug log files seem to have wrong context

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

          QA Contact
          security-team@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

time->Wed Feb 19 20:33:09 2025
type=3DAVC msg=3Daudit(1739993589.246:359): avc:  denied  { write } for  pi=
d=3D25671
comm=3D"plymouthd" name=3D"plymouth-shutdown-debug.log"=
 dev=3D"dm-1" ino=3D14375
scontext=3Dsystem_u:system_r:plymouthd_t:s0
tcontext=3Dsystem_u:object_r:var_log_t:s0 tclass=3Dfile permissive=3D0

Sure enough:
$ ls -1Z /var/log/plymouth-*
system_u:object_r:var_log_t:s0 /var/log/plymouth-debug.log
system_u:object_r:var_log_t:s0 /var/log/plymouth-shutdown-debug.log

That doesn't look right.

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

You are on the CC list for the bug.

=

--17400625711.a305d45D9.13686--