--17518856821.AD35C.24383
Date: Mon, 7 Jul 2025 10:54:42 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1245969
           Summary: Java:packages/javapackages-tools: Bug: /usr/bin/build-classpath does not work without find
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: fstrba-at-suse.com
          Reporter: jslaby-at-suse.com
        QA Contact: screening-team-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I am using build-classpath in a container and find was not installed there.
javapackages-tools should Require find...
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17518856821.AD35C.24383
Date: Mon, 7 Jul 2025 10:54:42 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1245969

          Summary
          Java:packages/javapackages-tools: Bug: /usr/bin/build-classpa=
th does not work without find

          Classification
          openSUSE

          Product
          openSUSE.org

          Version
          unspecified

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          3rd party software

          Assignee
          fstrba@suse.com

          Reporter
          jslaby@suse.com

          QA Contact
          screening-team-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I am using build-classpath in a container and find was not i=
nstalled there.
javapackages-tools should Require find...

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

You are on the CC list for the bug.

=

--17518856821.AD35C.24383--


--17518982260.fcC6269.25661
Date: Mon, 7 Jul 2025 14:23: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=3D1246013

            Bug ID: 1246013
           Summary: transactional-update setup-fips with BLS (systemd-boot) leaves setup incomplete
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: MicroOS
          Assignee: screening-team-bugs-at-suse.de
          Reporter: santiago.zarate-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

After installing the system, and calling "transactional-update setup-fips" =
the
system is left with an incomplete setup, it correctly modifies the snapshot=
 #2:

Snapshot #2 has correct parameter in /etc/kernel/cmdline so does its snapsh=
ot
counterpart, but not the bootloader entry

> localhost:~ # cat /.snapshots/*/snapshot/etc/kernel/cmdline=20
> root=3D/dev/vda2 splash=3Dsilent swapaccount=3D1 systemd.show_status=3D1 =
mitigations=3Dauto quiet security=3Dselinux selinux=3D1
> root=3D/dev/vda2 splash=3Dsilent swapaccount=3D1 systemd.show_status=3D1 =
mitigations=3Dauto quiet security=3Dselinux selinux=3D1 fips=3D1
> localhost:~ # cat /etc/kernel/cmdline=20
> root=3D/dev/vda2 splash=3Dsilent swapaccount=3D1 systemd.show_status=3D1 =
mitigations=3Dauto quiet security=3Dselinux selinux=3D1 fips=3D1

However after rebooting, fips=3D1 is not present.
> localhost:~ # cat /proc/cmdline=20
> <kernel and initrd> splash=3Dsilent swapaccount=3D1 systemd.show_status=
=3D1 mitigations=3Dauto quiet security=3Dselinux selinux=3D1 rootflags=3Dsu=
bvol=3D@/.snapshots/2/snapshot systemd.machine_id=3D0fa90be4ff222f358bdfd4a=
2686b7ee
> localhost:~ # cat /boot/efi/loader/entries/opensuse-microos-* | grep  -w =
fips; echo $?
1

to fix this I had to:
- Call sdbootutil update-all-entries
- Call  update-crypto-policies --set FIPS
- reboot

> localhost:~ # cat /boot/efi/loader/entries/opensuse-microos-* | grep -q -=
w fips && echo found
> found
> localhost:~ # cat /proc/cmdline | grep -q -w fips && echo found
> found

I guess the problem(s) is related to this line(s):
https://github.com/openSUSE/transactional-update/blob/662d3b3eb2c02df0fb70a=
a7603c525ed18701379/sbin/transactional-update.in#L1259
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17518982260.fcC6269.25661
Date: Mon, 7 Jul 2025 14:23: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
          1246013

          Summary
          transactional-update setup-fips with BLS (systemd-boot) leave=
s setup incomplete

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          MicroOS

          Assignee
          screening-team-bugs@suse.de

          Reporter
          santiago.zarate@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

After installing the system, and calling "transactional=
-update setup-fips" the
system is left with an incomplete setup, it correctly modifies the snapshot=
 #2:

Snapshot #2 has correct parameter in /etc/kernel/cmdline so does its snapsh=
ot
counterpart, but not the bootloader entry

> localhost:~ # cat /.snapshots/*/snapshot/etc/ker=
nel/cmdline=20
> root=3D/dev/vda2 splash=3Dsilent swapaccount=3D1 systemd.show_status=
=3D1 mitigations=3Dauto quiet security=3Dselinux selinux=3D1
> root=3D/dev/vda2 splash=3Dsilent swapaccount=3D1 systemd.show_status=
=3D1 mitigations=3Dauto quiet security=3Dselinux selinux=3D1 fips=3D1
> localhost:~ # cat /etc/kernel/cmdline=20
> root=3D/dev/vda2 splash=3Dsilent swapaccount=3D1 systemd.show_status=
=3D1 mitigations=3Dauto quiet security=3Dselinux selinux=3D1 fips=3D1

However after rebooting, fips=3D1 is not present.
> localhost:~ # cat /proc/cmdline=20
> <kernel and initrd> splash=3Dsilent swapaccount=3D1 systemd.show=
_status=3D1 mitigations=3Dauto quiet security=3Dselinux selinux=3D1 rootfla=
gs=3Dsubvol=3D@/.snapshots/2/snapshot systemd.machine_id=3D0fa90be4ff22=
2f358bdfd4a2686b7ee
> localhost:~ # cat /boot/efi/loader/entries/opensuse-microos-* | grep  =
-w fips; echo $?
1

to fix this I had to:
- Call sdbootutil update-all-entries
- Call  update-crypto-policies --set FIPS
- reboot

> localhost:~ # cat /boot/efi/loader/entries/opens=
use-microos-* | grep -q -w fips && echo found
> found
> localhost:~ # cat /proc/cmdline | grep -q -w fips && echo found
> found

I guess the problem(s) is related to this line(s):
https://=
github.com/openSUSE/transactional-update/blob/662d3b3eb2c02df0fb70aa7603c52=
5ed18701379/sbin/transactional-update.in#L1259

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

You are on the CC list for the bug.

=

--17518982260.fcC6269.25661--


--17519607101.3a09EacEE.27466
Date: Tue, 8 Jul 2025 07:45: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=3D1246072

            Bug ID: 1246072
           Summary: Wine after update to 10.11.1.1 did not work
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: virex-at-mail.ru
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Wine after update to 10.11.1.1 did not work

errors while execute winefile:=20

winefile
002c:err:winediag:getaddrinfo Failed to resolve your host name IP
Failed loading SDL3 library.
wine: Assertion failed at address F7F31579 (thread 00bc), starting debugger=
...
00bc:fixme:process:NtCreateUserProcess unhandled output attribute 14
00bc:fixme:process:NtCreateUserProcess unhandled output attribute 149dc1c
00bc:fixme:process:NtCreateUserProcess unhandled output attribute 149fbc0
008c:err:ole:start_rpcss Failed to start RpcSs service
003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"wine=
bus"
failed to start: 1053
008c:err:ole:start_rpcss Failed to start RpcSs service
003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"wine=
usb"
failed to start: 1053
003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"wine=
bth"
failed to start: 1053
wine: Unhandled page fault on write access to 0140FFFF at address 7BF92BC5
(thread 0168), starting debugger...
0168:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr
0x7bf8e62e
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17519607101.3a09EacEE.27466
Date: Tue, 8 Jul 2025 07:45: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
          1246072

          Summary
          Wine after update to 10.11.1.1 did not work

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          virex@mail.ru

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Wine after update to 10.11.1.1 did not work

errors while execute winefile:=20

winefile
002c:err:winediag:getaddrinfo Failed to resolve your host name IP
Failed loading SDL3 library.
wine: Assertion failed at address F7F31579 (thread 00bc), starting debugger=
...
00bc:fixme:process:NtCreateUserProcess unhandled output attribute 14
00bc:fixme:process:NtCreateUserProcess unhandled output attribute 149dc1c
00bc:fixme:process:NtCreateUserProcess unhandled output attribute 149fbc0
008c:err:ole:start_rpcss Failed to start RpcSs service
003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L&quot=
;winebus"
failed to start: 1053
008c:err:ole:start_rpcss Failed to start RpcSs service
003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L&quot=
;wineusb"
failed to start: 1053
003c:err:service:process_send_command receiving command result timed out
003c:fixme:service:scmdatabase_autostart_services Auto-start service L&quot=
;winebth"
failed to start: 1053
wine: Unhandled page fault on write access to 0140FFFF at address 7BF92BC5
(thread 0168), starting debugger...
0168:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr
0x7bf8e62e

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

You are on the CC list for the bug.

=

--17519607101.3a09EacEE.27466--


body:
--17520075640.C7d4.30292
Date: Tue, 8 Jul 2025 20:46:04 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1246121
           Summary: GNU Emacs very slow since update
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: felix-at-dumbeck.net
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I updated GNU Emacs from 30.1-6.1 to 30.1-7.1 (both: GNU Emacs 30.1 (build =
1,
x86_64-suse-linux-gnu, GTK+ Version 3.24.50, cairo version 1.18.4))

Since then Emacs is very slow. For example opening a 300 bytes org file with
only flat text (no headings, blocks etc.) takes several seconds. Prior to t=
he
update opening it was instant.

Both times emacs is started with -Q. Increasing the gc threshold improves t=
he
situation slightly but not barely.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17520075640.C7d4.30292
Date: Tue, 8 Jul 2025 20:46:04 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1246121

          Summary
          GNU Emacs very slow since update

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          felix@dumbeck.net

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I updated GNU Emacs from 30.1-6.1 to 30.1-7.1 (both: GNU Ema=
cs 30.1 (build 1,
x86_64-suse-linux-gnu, GTK+ Version 3.24.50, cairo version 1.18.4))

Since then Emacs is very slow. For example opening a 300 bytes org file with
only flat text (no headings, blocks etc.) takes several seconds. Prior to t=
he
update opening it was instant.

Both times emacs is started with -Q. Increasing the gc threshold improves t=
he
situation slightly but not barely.

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

You are on the CC list for the bug.

=

--17520075640.C7d4.30292--

summary: GNU Emacs very slow since update


--17520517303.4817F0aC.31393
Date: Wed, 9 Jul 2025 09:02: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=3D1246139

            Bug ID: 1246139
           Summary: relabel with /etc as subvolume creates read-only errors
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: MicroOS
          Assignee: forgotten_u0-bnvADNc-at-user.net
          Reporter: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Relabeling of / from the initrd creates some errors:
Jul 09 08:53:40 localhost systemd[1]: Starting dracut pre-pivot and cleanup
hook...
Jul 09 08:53:40 localhost dracut-pre-pivot[808]: SELinux: relabeling root
filesystem
Jul 09 08:53:40 localhost dracut-pre-pivot[808]: SELinux: mount root read-w=
rite
and relabel
Jul 09 08:53:40 localhost dracut-pre-pivot[808]:
//lib/dracut/hooks/pre-pivot/50-selinux-microos-relabel.sh: line 80:
/sysroot-selinux/etc/selinux/.relabelled: Read-only file system
Jul 09 08:53:42 localhost dracut-pre-pivot[835]: /sbin/setfiles: Could not =
set
context for /etc/ld.so.cache:  Read-only file system

Could it be that only "/" get's mounted read-write, but not the new "/etc"
subvolume?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17520517303.4817F0aC.31393
Date: Wed, 9 Jul 2025 09:02: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
          1246139

          Summary
          relabel with /etc as subvolume creates read-only errors

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          MicroOS

          Assignee
          forgotten_u0-bnvADNc@user.net

          Reporter
          kukuk@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Relabeling of / from the initrd creates some errors:
Jul 09 08:53:40 localhost systemd[1]: Starting dracut pre-pivot and cleanup
hook...
Jul 09 08:53:40 localhost dracut-pre-pivot[808]: SELinux: relabeling root
filesystem
Jul 09 08:53:40 localhost dracut-pre-pivot[808]: SELinux: mount root read-w=
rite
and relabel
Jul 09 08:53:40 localhost dracut-pre-pivot[808]:
//lib/dracut/hooks/pre-pivot/50-selinux-microos-relabel.sh: line 80:
/sysroot-selinux/etc/selinux/.relabelled: Read-only file system
Jul 09 08:53:42 localhost dracut-pre-pivot[835]: /sbin/setfiles: Could not =
set
context for /etc/ld.so.cache:  Read-only file system

Could it be that only "/" get's mounted read-write, but not the n=
ew "/etc"
subvolume?

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

You are on the CC list for the bug.

=

--17520517303.4817F0aC.31393--


--17520628810.eC62b7Fb.32128
Date: Wed, 9 Jul 2025 12:08:01 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1246162
           Summary: [AUDIT] new tmpfiles.d rules in nix package with 2.30.0 update
    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: mrueckert-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

https://build.opensuse.org/request/show/1291337#comment-2165236
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17520628810.eC62b7Fb.32128
Date: Wed, 9 Jul 2025 12:08:01 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1246162

          Summary
          [AUDIT] new tmpfiles.d rules in nix package with 2.30.0 update

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

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

https://build.opensuse.org/request/show/1291337#comment-216=
5236

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

You are on the CC list for the bug.

=

--17520628810.eC62b7Fb.32128--


--17521800481.D2b2Cd.5592
Date: Thu, 10 Jul 2025 20:40: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=3D1246308

            Bug ID: 1246308
           Summary: iio-sensor-proxy.service keeps deactivating (missing kernel drivers)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel:Drivers
          Assignee: kernel-bugs-at-suse.de
          Reporter: dev-at-bayesians.ca
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

This bug was observed on Framework Labptop 12 (2-in-1).

On Fedora-42, the accelerometer is detected fine and it works as expected. =
 On
Fedora-rawhide as well, the accelerometer works once the workaround for
iio-sensor-proxy 3.7 is applied
(<https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/411>).
However, on Tumbleweed (20250709) the following is observed:

- iio-sensor-proxy.service stays deactivated (even after applying the
workaround
  for 3.7).  As such "monitor-sensor --accel" keeps perpetually waiting for
  "iio-sensor-proxy to appear".
- No SELinux errors are observed.
- When iio-service-proxy is run manually as root it shows a debug error abo=
ut
  missing drivers.

$> sudo systemctl status iio-sensor-proxy.service=20
[sudo] password for root:=20
=E2=97=8B iio-sensor-proxy.service - IIO Sensor Proxy service
     Loaded: loaded (/usr/lib/systemd/system/iio-sensor-proxy.service; stat=
ic)
     Active: inactive (dead)

$> sudo systemctl status iio-sensor-proxy.service --no-pager
=E2=97=8B iio-sensor-proxy.service - IIO Sensor Proxy service
     Loaded: loaded (/usr/lib/systemd/system/iio-sensor-proxy.service; stat=
ic)
     Active: inactive (dead)

Jul 10 15:43:25 lime systemd[1]: Starting IIO Sensor Proxy service...
Jul 10 15:43:26 lime systemd[1]: Started IIO Sensor Proxy service.
Jul 10 15:43:26 lime iio-sensor-prox[2981]: Not a switch
[/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/inpu=E2=80=A6i=
ties/sw]
Jul 10 15:43:26 lime iio-sensor-prox[2981]: Invalid bitmask entry for
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXV=E2=80=A68/event10
Jul 10 15:43:26 lime systemd[1]: iio-sensor-proxy.service: Deactivated
successfully.
Hint: Some lines were ellipsized, use -l to show in full.

$> sudo /usr/libexec/iio-sensor-proxy -rv
[sudo] password for root:=20
** (iio-sensor-proxy:4539): DEBUG: 16:05:51.670: Starting iio-sensor-proxy
version 3.7

** (iio-sensor-proxy:4539): WARNING **: 16:05:51.683: Not a switch
[/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input18/=
../capabilities/sw]

** (iio-sensor-proxy:4539): WARNING **: 16:05:51.683: Invalid bitmask entry=
 for
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input18/e=
vent10
** (iio-sensor-proxy:4539): DEBUG: 16:05:51.684: No sensors or missing kern=
el
drivers for the sensors
0

$> sudo ausearch -m avc,user_avc,selinux_err,user_selinux_err -ts boot
<no matches>

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D

After comparing the output of lsmod between Fedora and Tumbleweed, it seems=
 the
following relevant drivers that are present in Fedora are missing in
Tumbleweed:

- core-ec-sensors
- core-ec-sensors-core
- core-ec-lid-angle

It's possible that the above is the root cause, but I am speculating; I don=
't
know how to get an appropriate build for those modules that I can test with.

Output of attempting to load the above modules in Tumbleweed:

$> sudo modprobe core-ec-sensors
modprobe: FATAL: Module core-ec-sensors not found in directory
/usr/lib/modules/6.15.5-1-default

$> sudo modprobe core-ec-sensors-core
modprobe: FATAL: Module core-ec-sensors-core not found in directory
/usr/lib/modules/6.15.5-1-default

$> sudo modprobe core-ec-lid-angle
modprobe: FATAL: Module core-ec-lid-angle not found in directory
/usr/lib/modules/6.15.5-1-default
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17521800481.D2b2Cd.5592
Date: Thu, 10 Jul 2025 20:40: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
          1246308

          Summary
          iio-sensor-proxy.service keeps deactivating (missing kernel d=
rivers)

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel:Drivers

          Assignee
          kernel-bugs@suse.de

          Reporter
          dev@bayesians.ca

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

This bug was observed on Framework Labptop 12 (2-in-1).

On Fedora-42, the accelerometer is detected fine and it works as expected. =
 On
Fedora-rawhide as well, the accelerometer works once the workaround for
iio-sensor-proxy 3.7 is applied
(<https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/4=
11>).
However, on Tumbleweed (20250709) the following is observed:

- iio-sensor-proxy.service stays deactivated (even after applying the
workaround
  for 3.7).  As such "monitor-sensor --accel" keeps perpetually w=
aiting for
  "iio-sensor-proxy to appear".
- No SELinux errors are observed.
- When iio-service-proxy is run manually as root it shows a debug error abo=
ut
  missing drivers.

$> sudo systemctl status iio-sensor-proxy.service=20
[sudo] password for root:=20
=E2=97=8B iio-sensor-proxy.service - IIO Sensor Proxy service
     Loaded: loaded (/usr/lib/systemd/system/iio-sensor-proxy.service; stat=
ic)
     Active: inactive (dead)

$> sudo systemctl status iio-sensor-proxy.service --no-pager
=E2=97=8B iio-sensor-proxy.service - IIO Sensor Proxy service
     Loaded: loaded (/usr/lib/systemd/system/iio-sensor-proxy.service; stat=
ic)
     Active: inactive (dead)

Jul 10 15:43:25 lime systemd[1]: Starting IIO Sensor Proxy service...
Jul 10 15:43:26 lime systemd[1]: Started IIO Sensor Proxy service.
Jul 10 15:43:26 lime iio-sensor-prox[2981]: Not a switch
[/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/inpu=E2=80=A6i=
ties/sw]
Jul 10 15:43:26 lime iio-sensor-prox[2981]: Invalid bitmask entry for
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXV=E2=80=A68/event10
Jul 10 15:43:26 lime systemd[1]: iio-sensor-proxy.service: Deactivated
successfully.
Hint: Some lines were ellipsized, use -l to show in full.

$> sudo /usr/libexec/iio-sensor-proxy -rv
[sudo] password for root:=20
** (iio-sensor-proxy:4539): DEBUG: 16:05:51.670: Starting iio-sensor-proxy
version 3.7

** (iio-sensor-proxy:4539): WARNING **: 16:05:51.683: Not a switch
[/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input18/=
../capabilities/sw]

** (iio-sensor-proxy:4539): WARNING **: 16:05:51.683: Invalid bitmask entry=
 for
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input18/e=
vent10
** (iio-sensor-proxy:4539): DEBUG: 16:05:51.684: No sensors or missing kern=
el
drivers for the sensors
0

$> sudo ausearch -m avc,user_avc,selinux_err,user_selinux_err -ts boot
<no matches>

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D

After comparing the output of lsmod between Fedora and Tumbleweed, it seems=
 the
following relevant drivers that are present in Fedora are missing in
Tumbleweed:

- core-ec-sensors
- core-ec-sensors-core
- core-ec-lid-angle

It's possible that the above is the root cause, but I am speculating; I don=
't
know how to get an appropriate build for those modules that I can test with.

Output of attempting to load the above modules in Tumbleweed:

$> sudo modprobe core-ec-sensors
modprobe: FATAL: Module core-ec-sensors not found in directory
/usr/lib/modules/6.15.5-1-default

$> sudo modprobe core-ec-sensors-core
modprobe: FATAL: Module core-ec-sensors-core not found in directory
/usr/lib/modules/6.15.5-1-default

$> sudo modprobe core-ec-lid-angle
modprobe: FATAL: Module core-ec-lid-angle not found in directory
/usr/lib/modules/6.15.5-1-default

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

You are on the CC list for the bug.

=

--17521800481.D2b2Cd.5592--


--17522255580.23FF5813.6879
Date: Fri, 11 Jul 2025 09:19:18 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1246332
           Summary: [Build 20250709] openQA test fails in ioctl10
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/5166571/modules/ioct
                    l10/steps/7
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

Created attachment 884085
  --> https://bugzilla.suse.com/attachment.cgi?id=3D884085&action=3Dedit
test log

## Observation

openQA test in scenario
opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-ltp-syscalls@aarch64-HD20G
fails in
[ioctl10](https://openqa.opensuse.org/tests/5166571/modules/ioctl10/steps/7)

Main package changes in snapshot 20250709:
Packages changed:
  MozillaFirefox (139.0.4 -> 140.0.2)
  coreutils
  coreutils-systemd
  kernel-source (6.15.4 -> 6.15.5)
  libvirt
  mdevctl
  mozilla-nss (3.110 -> 3.112)
  myrlyn (0.9.6 -> 0.9.7)
  ncompress
  nghttp2 (1.65.0 -> 1.66.0)
  openSUSE-release (20250708 -> 20250709)
  opensc
  openssl-3 (3.5.0 -> 3.5.1)
  openssl (3.5.0 -> 3.5.1)
  patterns-base
  raptor
  selinux-policy
  spu-tools

The kernel update looks like a good candidate for the regression.

## Test suite description
/var/tmp: https://progress.opensuse.org/issues/155017
LTP_TAINT_EXPECTED=3D0x8001b801

## Reproducible

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

## Expected result

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

## Further details

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

--17522255580.23FF5813.6879
Date: Fri, 11 Jul 2025 09:19:18 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1246332

          Summary
          [Build 20250709] openQA test fails in ioctl10

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          URL
          https://openqa.opensuse.org/tests/5166571/modules/ioctl10/ste=
ps/7

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          guillaume.gardet@arm.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

Created attachment 884085 [detai=
ls]
test log

## Observation

openQA test in scenario
opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-ltp-syscalls@aarch64-=
HD20G
fails in
[ioctl10](https://openqa.opensuse.org/tests/5166571/modules/ioctl10/step=
s/7)

Main package changes in snapshot 20250709:
Packages changed:
  MozillaFirefox (139.0.4 -> 140.0.2)
  coreutils
  coreutils-systemd
  kernel-source (6.15.4 -> 6.15.5)
  libvirt
  mdevctl
  mozilla-nss (3.110 -> 3.112)
  myrlyn (0.9.6 -> 0.9.7)
  ncompress
  nghttp2 (1.65.0 -> 1.66.0)
  openSUSE-release (20250708 -> 20250709)
  opensc
  openssl-3 (3.5.0 -> 3.5.1)
  openssl (3.5.0 -> 3.5.1)
  patterns-base
  raptor
  selinux-policy
  spu-tools

The kernel update looks like a good candidate for the regression.

## Test suite description
/var/tmp: https://p=
rogress.opensuse.org/issues/155017
LTP_TAINT_EXPECTED=3D0x8001b801

## Reproducible

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

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa=
.opensuse.org/tests/latest?arch=3Daarch64&distri=3Dopensuse&flavor=
=3DJeOS-for-AArch64&machine=3Daarch64-HD20G&test=3Djeos-ltp-syscall=
s&version=3DTumbleweed)

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

You are on the CC list for the bug.

=

--17522255580.23FF5813.6879--


--17522415603.B7f57b1.8220
Date: Fri, 11 Jul 2025 13:46:00 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1246377
           Summary: VUL-0: CVE-2025-53630: llamacpp: integer overflow in the gguf_init_from_file_impl function in ggml/src/gguf.cpp can lead to heap out-of-bounds read/write
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/463630/
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: eyadlorenzo-at-gmail.com
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: camila.matos-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

llama.cpp is an inference of several LLM models in C/C++. Integer Overflow =
in
the gguf_init_from_file_impl function in ggml/src/gguf.cpp can lead to Heap
Out-of-Bounds Read/Write. This vulnerability is fixed in commit
26a48ad699d50b6268900062661bd22f3e792579.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-53630
https://www.cve.org/CVERecord?id=3DCVE-2025-53630
https://github.com/ggml-org/llama.cpp/commit/26a48ad699d50b6268900062661bd2=
2f3e792579
https://github.com/ggml-org/llama.cpp/security/advisories/GHSA-vgg9-87g3-85=
w8
https://github.com/CVEProject/cvelistV5/blob/main//cves/2025/53xxx/CVE-2025=
-53630.json
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17522415603.B7f57b1.8220
Date: Fri, 11 Jul 2025 13:46:00 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1246377

          Summary
          VUL-0: CVE-2025-53630: llamacpp: integer overflow in the gguf=
_init_from_file_impl function in ggml/src/gguf.cpp can lead to heap out-of-=
bounds read/write

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Security

          Assignee
          eyadlorenzo@gmail.com

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          camila.matos@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

llama.cpp is an inference of several LLM models in C/C++. In=
teger Overflow in
the gguf_init_from_file_impl function in ggml/src/gguf.cpp can lead to Heap
Out-of-Bounds Read/Write. This vulnerability is fixed in commit
26a48ad699d50b6268900062661bd22f3e792579.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-53630
https://www.c=
ve.org/CVERecord?id=3DCVE-2025-53630
https://github.com/ggml-org/llama.cpp/commit/26a48ad=
699d50b6268900062661bd22f3e792579
https://github.com/ggml-org/llama.cpp/security/advisories/GH=
SA-vgg9-87g3-85w8
https://github.com/CVEProject/cvelistV5/blob/main//=
cves/2025/53xxx/CVE-2025-53630.json

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

You are on the CC list for the bug.

=

--17522415603.B7f57b1.8220--


--17523006100.4c5AE3bC.9155
Date: Sat, 12 Jul 2025 06:10: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=3D1246408

            Bug ID: 1246408
           Summary: Cockpit fails to start if a user has customized /etc/nsswitch.conf
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Cockpit
          Assignee: Cockpit-bugs-at-suse.de
          Reporter: lbeltrame-at-kde.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

On my machines I run SSSD, so my /etc/nsswitch.configuration is like this
(snippet):

passwd:         compat systemd sss
group:          compat [SUCCESS=3Dmerge] systemd sss
shadow:         compat systemd
sudoers:        files sss

However, /usr/libexec/check_cockpit_users has this line:

if [ -f /etc/nsswitch.conf ]; then
    grep -Exq "passwd:.*?compat systemd" /etc/nsswitch.conf
    if [ $? -ne 0 ]; then
        echo "/etc/nsswitch.conf is out of date, please update it from
/usr/etc/nsswitch.conf to use cockpit"
        failed=3Dtrue
    fi
fi

So if "compat systemd" is not last in the passwd line, it will fail, and the
service startup will fail *silently* (systemd will report a failed executio=
n,
but no data will be reported to the journal). I workarounded this issue by
putting in "sss" first.

IMO the regex should just check for the presence of "compat systemd" regard=
less
of the order that is there.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17523006100.4c5AE3bC.9155
Date: Sat, 12 Jul 2025 06:10: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
          1246408

          Summary
          Cockpit fails to start if a user has customized /etc/nsswitch=
.conf

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Cockpit

          Assignee
          Cockpit-bugs@suse.de

          Reporter
          lbeltrame@kde.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

On my machines I run SSSD, so my /etc/nsswitch.configuration=
 is like this
(snippet):

passwd:         compat systemd sss
group:          compat [SUCCESS=3Dmerge] systemd sss
shadow:         compat systemd
sudoers:        files sss

However, /usr/libexec/check_cockpit_users has this line:

if [ -f /etc/nsswitch.conf ]; then
    grep -Exq "passwd:.*?compat systemd" /etc/nsswitch.conf
    if [ $? -ne 0 ]; then
        echo "/etc/nsswitch.conf is out of date, please update it from
/usr/etc/nsswitch.conf to use cockpit"
        failed=3Dtrue
    fi
fi

So if "compat systemd" is not last in the passwd line, it will fa=
il, and the
service startup will fail *silently* (systemd will report a failed executio=
n,
but no data will be reported to the journal). I workarounded this issue by
putting in "sss" first.

IMO the regex should just check for the presence of "compat systemd&qu=
ot; regardless
of the order that is there.

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

You are on the CC list for the bug.

=

--17523006100.4c5AE3bC.9155--


--17524923464.E8Ae.10972
Date: Mon, 14 Jul 2025 11:25: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=3D1246463

            Bug ID: 1246463
           Summary: VUL-0: CVE-2025-53549: fractal: matrix-sdk: SQL injection in the EventCache implementation
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/463610/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: bjorn.lie-at-gmail.com
          Reporter: camila.matos-at-suse.com
        QA Contact: security-team-at-suse.de
                CC: camila.matos-at-suse.com, security-team-at-suse.de,
                    smash_bz-at-suse.de
            Blocks: 1246458
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

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

The Matrix Rust SDK is a collection of libraries that make it easier to bui=
ld
Matrix clients in Rust. An SQL injection vulnerability in the
EventCache::find_event_with_relations method of matrix-sdk 0.11 and 0.12 al=
lows
malicious room members to execute arbitrary SQL commands in Matrix clients =
that
directly pass relation types provided by those room members into this metho=
d,
when used with the default sqlite-based store backend. Exploitation is
unlikely, as no known clients currently use the API in this manner. This
vulnerability is fixed in 0.13.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-53549
https://www.cve.org/CVERecord?id=3DCVE-2025-53549
https://github.com/matrix-org/matrix-rust-sdk/pull/4849
https://github.com/matrix-org/matrix-rust-sdk/security/advisories/GHSA-275g=
-g844-73jh
https://github.com/CVEProject/cvelistV5/blob/main//cves/2025/53xxx/CVE-2025=
-53549.json
https://bugzilla.redhat.com/show_bug.cgi?id=3D2379350
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17524923464.E8Ae.10972
Date: Mon, 14 Jul 2025 11:25: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
          1246463

          Summary
          VUL-0: CVE-2025-53549: fractal: matrix-sdk: SQL injection in =
the EventCache implementation

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          bjorn.lie@gmail.com

          Reporter
          camila.matos@suse.com

          QA Contact
          security-team@suse.de

          CC
          camila.matos@suse.com, security-team@suse.de, smash_b=
z@suse.de

          Blocks
          1246458

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

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

The Matrix Rust SDK is a collection of libraries that make it easier to bui=
ld
Matrix clients in Rust. An SQL injection vulnerability in the
EventCache::find_event_with_relations method of matrix-sdk 0.11 and 0.12 al=
lows
malicious room members to execute arbitrary SQL commands in Matrix clients =
that
directly pass relation types provided by those room members into this metho=
d,
when used with the default sqlite-based store backend. Exploitation is
unlikely, as no known clients currently use the API in this manner. This
vulnerability is fixed in 0.13.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-53549
https://www.c=
ve.org/CVERecord?id=3DCVE-2025-53549
https:/=
/github.com/matrix-org/matrix-rust-sdk/pull/4849
https://github.com/matrix-org/matrix-rust-sdk/securi=
ty/advisories/GHSA-275g-g844-73jh
https://github.com/CVEProject/cvelistV5/blob/main//=
cves/2025/53xxx/CVE-2025-53549.json
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2379350

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

You are on the CC list for the bug.

=

--17524923464.E8Ae.10972--


--17524989240.Bec3E.11449
Date: Mon, 14 Jul 2025 13:15:23 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1246476
           Summary: The tumbleweed kernel is limited to 64 PCI devices on s390x
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: S/390-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: miroslav.franc-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

We should set CONFIG_PCI_NR_FUNCTIONS to 512 to be in line with SLES.  The =
64
limit is too low and can be easily exceeded.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17524989240.Bec3E.11449
Date: Mon, 14 Jul 2025 13:15: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
          1246476

          Summary
          The tumbleweed kernel is limited to 64 PCI devices on s390x

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          S/390-64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          miroslav.franc@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

We should set CONFIG_PCI_NR_FUNCTIONS to 512 to be in line w=
ith SLES.  The 64
limit is too low and can be easily exceeded.

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

You are on the CC list for the bug.

=

--17524989240.Bec3E.11449--


body:
--17525622220.5C8F9cFA.13359
Date: Tue, 15 Jul 2025 06:50:22 +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=3D1246516

            Bug ID: 1246516
           Summary: Update xkeyboard-config to 2.45
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: gfx-bugs-at-suse.de
          Reporter: opensuse-at-wismill.eu
        QA Contact: gfx-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

xkeyboard-config 2.45 has be published on 2025-06-08

- Announcement: https://groups.google.com/a/listserv.bat.ru/g/xkb/c/woR9btf=
0M7A
- Release notes: https://xkeyboard-config.freedesktop.org/blog/2-45-release/

Note that it introduces breaking changes [documented in the release
notes](https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/b=
lob/master/ChangeLog.md?ref_type=3Dheads#breaking-changes-2).

However, it seems that some distros had some trouble upgrading:

- [Gentoo](https://bugs.gentoo.org/957712)
- [Termux](https://github.com/termux/termux-packages/issues/25005)
-
[ArchLinux](https://gitlab.archlinux.org/archlinux/packaging/packages/xkeyb=
oard-config/-/issues/1)

I am not much familiar with the packaging here, but hopefully these links w=
ill
help openSUSE to avoid hiccups with this upgrade.

Note that it is common that users have custom files under `/usr/share/X11/x=
kb`:
e.g. the file `/usr/share/X11/xkb/symbols/custom` is not provided by
`xkeyboard-config` but intended as an [*official*
hack](https://who-t.blogspot.com/2021/02/a-pre-supplied-custom-keyboard-lay=
out.html)
for **X11** sessions, which cannot use the modern [user
configuration](https://xkbcommon.org/doc/current/user-configuration.html)
offered by libxkbcommon for Wayland sessions.

Is it possible for the installer to *move* an existing regular dir, i.e. he=
re
move `/usr/share/X11/xkb/` to `/usr/share/xkeyboard-config-2` and *then* cr=
eate
the symlink `/usr/share/X11/xkb/` =E2=86=92 `/usr/share/xkeyboard-config-2`?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17525622220.5C8F9cFA.13359
Date: Tue, 15 Jul 2025 06:50:22 +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
          1246516

          Summary
          Update xkeyboard-config to 2.45

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X.Org

          Assignee
          gfx-bugs@suse.de

          Reporter
          opensuse@wismill.eu

          QA Contact
          gfx-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

xkeyboard-config 2.45 has be published on 2025-06-08

- Announcement: https://groups.google.com/a/listserv.bat.ru/g/xkb/c/woR9bt=
f0M7A
- Release notes: https://xkeyboard-config.freedesktop.org/blog/2-45-release/</=
a>

Note that it introduces breaking changes [documented in the release
notes](htt=
ps://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/blob/master=
/ChangeLog.md?ref_type=3Dheads#breaking-changes-2).

However, it seems that some distros had some trouble upgrading:

- [Gentoo](https://bugs.gentoo.o=
rg/957712)
- [Termux](https://github.com/termux/termux-packages/issues/25005)
-
[ArchLinux](https://gitlab.archlinux.org/archlinux/p=
ackaging/packages/xkeyboard-config/-/issues/1)

I am not much familiar with the packaging here, but hopefully these links w=
ill
help openSUSE to avoid hiccups with this upgrade.

Note that it is common that users have custom files under `/usr/share/X11/x=
kb`:
e.g. the file `/usr/share/X11/xkb/symbols/custom` is not provided by
`xkeyboard-config` but intended as an [*official*
hack](https://who-t.blogspot.com/2021/02/a-pre-supplied-cust=
om-keyboard-layout.html)
for **X11** sessions, which cannot use the modern [user
configuration](https://xkbcommon.org/doc/current/user-configuration.html)
offered by libxkbcommon for Wayland sessions.

Is it possible for the installer to *move* an existing regular dir, i.e. he=
re
move `/usr/share/X11/xkb/` to `/usr/share/xkeyboard-config-2` and *then* cr=
eate
the symlink `/usr/share/X11/xkb/` =E2=86=92 `/usr/share/xkeyboard-config-2`=
?

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

You are on the CC list for the bug.

=

--17525622220.5C8F9cFA.13359--

summary: Update xkeyboard-config to 2.45


body:
--17526028802.4D5E4A.14
Date: Tue, 15 Jul 2025 18:08:00 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1246558
           Summary: VUL-0: chromium release 138.0.7204.157
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 16.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: Andreas.Stieger-at-gmx.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: ro-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

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

Fixed in Chromium 138.0.7204.157

CVE-2025-7656: Integer overflow in V8
CVE-2025-6558: Incorrect validation of untrusted input in ANGLE and GPU
CVE-2025-7657: Use after free in WebRTC

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

--17526028802.4D5E4A.14
Date: Tue, 15 Jul 2025 18:08:00 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1246558

          Summary
          VUL-0: chromium release 138.0.7204.157

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 16.0

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Security

          Assignee
          Andreas.Stieger@gmx.de

          Reporter
          Andreas.Stieger@gmx.de

          QA Contact
          qa-bugs@suse.de

          CC
          ro@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

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

Fixed in Chromium 138.0.7204.157

CVE-2025-7656: Integer overflow in V8
CVE-2025-6558: Incorrect validation of untrusted input in ANGLE and GPU
CVE-2025-7657: Use after free in WebRTC

Google is aware that an exploit for CVE-2025-6558 exists in the wild.

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

You are on the CC list for the bug.

=

--17526028802.4D5E4A.14--

summary: VUL-0: chromium release 138.0.7204.157


--17526043121.eebFa8a.53
Date: Tue, 15 Jul 2025 18:31:52 +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=3D1246561

            Bug ID: 1246561
           Summary: rpm -ev kernel-default-6.15.3-1.1 pegs CPU for >10 minutes before removing kernel
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mrmazda-at-earthlink.net
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Original Summary:
rpm -ev kernel-default-6.15.3-1.1 pegs CPU for >10 minutes before removing
kernel

# rpm -ev kernel-default-6.15.3-1.1
## (>18 minutes later)
Preparing packages...
kernel-default-6.15.3-1.1.x86_64
# top
top - 13:35:53 up 31 min,  3 users,  load average: 1.00, 0.90, 0.64
Tasks: 166 total, 2 running, 164 sleep, 0 d-sleep, 0 stopped, 0 zombie
%Cpu(s): 21.0 us,  4.1 sy,  0.0 ni, 74.9 id,  0.0 wa,  0.0 hi,  0.0 si,  0.=
0 st
MiB Mem : 6860.180 total, 4130.559 free,  581.926 used, 2447.727 buff/cache
MiB Swap:    0.000 total,    0.000 free,    0.000 used. 6278.254 avail Mem

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMM=
AND
  11662 root      20   0   82216  77684  29212 R 100.0 1.106   9:17.89 rpm
# inxi -Saz --za --hostname
System:
  Host: ga88x Kernel: 6.15.6-1-default arch: x86_64 bits: 64 compiler: gcc
    v: 15.1.1 clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=3D/boot/vmlinuz root=3DLABEL=3D<filter> noresume
    ipv6.disable=3D1 net.ifnames=3D0 mitigations=3Doff consoleblank=3D0
    radeon.cik_support=3D0 amdgpu.cik_support=3D1
  Console: pty pts/1 wm: kwin_x11 DM: SDDM Distro: openSUSE Tumbleweed
    20250714
# inxi -CMz --za
Machine:
  Type: Desktop Mobo: Gigabyte model: F2A88XM-D3H v: x.x serial: N/A
    UEFI: American Megatrends v: F9 date: 12/25/2015
CPU:
  Info: quad core model: AMD PRO A10-8750B R7 12 Compute Cores 4C+8G bits: =
64
    type: MCP cache: L2: 4 MiB
  Speed (MHz): avg: 1400 min/max: 1400/3600 cores: 1: 1400 2: 1400 3: 1400
    4: 1400
# mount | grep ' / '
/dev/sda7 on / type ext4 (rw,noatime)
# df /
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/sda7        8043916 6341084   1276848  84% /
# /usr/lib64/ld-linux-x86-64.so.2 --help | tail -11
This program interpreter self-identifies as: /lib64/ld-linux-x86-64.so.2

Shared library search path:
  (libraries located via /etc/ld.so.cache)
  /lib64 (system search path)
  /usr/lib64 (system search path)

Subdirectories of glibc-hwcaps directories, in priority order:
  x86-64-v4
  x86-64-v3
  x86-64-v2 (supported, searched)
# rpm -qa | grep -iE 'boot|grub' | sort
efibootmgr-18-1.8.x86_64
grub2-2.12-54.1.x86_64
grub2-common-2.12-54.1.x86_64
grub2-i386-pc-2.12-54.1.noarch
grub2-x86_64-efi-2.12-54.1.noarch
ruby3.4-rubygem-cfa_grub2-2.0.0-1.24.x86_64
update-bootloader-1.24-1.2.x86_64
yast2-bootloader-5.0.21-1.1.x86_64
# efibootmgr
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001
Boot0000* opensusetw=20=20=20
HD(1,GPT,5b33...,0x800,0xa0000)/File(\EFI\opensusetw\grubx64.efi)
Boot0001* UEFI OS=20=20=20=20=20=20
HD(1,GPT,5b33...,0x800,0xa0000)/File(\EFI\BOOT\BOOTX64.EFI)
#

When this happened [yesterday?,Sunday?,Friday?], on a different TW
PC/installation, I thought it must be a fluke. After 5-10 minutes waiting a=
nd
then Ctrl-C, zypper rm had no problem removing same kernel in normal short
order.

Today I waited longer after pegged CPU started. After 18 minutes, command
completed. I see nothing in dmesg to explain this.
# dmesg | tail -30
[  440.223879] [      T1] systemd[1]: Starting Rule-based Manager for Device
Events and Files...
[  440.264734] [   T1592] systemd-journald[1592]: Collecting audit messages=
 is
disabled.
[  440.314108] [      T1] systemd[1]: Started Rule-based Manager for Device
Events and Files.
[  440.326424] [      T1] systemd[1]: Started Journal Service.
[ 1039.021598] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[ 1039.021619] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CRTC:41:crtc-0] [FB:55] #connectors=3D1 (x y) (0 0)
[ 1039.021640] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:49:DVI-D-1] to [CRTC:41:crtc-0]
[ 1039.021651] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:51:HDMI-A-1] to [CRTC:43:crtc-1]
[ 1039.021665] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[ 1039.021672] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CRTC:43:crtc-1] [FB:55] #connectors=3D1 (x y) (0 0)
[ 1039.021684] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:49:DVI-D-1] to [CRTC:41:crtc-0]
[ 1039.021693] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:51:HDMI-A-1] to [CRTC:43:crtc-1]
[ 1043.235045] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[ 1043.235067] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CRTC:41:crtc-0] [FB:55] #connectors=3D1 (x y) (0 0)
[ 1043.235088] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:49:DVI-D-1] to [CRTC:41:crtc-0]
[ 1043.235098] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:51:HDMI-A-1] to [CRTC:43:crtc-1]
[ 1043.235111] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[ 1043.235119] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CRTC:43:crtc-1] [FB:55] #connectors=3D1 (x y) (0 0)
[ 1043.235130] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:49:DVI-D-1] to [CRTC:41:crtc-0]
[ 1043.235140] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:51:HDMI-A-1] to [CRTC:43:crtc-1]
[ 1047.086601] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[ 1047.086624] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CRTC:41:crtc-0] [FB:55] #connectors=3D1 (x y) (0 0)
[ 1047.086645] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:49:DVI-D-1] to [CRTC:41:crtc-0]
[ 1047.086655] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:51:HDMI-A-1] to [CRTC:43:crtc-1]
[ 1047.086668] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[ 1047.086675] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CRTC:43:crtc-1] [FB:55] #connectors=3D1 (x y) (0 0)
[ 1047.086687] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:49:DVI-D-1] to [CRTC:41:crtc-0]
[ 1047.086696] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:51:HDMI-A-1] to [CRTC:43:crtc-1]
[ 1108.197140] [   T8114] block sda: the capability attribute has been
deprecated.
[ 1112.445043] [   T9547] NET: Registered PF_ALG protocol family
#
Journal didn't even have that much to report during the pegged CPU period.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17526043121.eebFa8a.53
Date: Tue, 15 Jul 2025 18:31:52 +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
          1246561

          Summary
          rpm -ev kernel-default-6.15.3-1.1 pegs CPU for >10 minutes=
 before removing kernel

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          mrmazda@earthlink.net

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Original Summary:
rpm -ev kernel-default-6.15.3-1.1 pegs CPU for >10 minutes before removi=
ng
kernel

# rpm -ev kernel-default-6.15.3-1.1
## (>18 minutes later)
Preparing packages...
kernel-default-6.15.3-1.1.x86_64
# top
top - 13:35:53 up 31 min,  3 users,  load average: 1.00, 0.90, 0.64
Tasks: 166 total, 2 running, 164 sleep, 0 d-sleep, 0 stopped, 0 zombie
%Cpu(s): 21.0 us,  4.1 sy,  0.0 ni, 74.9 id,  0.0 wa,  0.0 hi,  0.0 si,  0.=
0 st
MiB Mem : 6860.180 total, 4130.559 free,  581.926 used, 2447.727 buff/cache
MiB Swap:    0.000 total,    0.000 free,    0.000 used. 6278.254 avail Mem

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMM=
AND
  11662 root      20   0   82216  77684  29212 R 100.0 1.106   9:17.89 rpm
# inxi -Saz --za --hostname
System:
  Host: ga88x Kernel: 6.15.6-1-default arch: x86_64 bits: 64 compiler: gcc
    v: 15.1.1 clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=3D/boot/vmlinuz root=3DLABEL=3D<filter> no=
resume
    ipv6.disable=3D1 net.ifnames=3D0 mitigations=3Doff consoleblank=3D0
    radeon.cik_support=3D0 amdgpu.cik_support=3D1
  Console: pty pts/1 wm: kwin_x11 DM: SDDM Distro: openSUSE Tumbleweed
    20250714
# inxi -CMz --za
Machine:
  Type: Desktop Mobo: Gigabyte model: F2A88XM-D3H v: x.x serial: N/A
    UEFI: American Megatrends v: F9 date: 12/25/2015
CPU:
  Info: quad core model: AMD PRO A10-8750B R7 12 Compute Cores 4C+8G bits: =
64
    type: MCP cache: L2: 4 MiB
  Speed (MHz): avg: 1400 min/max: 1400/3600 cores: 1: 1400 2: 1400 3: 1400
    4: 1400
# mount | grep ' / '
/dev/sda7 on / type ext4 (rw,noatime)
# df /
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/sda7        8043916 6341084   1276848  84% /
# /usr/lib64/ld-linux-x86-64.so.2 --help | tail -11
This program interpreter self-identifies as: /lib64/ld-linux-x86-64.so.2

Shared library search path:
  (libraries located via /etc/ld.so.cache)
  /lib64 (system search path)
  /usr/lib64 (system search path)

Subdirectories of glibc-hwcaps directories, in priority order:
  x86-64-v4
  x86-64-v3
  x86-64-v2 (supported, searched)
# rpm -qa | grep -iE 'boot|grub' | sort
efibootmgr-18-1.8.x86_64
grub2-2.12-54.1.x86_64
grub2-common-2.12-54.1.x86_64
grub2-i386-pc-2.12-54.1.noarch
grub2-x86_64-efi-2.12-54.1.noarch
ruby3.4-rubygem-cfa_grub2-2.0.0-1.24.x86_64
update-bootloader-1.24-1.2.x86_64
yast2-bootloader-5.0.21-1.1.x86_64
# efibootmgr
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001
Boot0000* opensusetw=20=20=20
HD(1,GPT,5b33...,0x800,0xa0000)/File(\EFI\opensusetw\grubx64.efi)
Boot0001* UEFI OS=20=20=20=20=20=20
HD(1,GPT,5b33...,0x800,0xa0000)/File(\EFI\BOOT\BOOTX64.EFI)
#

When this happened [yesterday?,Sunday?,Friday?], on a different TW
PC/installation, I thought it must be a fluke. After 5-10 minutes waiting a=
nd
then Ctrl-C, zypper rm had no problem removing same kernel in normal short
order.

Today I waited longer after pegged CPU started. After 18 minutes, command
completed. I see nothing in dmesg to explain this.
# dmesg | tail -30
[  440.223879] [      T1] systemd[1]: Starting Rule-based Manager for Device
Events and Files...
[  440.264734] [   T1592] systemd-journald[1592]: Collecting audit messages=
 is
disabled.
[  440.314108] [      T1] systemd[1]: Started Rule-based Manager for Device
Events and Files.
[  440.326424] [      T1] systemd[1]: Started Journal Service.
[ 1039.021598] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[ 1039.021619] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CRTC:41:crtc-0] [FB:55] #connectors=3D1 (x y) (0 0)
[ 1039.021640] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:49:DVI-D-1] to [CRTC:41:crtc-0]
[ 1039.021651] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:51:HDMI-A-1] to [CRTC:43:crtc-1]
[ 1039.021665] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[ 1039.021672] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CRTC:43:crtc-1] [FB:55] #connectors=3D1 (x y) (0 0)
[ 1039.021684] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:49:DVI-D-1] to [CRTC:41:crtc-0]
[ 1039.021693] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:51:HDMI-A-1] to [CRTC:43:crtc-1]
[ 1043.235045] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[ 1043.235067] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CRTC:41:crtc-0] [FB:55] #connectors=3D1 (x y) (0 0)
[ 1043.235088] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:49:DVI-D-1] to [CRTC:41:crtc-0]
[ 1043.235098] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:51:HDMI-A-1] to [CRTC:43:crtc-1]
[ 1043.235111] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[ 1043.235119] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CRTC:43:crtc-1] [FB:55] #connectors=3D1 (x y) (0 0)
[ 1043.235130] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:49:DVI-D-1] to [CRTC:41:crtc-0]
[ 1043.235140] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:51:HDMI-A-1] to [CRTC:43:crtc-1]
[ 1047.086601] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[ 1047.086624] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CRTC:41:crtc-0] [FB:55] #connectors=3D1 (x y) (0 0)
[ 1047.086645] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:49:DVI-D-1] to [CRTC:41:crtc-0]
[ 1047.086655] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:51:HDMI-A-1] to [CRTC:43:crtc-1]
[ 1047.086668] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[ 1047.086675] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CRTC:43:crtc-1] [FB:55] #connectors=3D1 (x y) (0 0)
[ 1047.086687] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:49:DVI-D-1] to [CRTC:41:crtc-0]
[ 1047.086696] [    T405] amdgpu 0000:00:01.0: [drm:drm_crtc_helper_set_con=
fig]
[CONNECTOR:51:HDMI-A-1] to [CRTC:43:crtc-1]
[ 1108.197140] [   T8114] block sda: the capability attribute has been
deprecated.
[ 1112.445043] [   T9547] NET: Registered PF_ALG protocol family
#
Journal didn't even have that much to report during the pegged CPU period.<=
/pre>

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

You are on the CC list for the bug.

=

--17526043121.eebFa8a.53--


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

Aeon has historically removed setting `ro` as a mount attribute in its fstab
due to race conditions such as seen in
https://github.co=
m/systemd/systemd/issues/927

ro=3Dvfs is now a thing that should allow the use of a mount attribute with=
out
hitting that race condition

This makes things easier to detect whether or not / is intended to be read-=
only

Reproducible: Always

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

You are on the CC list for the bug.

=

--17526631228.CAeD35F3E.1118--

pkgs: openSUSE-Aeon tik-osimage-Aeon

summary: Use `ro=3Dvfs`in fstab


--17528185562.10D59ACA.329
Date: Fri, 18 Jul 2025 06:02: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=3D1246689

            Bug ID: 1246689
           Summary: [Build 20250717] openQA test fails in usr_sbin_smbd
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/5182157/modules/usr_
                    sbin_smbd/steps/115
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

## Observation

type=3DAVC msg=3Daudit(1752817260.171:801): apparmor=3D"DENIED" operation=
=3D"open"
class=3D"file" profile=3D"samba-rpcd-classic" name=3D"/usr/etc/krb5.conf" p=
id=3D3744
comm=3D"rpcd_classic" requested_mask=3D"r" denied_mask=3D"r" fsuid=3D0 ouid=
=3D0
type=3DAVC msg=3Daudit(1752817260.476:802): apparmor=3D"DENIED" operation=
=3D"open"
class=3D"file" profile=3D"samba-rpcd-classic" name=3D"/usr/etc/krb5.conf" p=
id=3D3744
comm=3D"rpcd_classic" requested_mask=3D"r" denied_mask=3D"r" fsuid=3D0 ouid=
=3D0

The change happened in the krb5 package:
 5+- Moved /etc/krb5.conf to /usr/etc/krb5.conf
 6+  This patch (0011_usr_etc.patch) is upstream:
 7+  https://github.com/krb5/krb5/pull/1437/

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-apparmor_profile@64b=
it
fails in
[usr_sbin_smbd](https://openqa.opensuse.org/tests/5182157/modules/usr_sbin_=
smbd/steps/115)

## Test suite description
Maintained by QE Security

## Reproducible

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

## Expected result

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

## Further details

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

--17528185562.10D59ACA.329
Date: Fri, 18 Jul 2025 06:02: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
          1246689

          Summary
          [Build 20250717] openQA test fails in usr_sbin_smbd

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          URL
          https://openqa.opensuse.org/tests/5182157/modules/usr_sbin_sm=
bd/steps/115

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          AppArmor

          Assignee
          suse-beta@cboltz.de

          Reporter
          dimstar@opensuse.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

## Observation

type=3DAVC msg=3Daudit(1752817260.171:801): apparmor=3D"DENIED" o=
peration=3D"open"
class=3D"file" profile=3D"samba-rpcd-classic" name=3D&q=
uot;/usr/etc/krb5.conf" pid=3D3744
comm=3D"rpcd_classic" requested_mask=3D"r" denied_mask=
=3D"r" fsuid=3D0 ouid=3D0
type=3DAVC msg=3Daudit(1752817260.476:802): apparmor=3D"DENIED" o=
peration=3D"open"
class=3D"file" profile=3D"samba-rpcd-classic" name=3D&q=
uot;/usr/etc/krb5.conf" pid=3D3744
comm=3D"rpcd_classic" requested_mask=3D"r" denied_mask=
=3D"r" fsuid=3D0 ouid=3D0

The change happened in the krb5 package:
 5+- Moved /etc/krb5.conf to /usr/etc/krb5.conf
 6+  This patch (0011_usr_etc.patch) is upstream:
 7+  https://github.com=
/krb5/krb5/pull/1437/

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-apparmor_profile&#64=
;64bit
fails in
[usr_sbin_smbd](https://openqa.opensuse.org/tests/5182157/module=
s/usr_sbin_smbd/steps/115)

## Test suite description
Maintained by QE Security

## Reproducible

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

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/lat=
est?arch=3Dx86_64&distri=3Dopensuse&flavor=3DDVD&machine=3D64bi=
t&test=3Dapparmor_profile&version=3DTumbleweed)

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

You are on the CC list for the bug.

=

--17528185562.10D59ACA.329--


--17528281183.355a2b3E5.482
Date: Fri, 18 Jul 2025 08:41:58 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1246701
           Summary: fuse: please update to work with gettext-runtime 0.25
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: ana.guerrero-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

fuse needs a small update to work with gettext-runtime 0.25.
You have the diff below or in this bogus SR#1294325

changes files:
--------------
-


--17528437087.9CcaEF5ef.1367
Date: Fri, 18 Jul 2025 13:01: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=3D1246722

            Bug ID: 1246722
           Summary: VUL-0: CVE-2025-46569: hauler: github.com/open-policy-agent/opa: HTTP request path can be crafted to inject Rego code into a constructed query when a virtual document is requested through the Data API
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://smash.suse.de/issue/453158/
                OS: Other
            Status: NEW
        Whiteboard: CVSSv3.1:SUSE:CVE-2025-46569:8.3:(AV:N/AC:L/PR:L/UI:N/
                    S:U/C:H/I:H/A:L)
                    CVSSv4:SUSE:CVE-2025-46569:7.6:(AV:N/AC:L/AT:P/PR:L/UI
                    :N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N)
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: dmueller-at-suse.com
          Reporter: camila.matos-at-suse.com
        QA Contact: security-team-at-suse.de
            Blocks: 1246710
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Open Policy Agent (OPA) is an open source, general-purpose policy engine. P=
rior
to version 1.4.0, when run as a server, OPA exposes an HTTP Data API for
reading and writing documents. Requesting a virtual document through the Da=
ta
API entails policy evaluation, where a Rego query containing a single data
document reference is constructed from the requested path. This query is th=
en
used for policy evaluation. A HTTP request path can be crafted in a way that
injects Rego code into the constructed query. The evaluation result cannot =
be
made to return any other data than what is generated by the requested path,=
 but
this path can be misdirected, and the injected Rego code can be crafted to =
make
the query succeed or fail; opening up for oracle attacks or, given the right
circumstances, erroneous policy decision results. Furthermore, the injected
code can be crafted to be computationally expensive, resulting in a Denial =
Of
Service (DoS) attack. This issue has been patched in version 1.4.0. A
workaround involves having network access to OPA=E2=80=99s RESTful APIs bei=
ng limited
to `localhost` and/or trusted networks, unless necessary for production
reasons.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-46569
https://www.cve.org/CVERecord?id=3DCVE-2025-46569
https://github.com/open-policy-agent/opa/commit/ad2063247a14711882f18c387a5=
11fc8094aa79c
https://github.com/open-policy-agent/opa/security/advisories/GHSA-6m8w-jc87=
-6cr7
https://bugzilla.redhat.com/show_bug.cgi?id=3D2363571
https://github.com/CVEProject/cvelistV5/blob/main//cves/2025/46xxx/CVE-2025=
-46569.json
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17528437087.9CcaEF5ef.1367
Date: Fri, 18 Jul 2025 13:01: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
          1246722

          Summary
          VUL-0: CVE-2025-46569: hauler: github.com/open-policy-agent/o=
pa: HTTP request path can be crafted to inject Rego code into a constructed=
 query when a virtual document is requested through the Data API

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

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

          Severity
          Major

          Priority
          P5 - None

          Component
          Security

          Assignee
          dmueller@suse.com

          Reporter
          camila.matos@suse.com

          QA Contact
          security-team@suse.de

          Blocks
          1246710

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Open Policy Agent (OPA) is an open source, general-purpose p=
olicy engine. Prior
to version 1.4.0, when run as a server, OPA exposes an HTTP Data API for
reading and writing documents. Requesting a virtual document through the Da=
ta
API entails policy evaluation, where a Rego query containing a single data
document reference is constructed from the requested path. This query is th=
en
used for policy evaluation. A HTTP request path can be crafted in a way that
injects Rego code into the constructed query. The evaluation result cannot =
be
made to return any other data than what is generated by the requested path,=
 but
this path can be misdirected, and the injected Rego code can be crafted to =
make
the query succeed or fail; opening up for oracle attacks or, given the right
circumstances, erroneous policy decision results. Furthermore, the injected
code can be crafted to be computationally expensive, resulting in a Denial =
Of
Service (DoS) attack. This issue has been patched in version 1.4.0. A
workaround involves having network access to OPA=E2=80=99s RESTful APIs bei=
ng limited
to `localhost` and/or trusted networks, unless necessary for production
reasons.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-46569
https://www.c=
ve.org/CVERecord?id=3DCVE-2025-46569
https://github.com/open-policy-agent/opa/commit/a=
d2063247a14711882f18c387a511fc8094aa79c
https://github.com/open-policy-agent/opa/security/advisor=
ies/GHSA-6m8w-jc87-6cr7
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2363571
https://github.com/CVEProject/cvelistV5/blob/main//=
cves/2025/46xxx/CVE-2025-46569.json

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

You are on the CC list for the bug.

=

--17528437087.9CcaEF5ef.1367--


--17528580711.F56d2F.2008
Date: Fri, 18 Jul 2025 17:01:11 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1246743
           Summary: latest change in xkeyboard-config breaks abstraction/X
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: mrueckert-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

```
/usr/share/xkeyboard-config-2/** r,
```
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17528580711.F56d2F.2008
Date: Fri, 18 Jul 2025 17:01:11 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1246743

          Summary
          latest change in xkeyboard-config breaks abstraction/X

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          AppArmor

          Assignee
          suse-beta@cboltz.de

          Reporter
          mrueckert@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

```
/usr/share/xkeyboard-config-2/** r,
```

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

You are on the CC list for the bug.

=

--17528580711.F56d2F.2008--


--17530316023.f7D9.119
Date: Sun, 20 Jul 2025 17:13:22 +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=3D1246767

            Bug ID: 1246767
           Summary: Mismatch between 'go' (golang) and 'dlv' (delve) versions
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: andrew-at-sourceflow.dev
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I'm trying to debug a Go program with the `helix` editor, along with `go`,
`dlv` and `gopls`. When I try to debug, I get this error:

2025-07-20T13:01:15.940 helix_dap::transport [ERROR] [1v1] <- DAP error
Some("Failed to launch") (Some(Object {"error": Object {"format":
String("Failed to launch: Version of Delve is too old for Go version go1.25=
rc2
(maximum supported version 1.24, suppress this error with
--check-go-version=3Dfalse)"), "id": Number(3000), "showUser": Bool(true)}}=
)) for
command #1 launch

```
$ go version
go version go1.25rc2 linux/amd64
$ dlv version
Delve Debugger
Version: 1.25.0
Build: $Id: e323af07680631b9cbdcc9d02e0a37891d12d972
```

When I run the command from the command line, it continues after a warning:

```
$ dlv --check-go-version=3Dfalse debug hello.go
WARNING: undefined behavior - version of Delve is too old for Go version
go1.25rc2 (maximum supported version 1.24)
Type 'help' for list of commands.
(dlv)=20
```

In Helix, editing a custom `~/.config/helix/languages.toml` file doesn't
resolve the issue (I get the same error message in Helix):

```
[language.debugger]
name =3D "go"
transport =3D "tcp"
command =3D "dlv"
args =3D ["dap", "--check-go-version=3Dfalse"] ### Changed here
port-arg =3D "-l 127.0.0.1:{}"

[[language.debugger.templates]]
name =3D "source"
request =3D "launch"
completion =3D [ { name =3D "entrypoint", completion =3D "filename", defaul=
t =3D "." }
]
args =3D { mode =3D "debug", program =3D "{0}" }
```

For comparison, see the upstream Helix configuration:

https://github.com/helix-editor/helix/blob/e7f95ca6b2e685b7cd2191c478ec9176=
0988241f/languages.toml#L746

Is there some way to fix or work around this issue, and/or to prevent it fr=
om
happening again in the future?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17530316023.f7D9.119
Date: Sun, 20 Jul 2025 17:13:22 +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
          1246767

          Summary
          Mismatch between 'go' (golang) and 'dlv' (delve) versions

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Development

          Assignee
          screening-team-bugs@suse.de

          Reporter
          andrew@sourceflow.dev

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I'm trying to debug a Go program with the `helix` editor, al=
ong with `go`,
`dlv` and `gopls`. When I try to debug, I get this error:

2025-07-20T13:01:15.940 helix_dap::transport [ERROR] [1v1] <- DAP error
Some("Failed to launch") (Some(Object {"error": Object =
{"format":
String("Failed to launch: Version of Delve is too old for Go version g=
o1.25rc2
(maximum supported version 1.24, suppress this error with
--check-go-version=3Dfalse)"), "id": Number(3000), "sho=
wUser": Bool(true)}})) for
command #1 launch

```
$ go version
go version go1.25rc2 linux/amd64
$ dlv version
Delve Debugger
Version: 1.25.0
Build: $Id: e323af07680631b9cbdcc9d02e0a37891d12d972
```

When I run the command from the command line, it continues after a warning:

```
$ dlv --check-go-version=3Dfalse debug hello.go
WARNING: undefined behavior - version of Delve is too old for Go version
go1.25rc2 (maximum supported version 1.24)
Type 'help' for list of commands.
(dlv)=20
```

In Helix, editing a custom `~/.config/helix/languages.toml` file doesn't
resolve the issue (I get the same error message in Helix):

```
[language.debugger]
name =3D "go"
transport =3D "tcp"
command =3D "dlv"
args =3D ["dap", "--check-go-version=3Dfalse"] ### Chan=
ged here
port-arg =3D "-l 127.0.0.1:{}"

[[language.debugger.templates]]
name =3D "source"
request =3D "launch"
completion =3D [ { name =3D "entrypoint", completion =3D "fi=
lename", default =3D "." }
]
args =3D { mode =3D "debug", program =3D "{0}" }
```

For comparison, see the upstream Helix configuration:

https://github.com/helix-editor/he=
lix/blob/e7f95ca6b2e685b7cd2191c478ec91760988241f/languages.toml#L746

Is there some way to fix or work around this issue, and/or to prevent it fr=
om
happening again in the future?

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

You are on the CC list for the bug.

=

--17530316023.f7D9.119--


--17530324384.75EE.122
Date: Sun, 20 Jul 2025 17:27:18 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1246768
           Summary: %pretrans in xkeyboard-config causes never ending loop
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: sndirsch-at-suse.com
          Reporter: mcepl-at-suse.com
        QA Contact: gfx-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Upgrading xkeyboard-config-2.45-1.1.noarch leads to freezing zypper. The
process `rpm --root / --dbpath /usr/lib/sysimage/rpm --define _dump_posttra=
ns 1
-U --percent --noglob --force --nodeps --
/var/cache/zypp/packages/repo-oss/noarch/xkeyboard-config` is running at 10=
0%
CPU and never ends.

strace on that rpm shows never ending list of these systems calls

rename("/usr/share/X11/xkb.rpmmoved", "/usr/share/X11/xkb.rpmmoved.10626161=
") =3D
-1 ENOENT (No such file or directory)

and quick look at
https://build.opensuse.org/projects/X11:XOrg/packages/xkeyboard-config/file=
s/xkeyboard-config.spec?expand=3D1
shows that %pretrans script is completely not protected against going into
never ending loop.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17530324384.75EE.122
Date: Sun, 20 Jul 2025 17:27:18 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1246768

          Summary
          %pretrans in xkeyboard-config causes never ending loop

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X.Org

          Assignee
          sndirsch@suse.com

          Reporter
          mcepl@suse.com

          QA Contact
          gfx-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Upgrading xkeyboard-config-2.45-1.1.noarch leads to freezing=
 zypper. The
process `rpm --root / --dbpath /usr/lib/sysimage/rpm --define _dump_posttra=
ns 1
-U --percent --noglob --force --nodeps --
/var/cache/zypp/packages/repo-oss/noarch/xkeyboard-config` is running at 10=
0%
CPU and never ends.

strace on that rpm shows never ending list of these systems calls

rename("/usr/share/X11/xkb.rpmmoved", "/usr/share/X11/xkb.rp=
mmoved.10626161") =3D
-1 ENOENT (No such file or directory)

and quick look at
https://build.opensuse.org/p=
rojects/X11:XOrg/packages/xkeyboard-config/files/xkeyboard-config.spec?expa=
nd=3D1
shows that %pretrans script is completely not protected against going into
never ending loop.

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

You are on the CC list for the bug.

=

--17530324384.75EE.122--