--17496327810.5eD4f.998
Date: Wed, 11 Jun 2025 09:06:21 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1244445
           Summary: Kernel master branch build is broken on ppc64le (drivers/gpu/drm/sitronix/st7571-i2c.ko)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: pedro.falcato-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Ever since

commit 4b35f0f41ee295059c46a6f4ae97e4b5b8f10d9e
Author: Marcus Folkesson <marcus.folkesson-at-gmail.com>
Date:   Wed Apr 23 21:03:21 2025 +0200

    drm/st7571-i2c: add support for Sitronix ST7571 LCD controller

that the master branch build for ppc64le is broken with errors similar to:

ERROR: modpost: "of_get_display_timing"
[drivers/gpu/drm/sitronix/st7571-i2c.ko] undefined!
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17496327810.5eD4f.998
Date: Wed, 11 Jun 2025 09:06:21 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244445

          Summary
          Kernel master branch build is broken on ppc64le (drivers/gpu/=
drm/sitronix/st7571-i2c.ko)

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          pedro.falcato@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Ever since

commit 4b35f0f41ee295059c46a6f4ae97e4b5b8f10d9e
Author: Marcus Folkesson <marcus.folkesson@gmail.com>
Date:   Wed Apr 23 21:03:21 2025 +0200

    drm/st7571-i2c: add support for Sitronix ST7571 LCD controller

that the master branch build for ppc64le is broken with errors similar to:

ERROR: modpost: "of_get_display_timing"
[drivers/gpu/drm/sitronix/st7571-i2c.ko] undefined!

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

You are on the CC list for the bug.

=

--17496327810.5eD4f.998--


body:
--17496370823.519cD2DB3.2081
Date: Wed, 11 Jun 2025 10:18:02 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1244452
           Summary: chromium 137.0.7151.103 release
    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: ro-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

[420150619] High CVE-2025-5958: Use after free in Media. Reported by Huang
Xilin of Ant Group Light-Year Security Lab on 2025-05-25

[422313191] High CVE-2025-5959: Type Confusion in V8. Reported by Seunghyun=
 Lee
as part of TyphoonPWN 2025 on 2025-06-04
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17496370823.519cD2DB3.2081
Date: Wed, 11 Jun 2025 10:18:02 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244452

          Summary
          chromium 137.0.7151.103 release

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

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

[420150619] High CVE-2025-5958: Use after free in Media. Rep=
orted by Huang
Xilin of Ant Group Light-Year Security Lab on 2025-05-25

[422313191] High CVE-2025-5959: Type Confusion in V8. Reported by Seunghyun=
 Lee
as part of TyphoonPWN 2025 on 2025-06-04

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

You are on the CC list for the bug.

=

--17496370823.519cD2DB3.2081--

summary: chromium 137.0.7151.103 release


--17496473622.2fA5fd6f.2444
Date: Wed, 11 Jun 2025 13:09: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=3D1244458

            Bug ID: 1244458
           Summary: conflict detected by zypper precheck in kernel-firmware-nvidia
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: tiwai-at-suse.com
          Reporter: mrueckert-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Problem occurred during or after installation or removal of packages:
Executing the transaction failed because of the following problems:
    file /usr/lib/firmware/nvidia/ad103 from install of
kernel-firmware-nvidia-20250516-2.1.noarch conflicts with file from package
kernel-firmware-nvidia-20250206-4.1.noarch
    file /usr/lib/firmware/nvidia/ad104 from install of
kernel-firmware-nvidia-20250516-2.1.noarch conflicts with file from package
kernel-firmware-nvidia-20250206-4.1.noarch
    file /usr/lib/firmware/nvidia/ad106 from install of
kernel-firmware-nvidia-20250516-2.1.noarch conflicts with file from package
kernel-firmware-nvidia-20250206-4.1.noarch
    file /usr/lib/firmware/nvidia/ad107 from install of
kernel-firmware-nvidia-20250516-2.1.noarch conflicts with file from package
kernel-firmware-nvidia-20250206-4.1.noarch
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17496473622.2fA5fd6f.2444
Date: Wed, 11 Jun 2025 13:09: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
          1244458

          Summary
          conflict detected by zypper precheck in kernel-firmware-nvidia

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          tiwai@suse.com

          Reporter
          mrueckert@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Problem occurred during or after installation or removal of =
packages:
Executing the transaction failed because of the following problems:
    file /usr/lib/firmware/nvidia/ad103 from install of
kernel-firmware-nvidia-20250516-2.1.noarch conflicts with file from package
kernel-firmware-nvidia-20250206-4.1.noarch
    file /usr/lib/firmware/nvidia/ad104 from install of
kernel-firmware-nvidia-20250516-2.1.noarch conflicts with file from package
kernel-firmware-nvidia-20250206-4.1.noarch
    file /usr/lib/firmware/nvidia/ad106 from install of
kernel-firmware-nvidia-20250516-2.1.noarch conflicts with file from package
kernel-firmware-nvidia-20250206-4.1.noarch
    file /usr/lib/firmware/nvidia/ad107 from install of
kernel-firmware-nvidia-20250516-2.1.noarch conflicts with file from package
kernel-firmware-nvidia-20250206-4.1.noarch

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

You are on the CC list for the bug.

=

--17496473622.2fA5fd6f.2444--


body:
--17496860463.046a.35
Date: Wed, 11 Jun 2025 23:54:06 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

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

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

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

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

--17496860463.046a.35
Date: Wed, 11 Jun 2025 23:54:06 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244485

          Summary
          go1.25 release tracking

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Development

          Assignee
          screening-team-bugs@suse.de

          Reporter
          jkowalczyk@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

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

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

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

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

You are on the CC list for the bug.

=

--17496860463.046a.35--

summary: go1.25 release tracking


--17497074562.5226.764
Date: Thu, 12 Jun 2025 05:50:56 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1244496
           Summary: Fingerprint sensor does not work for unlocking screen
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: aaron.w2-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I registered my finger with the fingerprint sensor on my Framework laptop, =
and
it also appears to be fully supported by fprintd. However, nothing happens =
when
I press it when asked (or to enter my password) to unlock the screen. I use=
 the
KDE environment, but this may be SDDM, hence filing under X11 applications.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17497074562.5226.764
Date: Thu, 12 Jun 2025 05:50:56 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244496

          Summary
          Fingerprint sensor does not work for unlocking screen

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X11 Applications

          Assignee
          screening-team-bugs@suse.de

          Reporter
          aaron.w2@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I registered my finger with the fingerprint sensor on my Fra=
mework laptop, and
it also appears to be fully supported by fprintd. However, nothing happens =
when
I press it when asked (or to enter my password) to unlock the screen. I use=
 the
KDE environment, but this may be SDDM, hence filing under X11 applications.=

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

You are on the CC list for the bug.

=

--17497074562.5226.764--


--17497686272.EcdFE90C.3610
Date: Thu, 12 Jun 2025 22:50:27 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1244538
           Summary: kernel: NULL pointer dereference in elv_iosched_show
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: rbranco-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Haven't yet found a minimal reproducer for this, but it consistently fails =
in
openQA now. It was found by the podman testsuite using crun instead of runc=
 as
the OCI runtime.

Failed jobs:
- https://openqa.opensuse.org/tests/5101737/file/serial0.txt
- https://openqa.opensuse.org/tests/5101406/file/serial0.txt

It passed a day before.  Haven't checked the diff in packages:
https://openqa.opensuse.org/tests/5098618

The list of commands to reproduce:
https://openqa.opensuse.org/tests/5098618/file/podman-commands.txt

The podman tests in question:
https://github.com/containers/podman/tree/v5.5.1/test/system

There are 4 podman scenarios run: rootless local, rootless remote, local ro=
ot &
local remote.  The test fails in the last one.  I cloned a job running only=
 the
last scenario but didn't fail, so it may depend on what happened before.

The last test seems to be 180-blkio.bats because the last line in the serial
terminal has "[170]":
https://openqa.opensuse.org/tests/5101737/file/serial_terminal.txt

The failure:

> [ 5870.346564][T530427] loop0: detected capacity change from 0 to 2
> [ 5870.367331][T517059] BUG: kernel NULL pointer dereference, address: 00=
00000000000000
> [ 5870.368423][T517059] #PF: supervisor read access in kernel mode
> [ 5870.369213][T517059] #PF: error_code(0x0000) - not-present page
> [ 5870.369960][T517059] PGD 0 P4D 0=20
> [ 5870.370434][T517059] Oops: Oops: 0000 [#1] SMP NOPTI
> [ 5870.371046][T517059] CPU: 1 UID: 0 PID: 517059 Comm: (udev-worker) Not=
 tainted 6.15.1-1-default #1 PREEMPT(voluntary) openSUSE Tumbleweed  04140c=
ca2f852e1fd4a6394bdffd054f1ab41973
> [ 5870.372778][T517059] Hardware name: QEMU Standard PC (i440FX + PIIX, 1=
996), BIOS rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014
> [ 5870.374203][T517059] RIP: 0010:elv_iosched_show+0x48/0x120
> [ 5870.374896][T517059] Code: 00 4c 8b 73 08 4c 89 ef e8 e5 06 77 00 4c 8=
b 63 08 4d 85 e4 0f 84 b9 00 00 00 b9 20 00 00 00 c7 45 00 6e 6f 6e 65 66 8=
9 4d 04 <4d> 8b 26 41 be 05 00 00 00 48 c7 c7 e0 f9 c7 99 e8 d3 64 77 00 48
> [ 5870.376963][T517059] RSP: 0018:ffffd02b8803bba8 EFLAGS: 00010286
> [ 5870.377707][T517059] RAX: 0000000000000000 RBX: ffff8cdd10acea48 RCX: =
0000000000000020
> [ 5870.378603][T517059] RDX: 0000000000000000 RSI: 0000000000000246 RDI: =
ffffd02b8803bb30
> [ 5870.379496][T517059] RBP: ffff8cdd08fdb000 R08: 00000000000013c6 R09: =
00000000000754f2
> [ 5870.380390][T517059] R10: 00000000000081b4 R11: ffff8cdd038bfa00 R12: =
ffff8cdc3340cc00
> [ 5870.381285][T517059] R13: ffff8cdd10aced08 R14: 0000000000000000 R15: =
0000000000000001
> [ 5870.382192][T517059] FS:  00007f5c9f714940(0000) GS:ffff8cdda22b0000(0=
000) knlGS:0000000000000000
> [ 5870.383174][T517059] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 5870.383956][T517059] CR2: 0000000000000000 CR3: 000000006b076002 CR4: =
0000000000770ef0
> [ 5870.384858][T517059] PKRU: 55555554
> [ 5870.385383][T517059] Call Trace:
> [ 5870.385918][T517059]  <TASK>
> [ 5870.386394][T517059]  sysfs_kf_seq_show+0xd2/0x120
> [ 5870.387051][T517059]  seq_read_iter+0x111/0x470
> [ 5870.387680][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.388395][T517059]  vfs_read+0x266/0x340
> [ 5870.388987][T517059]  ksys_read+0x63/0xe0
> [ 5870.389570][T517059]  do_syscall_64+0x82/0x830
> [ 5870.390206][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.390906][T517059]  ? syscall_exit_to_user_mode+0x37/0x1d0
> [ 5870.391623][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.392326][T517059]  ? do_syscall_64+0x8e/0x830
> [ 5870.392948][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.393657][T517059]  ? __memcg_slab_free_hook+0xf7/0x140
> [ 5870.394352][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.395054][T517059]  ? __memcg_slab_free_hook+0xf7/0x140
> [ 5870.395745][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.396449][T517059]  ? kmem_cache_free+0x3ee/0x450
> [ 5870.397107][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.397824][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.398528][T517059]  ? syscall_exit_to_user_mode+0x37/0x1d0
> [ 5870.399242][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.399941][T517059]  ? do_syscall_64+0x8e/0x830
> [ 5870.400562][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.401258][T517059]  ? do_syscall_64+0x8e/0x830
> [ 5870.401882][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.402574][T517059]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
> [ 5870.403298][T517059] RIP: 0033:0x7f5c9f895837
> [ 5870.403904][T517059] Code: 20 49 89 d0 48 89 fa 4c 89 df e8 e2 c3 00 0=
0 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 16 5b c3 0f 1f 40 00 48 8b 44 24 1=
0 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 e2 e8 11 ff ff ff
> [ 5870.406006][T517059] RSP: 002b:00007ffe3b8d9780 EFLAGS: 00000202 ORIG_=
RAX: 0000000000000000
> [ 5870.406941][T517059] RAX: ffffffffffffffda RBX: 00007f5c9f714940 RCX: =
00007f5c9f895837
> [ 5870.407833][T517059] RDX: 0000000000001008 RSI: 0000564a9bb609b0 RDI: =
0000000000000015
> [ 5870.408721][T517059] RBP: 0000000000001008 R08: 0000000000000000 R09: =
0000000000000000
> [ 5870.409621][T517059] R10: 0000000000000000 R11: 0000000000000202 R12: =
0000000000000015
> [ 5870.410506][T517059] R13: 0000000000001008 R14: ffffffffffffffff R15: =
0000000000000002
> [ 5870.411391][T517059]  </TASK>
> [ 5870.411845][T517059] Modules linked in: xfs udp_diag nft_nat nft_masq =
veth tun tcp_diag inet_diag null_blk ip6_tables overlay af_packet rfkill nf=
t_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4=
 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defr=
ag_ipv6 nf_defrag_ipv4 snd_hda_codec_generic intel_rapl_msr intel_rapl_comm=
on kvm_amd snd_hda_intel ccp snd_intel_dspcfg ppdev snd_intel_sdw_acpi snd_=
hda_codec snd_hda_core snd_hwdep snd_pcm virtio_net snd_timer kvm net_failo=
ver snd irqbypass i2c_piix4 failover pcspkr i2c_smbus soundcore parport_pc =
tiny_power_button parport button joydev br_netfilter bridge stp llc nf_tabl=
es nfnetlink fuse loop efi_pstore dm_mod configfs ip_tables x_tables hid_ge=
neric usbhid ata_generic ata_piix ahci sr_mod libahci xhci_pci polyval_clmu=
lni polyval_generic cdrom ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha=
1_ssse3 libata virtio_scsi sd_mod xhci_hcd scsi_dh_emc scsi_dh_rdac aesni_i=
ntel crypto_simd scsi_dh_alua cryptd sg virtio_blk floppy usbcore
> [ 5870.411957][T517059]  scsi_mod bochs scsi_common serio_raw btrfs blake=
2b_generic xor raid6_pq dmi_sysfs qemu_fw_cfg virtio_rng
> [ 5870.422810][T517059] CR2: 0000000000000000
> [ 5870.423392][T517059] ---[ end trace 0000000000000000 ]---
> [ 5870.424098][T517059] RIP: 0010:elv_iosched_show+0x48/0x120
> [ 5870.424810][T517059] Code: 00 4c 8b 73 08 4c 89 ef e8 e5 06 77 00 4c 8=
b 63 08 4d 85 e4 0f 84 b9 00 00 00 b9 20 00 00 00 c7 45 00 6e 6f 6e 65 66 8=
9 4d 04 <4d> 8b 26 41 be 05 00 00 00 48 c7 c7 e0 f9 c7 99 e8 d3 64 77 00 48
> [ 5870.426966][T517059] RSP: 0018:ffffd02b8803bba8 EFLAGS: 00010286
> [ 5870.427741][T517059] RAX: 0000000000000000 RBX: ffff8cdd10acea48 RCX: =
0000000000000020
> [ 5870.428684][T517059] RDX: 0000000000000000 RSI: 0000000000000246 RDI: =
ffffd02b8803bb30
> [ 5870.429630][T517059] RBP: ffff8cdd08fdb000 R08: 00000000000013c6 R09: =
00000000000754f2
> [ 5870.430569][T517059] R10: 00000000000081b4 R11: ffff8cdd038bfa00 R12: =
ffff8cdc3340cc00
> [ 5870.431511][T517059] R13: ffff8cdd10aced08 R14: 0000000000000000 R15: =
0000000000000001
> [ 5870.432455][T517059] FS:  00007f5c9f714940(0000) GS:ffff8cdda22b0000(0=
000) knlGS:0000000000000000
> [ 5870.433483][T517059] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 5870.434323][T517059] CR2: 0000000000000000 CR3: 000000006b076002 CR4: =
0000000000770ef0
> [ 5870.435273][T517059] PKRU: 55555554
> [ 5870.435850][T517059] note: (udev-worker)[517059] exited with irqs disa=
bled
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17497686272.EcdFE90C.3610
Date: Thu, 12 Jun 2025 22:50:27 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244538

          Summary
          kernel: NULL pointer dereference in elv_iosched_show

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          rbranco@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Haven't yet found a minimal reproducer for this, but it cons=
istently fails in
openQA now. It was found by the podman testsuite using crun instead of runc=
 as
the OCI runtime.

Failed jobs:
- ht=
tps://openqa.opensuse.org/tests/5101737/file/serial0.txt
- ht=
tps://openqa.opensuse.org/tests/5101406/file/serial0.txt

It passed a day before.  Haven't checked the diff in packages:
https://openqa.opensu=
se.org/tests/5098618

The list of commands to reproduce:
https://openqa.opensuse.org/tests/5098618/file/podman-commands.txt

The podman tests in question:
ht=
tps://github.com/containers/podman/tree/v5.5.1/test/system

There are 4 podman scenarios run: rootless local, rootless remote, local ro=
ot &
local remote.  The test fails in the last one.  I cloned a job running only=
 the
last scenario but didn't fail, so it may depend on what happened before.

The last test seems to be 180-blkio.bats because the last line in the serial
terminal has "[170]":
https://openqa.opensuse.org/tests/5101737/file/serial_terminal.txt

The failure:

> [ 5870.346564][T530427] loop0: detected capacity=
 change from 0 to 2
> [ 5870.367331][T517059] BUG: kernel NULL pointer dereference, address:=
 0000000000000000
> [ 5870.368423][T517059] #PF: supervisor read access in kernel mode
> [ 5870.369213][T517059] #PF: error_code(0x0000) - not-present page
> [ 5870.369960][T517059] PGD 0 P4D 0=20
> [ 5870.370434][T517059] Oops: Oops: 0000 [#1] SMP NOPTI
> [ 5870.371046][T517059] CPU: 1 UID: 0 PID: 517059 Comm: (udev-worker) =
Not tainted 6.15.1-1-default #1 PREEMPT(voluntary) openSUSE Tumbleweed  041=
40cca2f852e1fd4a6394bdffd054f1ab41973
> [ 5870.372778][T517059] Hardware name: QEMU Standard PC (i440FX + PIIX=
, 1996), BIOS rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014
> [ 5870.374203][T517059] RIP: 0010:elv_iosched_show+0x48/0x120
> [ 5870.374896][T517059] Code: 00 4c 8b 73 08 4c 89 ef e8 e5 06 77 00 4=
c 8b 63 08 4d 85 e4 0f 84 b9 00 00 00 b9 20 00 00 00 c7 45 00 6e 6f 6e 65 6=
6 89 4d 04 <4d> 8b 26 41 be 05 00 00 00 48 c7 c7 e0 f9 c7 99 e8 d3 64=
 77 00 48
> [ 5870.376963][T517059] RSP: 0018:ffffd02b8803bba8 EFLAGS: 00010286
> [ 5870.377707][T517059] RAX: 0000000000000000 RBX: ffff8cdd10acea48 RC=
X: 0000000000000020
> [ 5870.378603][T517059] RDX: 0000000000000000 RSI: 0000000000000246 RD=
I: ffffd02b8803bb30
> [ 5870.379496][T517059] RBP: ffff8cdd08fdb000 R08: 00000000000013c6 R0=
9: 00000000000754f2
> [ 5870.380390][T517059] R10: 00000000000081b4 R11: ffff8cdd038bfa00 R1=
2: ffff8cdc3340cc00
> [ 5870.381285][T517059] R13: ffff8cdd10aced08 R14: 0000000000000000 R1=
5: 0000000000000001
> [ 5870.382192][T517059] FS:  00007f5c9f714940(0000) GS:ffff8cdda22b000=
0(0000) knlGS:0000000000000000
> [ 5870.383174][T517059] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050=
033
> [ 5870.383956][T517059] CR2: 0000000000000000 CR3: 000000006b076002 CR=
4: 0000000000770ef0
> [ 5870.384858][T517059] PKRU: 55555554
> [ 5870.385383][T517059] Call Trace:
> [ 5870.385918][T517059]  <TASK>
> [ 5870.386394][T517059]  sysfs_kf_seq_show+0xd2/0x120
> [ 5870.387051][T517059]  seq_read_iter+0x111/0x470
> [ 5870.387680][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.388395][T517059]  vfs_read+0x266/0x340
> [ 5870.388987][T517059]  ksys_read+0x63/0xe0
> [ 5870.389570][T517059]  do_syscall_64+0x82/0x830
> [ 5870.390206][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.390906][T517059]  ? syscall_exit_to_user_mode+0x37/0x1d0
> [ 5870.391623][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.392326][T517059]  ? do_syscall_64+0x8e/0x830
> [ 5870.392948][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.393657][T517059]  ? __memcg_slab_free_hook+0xf7/0x140
> [ 5870.394352][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.395054][T517059]  ? __memcg_slab_free_hook+0xf7/0x140
> [ 5870.395745][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.396449][T517059]  ? kmem_cache_free+0x3ee/0x450
> [ 5870.397107][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.397824][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.398528][T517059]  ? syscall_exit_to_user_mode+0x37/0x1d0
> [ 5870.399242][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.399941][T517059]  ? do_syscall_64+0x8e/0x830
> [ 5870.400562][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.401258][T517059]  ? do_syscall_64+0x8e/0x830
> [ 5870.401882][T517059]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 5870.402574][T517059]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
> [ 5870.403298][T517059] RIP: 0033:0x7f5c9f895837
> [ 5870.403904][T517059] Code: 20 49 89 d0 48 89 fa 4c 89 df e8 e2 c3 0=
0 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 16 5b c3 0f 1f 40 00 48 8b 44 2=
4 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 e2 e8 11=
 ff ff ff
> [ 5870.406006][T517059] RSP: 002b:00007ffe3b8d9780 EFLAGS: 00000202 OR=
IG_RAX: 0000000000000000
> [ 5870.406941][T517059] RAX: ffffffffffffffda RBX: 00007f5c9f714940 RC=
X: 00007f5c9f895837
> [ 5870.407833][T517059] RDX: 0000000000001008 RSI: 0000564a9bb609b0 RD=
I: 0000000000000015
> [ 5870.408721][T517059] RBP: 0000000000001008 R08: 0000000000000000 R0=
9: 0000000000000000
> [ 5870.409621][T517059] R10: 0000000000000000 R11: 0000000000000202 R1=
2: 0000000000000015
> [ 5870.410506][T517059] R13: 0000000000001008 R14: ffffffffffffffff R1=
5: 0000000000000002
> [ 5870.411391][T517059]  </TASK>
> [ 5870.411845][T517059] Modules linked in: xfs udp_diag nft_nat nft_ma=
sq veth tun tcp_diag inet_diag null_blk ip6_tables overlay af_packet rfkill=
 nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_i=
pv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_d=
efrag_ipv6 nf_defrag_ipv4 snd_hda_codec_generic intel_rapl_msr intel_rapl_c=
ommon kvm_amd snd_hda_intel ccp snd_intel_dspcfg ppdev snd_intel_sdw_acpi s=
nd_hda_codec snd_hda_core snd_hwdep snd_pcm virtio_net snd_timer kvm net_fa=
ilover snd irqbypass i2c_piix4 failover pcspkr i2c_smbus soundcore parport_=
pc tiny_power_button parport button joydev br_netfilter bridge stp llc nf_t=
ables nfnetlink fuse loop efi_pstore dm_mod configfs ip_tables x_tables hid=
_generic usbhid ata_generic ata_piix ahci sr_mod libahci xhci_pci polyval_c=
lmulni polyval_generic cdrom ghash_clmulni_intel sha512_ssse3 sha256_ssse3 =
sha1_ssse3 libata virtio_scsi sd_mod xhci_hcd scsi_dh_emc scsi_dh_rdac aesn=
i_intel crypto_simd scsi_dh_alua cryptd sg virtio_blk floppy usbcore
> [ 5870.411957][T517059]  scsi_mod bochs scsi_common serio_raw btrfs bl=
ake2b_generic xor raid6_pq dmi_sysfs qemu_fw_cfg virtio_rng
> [ 5870.422810][T517059] CR2: 0000000000000000
> [ 5870.423392][T517059] ---[ end trace 0000000000000000 ]---
> [ 5870.424098][T517059] RIP: 0010:elv_iosched_show+0x48/0x120
> [ 5870.424810][T517059] Code: 00 4c 8b 73 08 4c 89 ef e8 e5 06 77 00 4=
c 8b 63 08 4d 85 e4 0f 84 b9 00 00 00 b9 20 00 00 00 c7 45 00 6e 6f 6e 65 6=
6 89 4d 04 <4d> 8b 26 41 be 05 00 00 00 48 c7 c7 e0 f9 c7 99 e8 d3 64=
 77 00 48
> [ 5870.426966][T517059] RSP: 0018:ffffd02b8803bba8 EFLAGS: 00010286
> [ 5870.427741][T517059] RAX: 0000000000000000 RBX: ffff8cdd10acea48 RC=
X: 0000000000000020
> [ 5870.428684][T517059] RDX: 0000000000000000 RSI: 0000000000000246 RD=
I: ffffd02b8803bb30
> [ 5870.429630][T517059] RBP: ffff8cdd08fdb000 R08: 00000000000013c6 R0=
9: 00000000000754f2
> [ 5870.430569][T517059] R10: 00000000000081b4 R11: ffff8cdd038bfa00 R1=
2: ffff8cdc3340cc00
> [ 5870.431511][T517059] R13: ffff8cdd10aced08 R14: 0000000000000000 R1=
5: 0000000000000001
> [ 5870.432455][T517059] FS:  00007f5c9f714940(0000) GS:ffff8cdda22b000=
0(0000) knlGS:0000000000000000
> [ 5870.433483][T517059] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050=
033
> [ 5870.434323][T517059] CR2: 0000000000000000 CR3: 000000006b076002 CR=
4: 0000000000770ef0
> [ 5870.435273][T517059] PKRU: 55555554
> [ 5870.435850][T517059] note: (udev-worker)[517059] exited with irqs d=
isabled

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

You are on the CC list for the bug.

=

--17497686272.EcdFE90C.3610--


--17498161340.baEcbd.8681
Date: Fri, 13 Jun 2025 12:02:14 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1244562
           Summary: libcrypto.so in aws-lc is not versioned and in the wrong subpackage
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: rrahl0-at-opensuse.org
          Reporter: mrueckert-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: georg.pfuetzenreuter-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

rpm -e --test aws-lc-devel
error: Failed dependencies:
        libcrypto.so()(64bit) is needed by (installed)
libssl1_51_2-1.52.1-1.1.x86_64
        libcrypto.so()(64bit) is needed by (installed)
haproxy-3.2.0+git0.e134140d2-11.2.x86_64
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17498161340.baEcbd.8681
Date: Fri, 13 Jun 2025 12:02:14 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244562

          Summary
          libcrypto.so in aws-lc is not versioned and in the wrong subp=
ackage

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          rrahl0@opensuse.org

          Reporter
          mrueckert@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          georg.pfuetzenreuter@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

rpm -e --test aws-lc-devel
error: Failed dependencies:
        libcrypto.so()(64bit) is needed by (installed)
libssl1_51_2-1.52.1-1.1.x86_64
        libcrypto.so()(64bit) is needed by (installed)
haproxy-3.2.0+git0.e134140d2-11.2.x86_64

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

You are on the CC list for the bug.

=

--17498161340.baEcbd.8681--


--17498199312.6dBD37BA4.8882
Date: Fri, 13 Jun 2025 13:05:31 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1244573
           Summary: [SELinux] dbus-broker triggers error while interacting with gnome-remote-desktop with selinux=3Dpermissive
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: nf.contact-at-ipoac.ch
        QA Contact: security-team-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Operating System: openSUSE Tumbleweed-Slowroll
SELinux status, mode and policy name:=20
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   permissive
Mode from config file:          permissive
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Memory protection checking:     actual (secure)
Max kernel policy version:      34

SELinux policy version and repository: 20250528-1.1 from Slowroll repo-oss

The software (incl. version) that is affected by the SELinux issue and the
error message:=20
dbus-broker-36-2.3 (seems while interacting with gnome-remote-desktop-48.1-=
1.1
and snapper-0.12.2-2.2)
tpm2.0-tools-5.7-2.3

SELinux Audit log:
time->Fri Jun 13 13:10:41 2025
type=3DUSER_AVC msg=3Daudit(1749813041.073:50): pid=3D1945 uid=3D498 auid=
=3D4294967295
ses=3D4294967295 subj=3Dsystem_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg=
=3D'avc:=20
denied  { send_msg } for  scontext=3Dsystem_u:system_r:gnome_remote_desktop=
_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Ddbus permissive=3D1
exe=3D"/usr/bin/dbus-broker" sauid=3D498 hostname=3D? addr=3D? terminal=3D?'
----
time->Fri Jun 13 13:15:06 2025
type=3DUSER_AVC msg=3Daudit(1749813306.534:328): pid=3D1945 uid=3D498 auid=
=3D4294967295
ses=3D4294967295 subj=3Dsystem_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg=
=3D'avc:=20
denied  { send_msg } for  scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Ddbus permissive=3D1
exe=3D"/usr/bin/dbus-broker" sauid=3D498 hostname=3D? addr=3D? terminal=3D?'
----
time->Fri Jun 13 13:15:06 2025
type=3DAVC msg=3Daudit(1749813306.534:329): avc:  denied  { getopt } for  p=
id=3D6657
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:15:06 2025
type=3DAVC msg=3Daudit(1749813306.534:330): avc:  denied  { getattr } for  =
pid=3D6657
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:15:06 2025
type=3DAVC msg=3Daudit(1749813306.534:331): avc:  denied  { setopt } for  p=
id=3D6657
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:15:27 2025
type=3DAVC msg=3Daudit(1749813327.193:339): avc:  denied  { getopt } for  p=
id=3D7320
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:15:27 2025
type=3DAVC msg=3Daudit(1749813327.193:340): avc:  denied  { getattr } for  =
pid=3D7320
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:15:27 2025
type=3DAVC msg=3Daudit(1749813327.193:341): avc:  denied  { setopt } for  p=
id=3D7320
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:20:17 2025
type=3DAVC msg=3Daudit(1749813617.732:349): avc:  denied  { getopt } for  p=
id=3D12014
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:20:17 2025
type=3DAVC msg=3Daudit(1749813617.732:350): avc:  denied  { getattr } for=20
pid=3D12014 comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:20:17 2025
type=3DAVC msg=3Daudit(1749813617.732:351): avc:  denied  { setopt } for  p=
id=3D12014
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:20:50 2025
type=3DAVC msg=3Daudit(1749813650.320:359): avc:  denied  { getopt } for  p=
id=3D13018
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:20:50 2025
type=3DAVC msg=3Daudit(1749813650.320:360): avc:  denied  { getattr } for=20
pid=3D13018 comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:20:50 2025
type=3DAVC msg=3Daudit(1749813650.320:361): avc:  denied  { setopt } for  p=
id=3D13018
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:21:12 2025
type=3DAVC msg=3Daudit(1749813672.121:363): avc:  denied  { getopt } for  p=
id=3D13665
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:21:12 2025
type=3DAVC msg=3Daudit(1749813672.121:364): avc:  denied  { getattr } for=20
pid=3D13665 comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:21:12 2025
type=3DAVC msg=3Daudit(1749813672.121:365): avc:  denied  { setopt } for  p=
id=3D13665
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1

Any other important details:
The SELinux audit log entries relating to gnome-remote-desktop appear as so=
on
as I reach the graphical desktop
the error relating to tpm2_getcap appear when enrolling tpm2 for FDE, like =
on
zypper updates or sdbootutil enroll --method=3Dtpm2
I followed the guidance on https://en.opensuse.org/Portal:SELinux/Setup whi=
ch
mentioned opening a bug report for errors appearing in ausearch
The system uses systemd-boot with full-disk encryption using the tpm for
unlocking on boot which seems to be handled in issue 1241964
<https://bugzilla.opensuse.org/show_bug.cgi?id=3D1241964>
I could not find any similar issues related to gnome-remote-desktop
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17498199312.6dBD37BA4.8882
Date: Fri, 13 Jun 2025 13:05:31 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244573

          Summary
          [SELinux] dbus-broker triggers error while interacting with g=
nome-remote-desktop with selinux=3Dpermissive

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          nf.contact@ipoac.ch

          QA Contact
          security-team@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Operating System: openSUSE Tumbleweed-Slowroll
SELinux status, mode and policy name:=20
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   permissive
Mode from config file:          permissive
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Memory protection checking:     actual (secure)
Max kernel policy version:      34

SELinux policy version and repository: 20250528-1.1 from Slowroll repo-oss

The software (incl. version) that is affected by the SELinux issue and the
error message:=20
dbus-broker-36-2.3 (seems while interacting with gnome-remote-desktop-48.1-=
1.1
and snapper-0.12.2-2.2)
tpm2.0-tools-5.7-2.3

SELinux Audit log:
time->Fri Jun 13 13:10:41 2025
type=3DUSER_AVC msg=3Daudit(1749813041.073:50): pid=3D1945 uid=3D498 auid=
=3D4294967295
ses=3D4294967295 subj=3Dsystem_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg=
=3D'avc:=20
denied  { send_msg } for  scontext=3Dsystem_u:system_r:gnome_remote_desktop=
_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Ddbus permissive=3D1
exe=3D"/usr/bin/dbus-broker" sauid=3D498 hostname=3D? addr=3D? te=
rminal=3D?'
----
time->Fri Jun 13 13:15:06 2025
type=3DUSER_AVC msg=3Daudit(1749813306.534:328): pid=3D1945 uid=3D498 auid=
=3D4294967295
ses=3D4294967295 subj=3Dsystem_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg=
=3D'avc:=20
denied  { send_msg } for  scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Ddbus permissive=3D1
exe=3D"/usr/bin/dbus-broker" sauid=3D498 hostname=3D? addr=3D? te=
rminal=3D?'
----
time->Fri Jun 13 13:15:06 2025
type=3DAVC msg=3Daudit(1749813306.534:329): avc:  denied  { getopt } for  p=
id=3D6657
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:15:06 2025
type=3DAVC msg=3Daudit(1749813306.534:330): avc:  denied  { getattr } for  =
pid=3D6657
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:15:06 2025
type=3DAVC msg=3Daudit(1749813306.534:331): avc:  denied  { setopt } for  p=
id=3D6657
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:15:27 2025
type=3DAVC msg=3Daudit(1749813327.193:339): avc:  denied  { getopt } for  p=
id=3D7320
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:15:27 2025
type=3DAVC msg=3Daudit(1749813327.193:340): avc:  denied  { getattr } for  =
pid=3D7320
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:15:27 2025
type=3DAVC msg=3Daudit(1749813327.193:341): avc:  denied  { setopt } for  p=
id=3D7320
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:20:17 2025
type=3DAVC msg=3Daudit(1749813617.732:349): avc:  denied  { getopt } for  p=
id=3D12014
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:20:17 2025
type=3DAVC msg=3Daudit(1749813617.732:350): avc:  denied  { getattr } for=20
pid=3D12014 comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:sna=
pperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:20:17 2025
type=3DAVC msg=3Daudit(1749813617.732:351): avc:  denied  { setopt } for  p=
id=3D12014
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:20:50 2025
type=3DAVC msg=3Daudit(1749813650.320:359): avc:  denied  { getopt } for  p=
id=3D13018
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:20:50 2025
type=3DAVC msg=3Daudit(1749813650.320:360): avc:  denied  { getattr } for=20
pid=3D13018 comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:sna=
pperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:20:50 2025
type=3DAVC msg=3Daudit(1749813650.320:361): avc:  denied  { setopt } for  p=
id=3D13018
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:21:12 2025
type=3DAVC msg=3Daudit(1749813672.121:363): avc:  denied  { getopt } for  p=
id=3D13665
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:21:12 2025
type=3DAVC msg=3Daudit(1749813672.121:364): avc:  denied  { getattr } for=20
pid=3D13665 comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:sna=
pperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1
----
time->Fri Jun 13 13:21:12 2025
type=3DAVC msg=3Daudit(1749813672.121:365): avc:  denied  { setopt } for  p=
id=3D13665
comm=3D"tpm2_getcap" scontext=3Dsystem_u:system_r:snapperd_t:s0
tcontext=3Dsystem_u:system_r:tabrmd_t:s0 tclass=3Dunix_stream_socket permis=
sive=3D1

Any other important details:
The SELinux audit log entries relating to gnome-remote-desktop appear as so=
on
as I reach the graphical desktop
the error relating to tpm2_getcap appear when enrolling tpm2 for FDE, like =
on
zypper updates or sdbootutil enroll --method=3Dtpm2
I followed the guidance on https://en.opensuse.org/Portal:SELinux/Setup which
mentioned opening a bug report for errors appearing in ausearch
The system uses systemd-boot with full-disk encryption using the tpm for
unlocking on boot which seems to be handled in issue 1241964
<htt=
ps://bugzilla.opensuse.org/show_bug.cgi?id=3D1241964>
I could not find any similar issues related to gnome-remote-desktop

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

You are on the CC list for the bug.

=

--17498199312.6dBD37BA4.8882--


body:
--17498982060.6004AE.152
Date: Sat, 14 Jun 2025 10:50:06 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1244605
           Summary: TRACKERBUG: gpgme 2.0 related issues
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: crypto-maintainers-at-suse.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

gpgme contains a number of changes:

* API/ABI changes
* split of C++/Qt/Python bindings into separate packages

This bug tracks the work needed to get this into openSUSE.

Upstream information: https://dev.gnupg.org/T7262
Mailing list:
https://lists.opensuse.org/archives/list/factory-at-lists.opensuse.org/thread/=
NSVWPKKZGG3PZM7YTGAIO7MNET6YLN5A/

Packages should use the following build dependencies:

pkgconfig(gpgme)
pkgconfig(gpgmepp) or cmake(Gpgmepp)
cmake(QGpgmeQt6)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17498982060.6004AE.152
Date: Sat, 14 Jun 2025 10:50:06 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244605

          Summary
          TRACKERBUG: gpgme 2.0 related issues

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          crypto-maintainers@suse.de

          Reporter
          Andreas.Stieger@gmx.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

gpgme contains a number of changes:

* API/ABI changes
* split of C++/Qt/Python bindings into separate packages

This bug tracks the work needed to get this into openSUSE.

Upstream information: https://dev.g=
nupg.org/T7262
Mailing list:
https://lists.opensuse.or=
g/archives/list/factory@lists.opensuse.org/thread/NSVWPKKZGG3PZM7YTGAIO=
7MNET6YLN5A/

Packages should use the following build dependencies:

pkgconfig(gpgme)
pkgconfig(gpgmepp) or cmake(Gpgmepp)
cmake(QGpgmeQt6)

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

You are on the CC list for the bug.

=

--17498982060.6004AE.152--

pkgs: gpgmepp libcryptui libkleo python-gpg python-gpgme qgpgme seahorse seahorse-nautilus

summary: TRACKERBUG: gpgme 2.0 related issues


--17499880656.0FaC2.221
Date: Sun, 15 Jun 2025 11:47: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=3D1244617

            Bug ID: 1244617
           Summary: oqs-provider fails to build with openssl 3.5.
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: meissner-at-suse.com
          Reporter: meissner-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: crypto-maintainers-at-suse.de, lucas.mulling-at-suse.com,
                    meissner-at-suse.com, pmonrealgonzalez-at-suse.com,
                    qa-bugs-at-suse.de
            Blocks: 1241037
  Target Milestone: ---
          Found By: ---
           Blocker: ---

[   14s] + /usr/bin/ctest --output-on-failure --force-new-ctest-process -j4=
 .
[   14s] Test project
/home/abuild/rpmbuild/BUILD/oqs-provider-0.8.0-build/oqs-provider-0.8.0/bui=
ld
[   14s]     Start 1: oqs_signatures
[   14s]     Start 2: oqs_kems
[   14s]     Start 3: oqs_groups
[   14s]     Start 4: oqs_tlssig
[   14s] 1/6 Test #1: oqs_signatures ...................Subprocess
aborted***Exception:   0.00 sec
[   14s] error registering mldsa44 with no hash
[   14s]
/home/abuild/rpmbuild/BUILD/oqs-provider-0.8.0-build/oqs-provider-0.8.0/tes=
t/test_common.c:55:
OpenSSL internal error: OSSL_PROVIDER_available(libctx, modulename)
[   14s]=20
[   14s]     Start 5: oqs_endecode
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17499880656.0FaC2.221
Date: Sun, 15 Jun 2025 11:47:45 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244617

          Summary
          oqs-provider fails to build with openssl 3.5.

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          meissner@suse.com

          Reporter
          meissner@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          crypto-maintainers@suse.de, lucas.mulling@suse.com, m=
eissner@suse.com, pmonrealgonzalez@suse.com, qa-bugs@suse.de

          Blocks
          1241037

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

[   14s] + /usr/bin/ctest --output-on-failure --force-new-ct=
est-process -j4 .
[   14s] Test project
/home/abuild/rpmbuild/BUILD/oqs-provider-0.8.0-build/oqs-provider-0.8.0/bui=
ld
[   14s]     Start 1: oqs_signatures
[   14s]     Start 2: oqs_kems
[   14s]     Start 3: oqs_groups
[   14s]     Start 4: oqs_tlssig
[   14s] 1/6 Test #1: oqs_signatures ...................Subprocess
aborted***Exception:   0.00 sec
[   14s] error registering mldsa44 with no hash
[   14s]
/home/abuild/rpmbuild/BUILD/oqs-provider-0.8.0-build/oqs-provider-0.8.0/tes=
t/test_common.c:55:
OpenSSL internal error: OSSL_PROVIDER_available(libctx, modulename)
[   14s]=20
[   14s]     Start 5: oqs_endecode

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

You are on the CC list for the bug.

=

--17499880656.0FaC2.221--


body:
--17500720088.Be0CD6.1109
Date: Mon, 16 Jun 2025 11:06: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=3D1244636

            Bug ID: 1244636
           Summary: kget fails to build with gpgme 2
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1244605
  Target Milestone: ---
          Found By: ---
           Blocker: ---

kget fails to build with gpgme2.

From
https://build.opensuse.org/package/live_build_log/home:AndreasStieger:branc=
hes:Base:System/kget/localdep/x86_64

[  107s]
/home/abuild/rpmbuild/BUILD/kget-25.04.2-build/kget-25.04.2/ui/signaturedlg=
.cpp:
In member function =E2=80=98void SignatureDlg::updateData()=E2=80=99:
[  107s]
/home/abuild/rpmbuild/BUILD/kget-25.04.2-build/kget-25.04.2/ui/signaturedlg=
.cpp:188:84:
error: no match for =E2=80=98operator<<=E2=80=99 (operand types are =E2=80=
=98QDebug=E2=80=99 and
=E2=80=98GpgME::Error=E2=80=99)
[  107s]   188 |                 qCDebug(KGET_DEBUG) << "There was an error
while loading the key:" << err;
[  107s]       |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                    ^~ ~~~
[  107s]       |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                       |
[  107s]       |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                       GpgME::Error
[  107s] In file included from /usr/include/qt6/QtCore/qvariant.h:12,
[  107s]                  from /usr/include/qt6/QtGui/qaction.h:13,
[  107s]                  from /usr/include/qt6/QtWidgets/qwidget.h:12,
[  107s]                  from /usr/include/qt6/QtWidgets/qdialog.h:8,
[  107s]                  from /usr/include/qt6/QtWidgets/QDialog:1,
[  107s]                  from
/home/abuild/rpmbuild/BUILD/kget-25.04.2-build/kget-25.04.2/ui/../core/base=
dialog.h:24,
[  107s]                  from
/home/abuild/rpmbuild/BUILD/kget-25.04.2-build/kget-25.04.2/ui/signaturedlg=
.h:23,
[  107s]                  from
/home/abuild/rpmbuild/BUILD/kget-25.04.2-build/kget-25.04.2/ui/signaturedlg=
.cpp:20:
[  107s] /usr/include/qt6/QtCore/qdebug.h:171:13: note: candidate:
=E2=80=98template<class ... Args> QDebug& QDebug::operator<<(const
std::__cxx11::basic_string<char, Args ...>&)=E2=80=99
[  107s]   171 |     QDebug &operator<<(const std::basic_string<char, Args.=
..>
&s)
[  107s]       |             ^~~~~~~~
[  107s] /usr/include/qt6/QtCore/qdebug.h:171:13: note:   template argument
deduction/substitution failed:
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17500720088.Be0CD6.1109
Date: Mon, 16 Jun 2025 11:06: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
          1244636

          Summary
          kget fails to build with gpgme 2

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          KDE Applications

          Assignee
          opensuse-kde-bugs@opensuse.org

          Reporter
          Andreas.Stieger@gmx.de

          QA Contact
          qa-bugs@suse.de

          Blocks
          1244605

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

kget fails to build with gpgme2.

From
https://build.opensuse.org=
/package/live_build_log/home:AndreasStieger:branches:Base:System/kget/local=
dep/x86_64

[  107s]
/home/abuild/rpmbuild/BUILD/kget-25.04.2-build/kget-25.04.2/ui/signaturedlg=
.cpp:
In member function =E2=80=98void SignatureDlg::updateData()=E2=80=99:
[  107s]
/home/abuild/rpmbuild/BUILD/kget-25.04.2-build/kget-25.04.2/ui/signaturedlg=
.cpp:188:84:
error: no match for =E2=80=98operator<<=E2=80=99 (operand types are =
=E2=80=98QDebug=E2=80=99 and
=E2=80=98GpgME::Error=E2=80=99)
[  107s]   188 |                 qCDebug(KGET_DEBUG) << "There w=
as an error
while loading the key:" << err;
[  107s]       |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                    ^~ ~~~
[  107s]       |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                       |
[  107s]       |=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
                       GpgME::Error
[  107s] In file included from /usr/include/qt6/QtCore/qvariant.h:12,
[  107s]                  from /usr/include/qt6/QtGui/qaction.h:13,
[  107s]                  from /usr/include/qt6/QtWidgets/qwidget.h:12,
[  107s]                  from /usr/include/qt6/QtWidgets/qdialog.h:8,
[  107s]                  from /usr/include/qt6/QtWidgets/QDialog:1,
[  107s]                  from
/home/abuild/rpmbuild/BUILD/kget-25.04.2-build/kget-25.04.2/ui/../core/base=
dialog.h:24,
[  107s]                  from
/home/abuild/rpmbuild/BUILD/kget-25.04.2-build/kget-25.04.2/ui/signaturedlg=
.h:23,
[  107s]                  from
/home/abuild/rpmbuild/BUILD/kget-25.04.2-build/kget-25.04.2/ui/signaturedlg=
.cpp:20:
[  107s] /usr/include/qt6/QtCore/qdebug.h:171:13: note: candidate:
=E2=80=98template<class ... Args> QDebug& QDebug::operator<&lt=
;(const
std::__cxx11::basic_string<char, Args ...>&)=E2=80=99
[  107s]   171 |     QDebug &operator<<(const std::basic_string&l=
t;char, Args...>
&s)
[  107s]       |             ^~~~~~~~
[  107s] /usr/include/qt6/QtCore/qdebug.h:171:13: note:   template argument
deduction/substitution failed:

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

You are on the CC list for the bug.

=

--17500720088.Be0CD6.1109--

summary: kget fails to build with gpgme 2


body:
--17501058041.51B5F4.38
Date: Mon, 16 Jun 2025 20:30: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=3D1244666

            Bug ID: 1244666
           Summary: Can we get a gkrellm 2.4 package built?
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: rskunath-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

The current 2.3.x gkrellm package has been bulletproof stable for years, but
since the users count reporting switch a bit ago the user count in Procs is
always zero now.

I don't know if the 2.4 version fixes this but at least this is the first
release since Bill Wilson passed away.=20

If we can get the user count issue set and the other fixes out, that would =
be
great.

TIA

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

--17501058041.51B5F4.38
Date: Mon, 16 Jun 2025 20:30: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
          1244666

          Summary
          Can we get a gkrellm 2.4 package built?

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Minor

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          rskunath@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

The current 2.3.x gkrellm package has been bulletproof stabl=
e for years, but
since the users count reporting switch a bit ago the user count in Procs is
always zero now.

I don't know if the 2.4 version fixes this but at least this is the first
release since Bill Wilson passed away.=20

If we can get the user count issue set and the other fixes out, that would =
be
great.

TIA

Rick Kunath

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

You are on the CC list for the bug.

=

--17501058041.51B5F4.38--

summary: Can we get a gkrellm 2.4 package built?


--17501493565.4FcDED08.734
Date: Tue, 17 Jun 2025 08:35:56 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1244680
           Summary: python313 nogil-base varies across builds
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Python
          Assignee: python-maintainers-at-suse.com
          Reporter: bwiedemann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1062303
  Target Milestone: ---
          Found By: Development
           Blocker: ---

While working on reproducible builds for openSUSE, I found that
our python313 nogil-base multibuild part varies in every build, because it
embeds a random tmp path into a .h file:

+++ new//usr/src/debug/Python-3.13.3/jit_stencils.h     2025-05-28
09:46:40.000000000 +0000
@@ -1,4 +1,4 @@
-// 328520b884ec505101e4fc3a2327868c2c059f1ed58fa7a0a01f9d31b4ec0b2b
+// 3219f378cedf704058992098467811142b449e68f9a5abd745affb72eefcb60b
 // $ /usr/bin/python3.13 ./Tools/jit/build.py x86_64-suse-linux-gnu

 void
@@ -7,7 +7,7 @@
     const _PyUOpInstruction *instruction, uintptr_t instruction_starts[])
 {=20=20=20
     //
-    // /tmp/tmplnyoes0h/_BINARY_OP.o:  file format elf64-x86-64
+    // /tmp/tmp0bzcbam2/_BINARY_OP.o:  file format elf64-x86-64

additionally, 2 .pyc files in python313-nogil-testsuite vary.

-


--17501498760.1C1DDA.773
Date: Tue, 17 Jun 2025 08:44:36 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1244683
           Summary: nvptx-tools too old, causing linker errors
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: burnus-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: rguenther-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

https://github.com/SourceryTools/nvptx-tools was last updated in September
2024,
while the RPM package was last updated after end-of-May commit.

Namely: nvptx-tools-1.0+git.20240530.96f8fc5-1.3.x86_64

The following works with the current nvptx-tools from git,
but fails with the RPM version as shown below.

Please update.

Test that fails with the old nvptx-tools' ld:
  $ g++-15 -fopenmp test.cc -foffload=3Dnvptx-none
  unresolved symbol link
  collect2: error: ld returned 1 exit status
  nvptx mkoffload: fatal error: x86_64-suse-linux-accel-nvptx-none-gcc-15
returned 1 exit status
------------------
#include <iostream>

void f(int m) {
  if (m < 0)
    std::cout << "should not happen" << std::endl;
}

int main() {
  #pragma omp target
   f(1);
}

#pragma omp begin declare target
namespace __gnu_cxx {
  const char * zoneinfo_dir_override() { return "";}
}
#pragma omp end declare target
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17501498760.1C1DDA.773
Date: Tue, 17 Jun 2025 08:44:36 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244683

          Summary
          nvptx-tools too old, causing linker errors

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Development

          Assignee
          screening-team-bugs@suse.de

          Reporter
          burnus@gmx.de

          QA Contact
          qa-bugs@suse.de

          CC
          rguenther@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

htt=
ps://github.com/SourceryTools/nvptx-tools was last updated in September
2024,
while the RPM package was last updated after end-of-May commit.

Namely: nvptx-tools-1.0+git.20240530.96f8fc5-1.3.x86_64

The following works with the current nvptx-tools from git,
but fails with the RPM version as shown below.

Please update.

Test that fails with the old nvptx-tools' ld:
  $ g++-15 -fopenmp test.cc -foffload=3Dnvptx-none
  unresolved symbol link
  collect2: error: ld returned 1 exit status
  nvptx mkoffload: fatal error: x86_64-suse-linux-accel-nvptx-none-gcc-15
returned 1 exit status
------------------
#include <iostream>

void f(int m) {
  if (m < 0)
    std::cout << "should not happen" << std::endl;
}

int main() {
  #pragma omp target
   f(1);
}

#pragma omp begin declare target
namespace __gnu_cxx {
  const char * zoneinfo_dir_override() { return "";}
}
#pragma omp end declare target

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

You are on the CC list for the bug.

=

--17501498760.1C1DDA.773--


body:
--17501735632.AE5b3d.5599
Date: Tue, 17 Jun 2025 15:19: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=3D1244702

            Bug ID: 1244702
           Summary: AUDIT-0: <package name>: <topic>
    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: guillaume.gardet-at-arm.com
        QA Contact: security-team-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

For my package found in OBS in hardware/libgpiod I would like a whitelisting
for the following rpmlint error:

[   66s] libgpiod-manager.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/etc/dbus-1/system.d/io.gpiod1.conf (sha256 file digest default
filter:c8033257b782186356e9ebf636a58d39c86de1b0a55d1c127b107e698d9cde85 she=
ll
filter:1acfa8f50efc9a37dd8e5fc14434b9c38cc5446fe991bc753a1239a36e475fb5 xml
filter:4a620749a1b62fb229cd564e2ddafdd59e0302702c57ad7ac76ec5f56429f48b)
[   66s] Packaging D-Bus services requires a review and whitelisting by the
SUSE
[   66s] security team. If the package is intended for inclusion in any SUSE
product
[   66s] please open a bug report to request review of the package by the
security
[   66s] team. Please refer to
[   66s]
https://en.opensuse.org/openSUSE:Package_security_guidelines#audit_bugs for
[   66s] more information.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17501735632.AE5b3d.5599
Date: Tue, 17 Jun 2025 15:19:23 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244702

          Summary
          AUDIT-0: <package name>: <topic>

          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
          guillaume.gardet@arm.com

          QA Contact
          security-team@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

For my package found in OBS in hardware/libgpiod I would lik=
e a whitelisting
for the following rpmlint error:

[   66s] libgpiod-manager.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/etc/dbus-1/system.d/io.gpiod1.conf (sha256 file digest default
filter:c8033257b782186356e9ebf636a58d39c86de1b0a55d1c127b107e698d9cde85 she=
ll
filter:1acfa8f50efc9a37dd8e5fc14434b9c38cc5446fe991bc753a1239a36e475fb5 xml
filter:4a620749a1b62fb229cd564e2ddafdd59e0302702c57ad7ac76ec5f56429f48b)
[   66s] Packaging D-Bus services requires a review and whitelisting by the
SUSE
[   66s] security team. If the package is intended for inclusion in any SUSE
product
[   66s] please open a bug report to request review of the package by the
security
[   66s] team. Please refer to
[   66s]
https://en.opensuse.org/openSUSE:Package_security_guidelines#audit=
_bugs for
[   66s] more information.

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

You are on the CC list for the bug.

=

--17501735632.AE5b3d.5599--

summary: AUDIT-0: <package name>: <topic>


body:
--17501962004.E000B.8296
Date: Tue, 17 Jun 2025 21:36:40 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1244711
           Summary: VUL-0: chromium 137.0.7151.119 release
    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: ro-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

[420697404] High CVE-2025-6191: Integer overflow in V8.
[421471016] High CVE-2025-6192: Use after free in Profiler.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17501962004.E000B.8296
Date: Tue, 17 Jun 2025 21:36:40 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244711

          Summary
          VUL-0: chromium 137.0.7151.119 release

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

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

[420697404] High CVE-2025-6191: Integer overflow in V8.
[421471016] High CVE-2025-6192: Use after free in Profiler.

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

You are on the CC list for the bug.

=

--17501962004.E000B.8296--

summary: VUL-0: chromium 137.0.7151.119 release


--17502288740.874EEefB1.10066
Date: Wed, 18 Jun 2025 06:41:14 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1244714
           Summary: VUL-0: CVE-2025-49847: llama-cpp: buffer overflow in helper _try_copy in llama.cpp/src/vocab.cpp
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/459837/
                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: andrea.mattiazzo-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

llama.cpp is an inference of several LLM models in C/C++. Prior to version
b5662, an attacker=E2=80=90supplied GGUF model vocabulary can trigger a buf=
fer overflow
in llama.cpp=E2=80=99s vocabulary=E2=80=90loading code. Specifically, the h=
elper _try_copy in
llama.cpp/src/vocab.cpp: llama_vocab::impl::token_to_piece() casts a very l=
arge
size_t token length into an int32_t, causing the length check (if (length <
(int32_t)size)) to be bypassed. As a result, memcpy is still called with th=
at
oversized size, letting a malicious model overwrite memory beyond the inten=
ded
buffer. This can lead to arbitrary memory corruption and potential code
execution. This issue has been patched in version b5662.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-49847
https://bugzilla.redhat.com/show_bug.cgi?id=3D2373282
https://www.cve.org/CVERecord?id=3DCVE-2025-49847
https://github.com/ggml-org/llama.cpp/commit/3cfbbdb44e08fd19429fed6cc85b98=
2a91f0efd5
https://github.com/ggml-org/llama.cpp/security/advisories/GHSA-8wwf-w4qm-gp=
qr
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17502288740.874EEefB1.10066
Date: Wed, 18 Jun 2025 06:41:14 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1244714

          Summary
          VUL-0: CVE-2025-49847: llama-cpp: buffer overflow in helper _=
try_copy in llama.cpp/src/vocab.cpp

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

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

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

llama.cpp is an inference of several LLM models in C/C++. Pr=
ior to version
b5662, an attacker=E2=80=90supplied GGUF model vocabulary can trigger a buf=
fer overflow
in llama.cpp=E2=80=99s vocabulary=E2=80=90loading code. Specifically, the h=
elper _try_copy in
llama.cpp/src/vocab.cpp: llama_vocab::impl::token_to_piece() casts a very l=
arge
size_t token length into an int32_t, causing the length check (if (length &=
lt;
(int32_t)size)) to be bypassed. As a result, memcpy is still called with th=
at
oversized size, letting a malicious model overwrite memory beyond the inten=
ded
buffer. This can lead to arbitrary memory corruption and potential code
execution. This issue has been patched in version b5662.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-49847
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2373282
https://www.c=
ve.org/CVERecord?id=3DCVE-2025-49847
https://github.com/ggml-org/llama.cpp/commit/3cfbbdb=
44e08fd19429fed6cc85b982a91f0efd5
https://github.com/ggml-org/llama.cpp/security/advisories/GH=
SA-8wwf-w4qm-gpqr

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

You are on the CC list for the bug.

=

--17502288740.874EEefB1.10066--


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

When using Konsole or Kate (or any other Qt application) on Tumbleweed, Uni=
code
characters are not rendered properly, nor are emoji handled properly

Reproducible: Always

Steps to Reproduce:
1. Open Konsole
2. run `echo -e '\u2802'
3. Copy the output and paste it into Kate
Actual Results:=20=20
Konsole displays a generic box, when copied and pasted, Kate does the same

Expected Results:=20=20
Konsole prints the proper =E2=A0=82 braille glyph associated with Unicode c=
haracter
u+2802

This works fine in Konsole from Flatpak, as the Flatpak org.kde.Platform *i=
s*
compiled with Unicode and Emoji support.

Our Qt6 is compiled without this support

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

You are on the CC list for the bug.

=

--17503150396.6a6cAD2fD.16977--

summary: Qt6 is lacking Unicode and Emoji support in the default build


--17506114981.4A8EAA8f.23396
Date: Sun, 22 Jun 2025 16:58: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=3D1245167

            Bug ID: 1245167
           Summary: kernel: iio / bmp280: most easurement readings time out since kernel 6.13.x
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel:Drivers
          Assignee: kernel-bugs-at-suse.de
          Reporter: Stromeko@NexGo.DE
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

After the update to a kernel 6.13 or up the IIO device files for my BME280
sensor can't be read most of the time:

cat: '/sys/bus/iio/devices/iio:device0/in_temp_input': Device or resource b=
usy
cat: '/sys/bus/iio/devices/iio:device0/in_humidityrelative_input': Device or
resource busy
cat: '/sys/bus/iio/devices/iio:device0/in_pressure_input': Device or resour=
ce
busy

That particular IIC bus has a BME280 and DS3231M in daisy-chain. The BME280=
 is
handled differently than before:

[ 2147.889803] [   T2128] bmp280 1-0076: Measurement cycle didn't complete.

Oversampling ratio is set to 1, so one read per second should not produce s=
uch
errors.  A single digit percentage of the reads actually succeed, but that =
is
of course not useful, just showing that the sensor is still working.

I've finally figured out that this was indeed some intentional change that =
went
into kernel 6.13rc1:

https://github.com/torvalds/linux/commit/26ccfaa9ddaaeaa7421a60323acaeb536a=
f5d5b2

The error seems to indicate that the driver does not calculate the wait time
correctly.  I have not found out if there's a way to get it back to the
previous "normal mode" behaviour (my reading of the change is that forced m=
ode
is used unconditionally) and it's not even clear if that would avoid the
wait_conv call that throws the error.  Additionally the code seems to leave=
 no
way to resume the read at a later time since it will put the sensor to sleep
again and wake it up in forced mode after it failed to complete the measure=
ment
cycle=E2=80=A6

I used to compile the driver myself before it got added to Tumbleweed, but =
due
to the safety measures introduced some time back that won't work (at least =
not
without additional steps, which I don't know) and I would have to dig out t=
he
procedure of exactly how I compiled the driver from back then and see if it
still works as well.  Would it be possible to get a driver that has an exte=
nded
measurement interval or just tries again when it hits the busy flag?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17506114981.4A8EAA8f.23396
Date: Sun, 22 Jun 2025 16:58: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
          1245167

          Summary
          kernel: iio / bmp280: most easurement readings time out since=
 kernel 6.13.x

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel:Drivers

          Assignee
          kernel-bugs@suse.de

          Reporter
          Stromeko@NexGo.DE

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

After the update to a kernel 6.13 or up the IIO device files=
 for my BME280
sensor can't be read most of the time:

cat: '/sys/bus/iio/devices/iio:device0/in_temp_input': Device or resource b=
usy
cat: '/sys/bus/iio/devices/iio:device0/in_humidityrelative_input': Device or
resource busy
cat: '/sys/bus/iio/devices/iio:device0/in_pressure_input': Device or resour=
ce
busy

That particular IIC bus has a BME280 and DS3231M in daisy-chain. The BME280=
 is
handled differently than before:

[ 2147.889803] [   T2128] bmp280 1-0076: Measurement cycle didn't complete.

Oversampling ratio is set to 1, so one read per second should not produce s=
uch
errors.  A single digit percentage of the reads actually succeed, but that =
is
of course not useful, just showing that the sensor is still working.

I've finally figured out that this was indeed some intentional change that =
went
into kernel 6.13rc1:

https://github.com/torvalds/linux/commit/26ccfaa9ddaaeaa=
7421a60323acaeb536af5d5b2

The error seems to indicate that the driver does not calculate the wait time
correctly.  I have not found out if there's a way to get it back to the
previous "normal mode" behaviour (my reading of the change is tha=
t forced mode
is used unconditionally) and it's not even clear if that would avoid the
wait_conv call that throws the error.  Additionally the code seems to leave=
 no
way to resume the read at a later time since it will put the sensor to sleep
again and wake it up in forced mode after it failed to complete the measure=
ment
cycle=E2=80=A6

I used to compile the driver myself before it got added to Tumbleweed, but =
due
to the safety measures introduced some time back that won't work (at least =
not
without additional steps, which I don't know) and I would have to dig out t=
he
procedure of exactly how I compiled the driver from back then and see if it
still works as well.  Would it be possible to get a driver that has an exte=
nded
measurement interval or just tries again when it hits the busy flag?

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

You are on the CC list for the bug.

=

--17506114981.4A8EAA8f.23396--


--17507612762.cd8255e.31451
Date: Tue, 24 Jun 2025 10:34: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=3D1245263

            Bug ID: 1245263
           Summary: libz-ng-compat1 breaks read-only-root-fs setup-etc-subvol
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

If libz-ng-compat1 is used instead of libz1, the libz.so.1 requirement is
satisfied by /usr/lib64/zlib-ng-compat/libz.so.1. This path is configured by
/etc/ld.so.conf.d/zlib-ng-compat-x86_64.conf.

setup-etc-subvol converts the /etc directory to a subvolume by doing

mv /etc /etc.transactional-update
btrfs subvolume create /etc
rsync --quiet --archive --xattrs --acls /etc.transactional-update/ /etc
rm -r /etc.transactional-update

(https://github.com/openSUSE/read-only-root-fs/blob/2b91c50d04acacc34b46a15=
6b49f99baf361f1dc/usr/libexec/setup-etc-subvol)

This fails because the initial mv makes ld.so.conf.d unavailable and the
following invocation of btrfs thus fails because ld.so no longer knows wher=
e to
find libz.so.1.

IMO the only good option to fix this is to move the ld.so.conf.d snippet fr=
om
/etc to /usr.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17507612762.cd8255e.31451
Date: Tue, 24 Jun 2025 10:34: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
          1245263

          Summary
          libz-ng-compat1 breaks read-only-root-fs setup-etc-subvol

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Development

          Assignee
          screening-team-bugs@suse.de

          Reporter
          fvogt@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

If libz-ng-compat1 is used instead of libz1, the libz.so.1 r=
equirement is
satisfied by /usr/lib64/zlib-ng-compat/libz.so.1. This path is configured by
/etc/ld.so.conf.d/zlib-ng-compat-x86_64.conf.

setup-etc-subvol converts the /etc directory to a subvolume by doing

mv /etc /etc.transactional-update
btrfs subvolume create /etc
rsync --quiet --archive --xattrs --acls /etc.transactional-update/ /etc
rm -r /etc.transactional-update

(https://github.c=
om/openSUSE/read-only-root-fs/blob/2b91c50d04acacc34b46a156b49f99baf361f1dc=
/usr/libexec/setup-etc-subvol)

This fails because the initial mv makes ld.so.conf.d unavailable and the
following invocation of btrfs thus fails because ld.so no longer knows wher=
e to
find libz.so.1.

IMO the only good option to fix this is to move the ld.so.conf.d snippet fr=
om
/etc to /usr.

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

You are on the CC list for the bug.

=

--17507612762.cd8255e.31451--


--17507696582.4FE7.31988
Date: Tue, 24 Jun 2025 12:54: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=3D1245288

            Bug ID: 1245288
           Summary: VUL-0: CVE-2025-6547: python-pytest-html: pbkdf2: static keys returned when processing Uint8Array input
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/460886/
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: python-maintainers-at-suse.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: 1245271
  Target Milestone: ---
          Deadline: 2025-07-11
          Found By: Security Response Team
           Blocker: ---

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

Improper Input Validation vulnerability in pbkdf2 allows Signature Spoofing=
 by
Improper Validation.This issue affects pbkdf2: <=3D3.1.2.

References:
https://github.com/browserify/pbkdf2/commit/e3102a8cd4830a3ac85cd0dd011cc00=
2fdde33bb
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-6547
https://www.cve.org/CVERecord?id=3DCVE-2025-6547
https://github.com/browserify/pbkdf2/security/advisories/GHSA-v62p-rq8g-8h59
https://bugzilla.redhat.com/show_bug.cgi?id=3D2374378
https://github.com/CVEProject/cvelistV5/blob/main//cves/2025/6xxx/CVE-2025-=
6547.json
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17507696582.4FE7.31988
Date: Tue, 24 Jun 2025 12:54: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
          1245288

          Summary
          VUL-0: CVE-2025-6547: python-pytest-html: pbkdf2: static keys=
 returned when processing Uint8Array input

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Security

          Assignee
          python-maintainers@suse.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
          1245271

          Target Milestone
          ---

          Deadline
          2025-07-11

          Found By
          Security Response Team

          Blocker
          ---

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

Improper Input Validation vulnerability in pbkdf2 allows Signature Spoofing=
 by
Improper Validation.This issue affects pbkdf2: <=3D3.1.2.

References:
https://github.com/browserify/pbkdf2/commit/e3102a8cd=
4830a3ac85cd0dd011cc002fdde33bb
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2025-6547
https://www.cv=
e.org/CVERecord?id=3DCVE-2025-6547
https://github.com/browserify/pbkdf2/security/advisories/GHSA=
-v62p-rq8g-8h59
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2374378
https://github.com/CVEProject/cvelistV5/blob/main//cv=
es/2025/6xxx/CVE-2025-6547.json

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

You are on the CC list for the bug.

=

--17507696582.4FE7.31988--