--16902000581.B0ceDA25.20979
Date: Mon, 24 Jul 2023 12:00:58 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1213595
           Summary: Live ISO does not creates Persistent storage
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Live Medium
          Assignee: fvogt-at-suse.com
          Reporter: sehsuvarselmanoglu-at-hotmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 868398
  --> https://bugzilla.suse.com/attachment.cgi?id=3D868398&action=3Dedit
7z File for some logs

Hi,
I downloaded OpenSUSE Leap ISO
(openSUSE-Leap-15.5-KDE-Live-x86_64-Build10.40-Media.iso) at 08/06/2023 (as
soon as released) then I =E2=80=9Cdd=E2=80=9D to USB stick and plugged to c=
omputer and it
worked fine. At first boot, it did create the persistent storage cow (boot.=
log
: [   22.002982] dracut-initqueue[877]: mke2fs 1.46.4 (18-Aug-2021) )

Few days later I download again this time build number was different
(openSUSE-Leap-15.5-KDE-Live-x86_64-Build10.57-Media.iso). At first boot, it
did not create persistent storage. dracut says (boot.log : [   21.489260]
dracut-initqueue[769]: Warning: Falling back to temporary overlay)
same as the new release
(openSUSE-Leap-15.5-KDE-Live-x86_64-Build10.73-Media.iso)

Any release after 10.40 does not creates persistent storage (neither 10.53 =
nor
10.73)=20

I tried with different CPU (AMD, Core Duo, I5) and different USB stick (4GB=
 8GB
16GB and 32GB) even with different port (USB2 USB3) with different USB s an=
d so
on. No matter what I tried don't work. Releases after 10.40 (10.57 or 10.73=
) do=20
not creates the persistent storage.

So I open discussion on the forums.opensuse.org and someone suggested that=
=20
I need to open bug report. and he/she wrote "It is not something you can fix
without recreating initrd. The script that is used here comes from kiwi dra=
cut
module.".

I also add the 7zip file for each ISO "....10.40", "...10.57", "...10.73" t=
hat
contains some log files.

"boot.log" : "sudo cp /var/log/boot.log"
"boot.msg" : "cp /var/log/boot.msg"
"dmesg.txt" : Output of "dmesg" right after the first boot
"fdisk.txt" : 0utput of "fdisk -l" right after first boot
"journal.txt" : Output of "sudo journalctl --no-pager --full -b"

Thank you very much.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16902000581.B0ceDA25.20979
Date: Mon, 24 Jul 2023 12:00:58 +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
          1213595

          Summary
          Live ISO does not creates Persistent storage

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          x86-64

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Live Medium

          Assignee
          fvogt@suse.com

          Reporter
          sehsuvarselmanoglu@hotmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 86839=
8 [details]
7z File for some logs

Hi,
I downloaded OpenSUSE Leap ISO
(openSUSE-Leap-15.5-KDE-Live-x86_64-Build10.40-Media.iso) at 08/06/2023 (as
soon as released) then I =E2=80=9Cdd=E2=80=9D to USB stick and plugged to c=
omputer and it
worked fine. At first boot, it did create the persistent storage cow (boot.=
log
: [   22.002982] dracut-initqueue[877]: mke2fs 1.46.4 (18-Aug-2021) )

Few days later I download again this time build number was different
(openSUSE-Leap-15.5-KDE-Live-x86_64-Build10.57-Media.iso). At first boot, it
did not create persistent storage. dracut says (boot.log : [   21.489260]
dracut-initqueue[769]: Warning: Falling back to temporary overlay)
same as the new release
(openSUSE-Leap-15.5-KDE-Live-x86_64-Build10.73-Media.iso)

Any release after 10.40 does not creates persistent storage (neither 10.53 =
nor
10.73)=20

I tried with different CPU (AMD, Core Duo, I5) and different USB stick (4GB=
 8GB
16GB and 32GB) even with different port (USB2 USB3) with different USB s an=
d so
on. No matter what I tried don't work. Releases after 10.40 (10.57 or 10.73=
) do=20
not creates the persistent storage.

So I open discussion on the forums.opensuse.org and someone suggested that=
=20
I need to open bug report. and he/she wrote "It is not something you c=
an fix
without recreating initrd. The script that is used here comes from kiwi dra=
cut
module.".

I also add the 7zip file for each ISO "....10.40", "...10.57=
", "...10.73" that
contains some log files.

"boot.log" : "sudo cp /var/log/boot.log"
"boot.msg" : "cp /var/log/boot.msg"
"dmesg.txt" : Output of "dmesg" right after the first b=
oot
"fdisk.txt" : 0utput of "fdisk -l" right after first bo=
ot
"journal.txt" : Output of "sudo journalctl --no-pager --full=
 -b"

Thank you very much.

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

You are on the CC list for the bug.

=

--16902000581.B0ceDA25.20979--


--16903886333.6d31Ed30.27060
Date: Wed, 26 Jul 2023 16:23:53 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1213692
           Summary: AUDIT-WHITELIST: org.freedesktop.home1.service is being moved from systemd-experimental to systemd-homed
    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: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Hi,

systemd-homed is no more considered as an experimental feature and as such =
it
has been moved to a dedicated sub-package named "systemd-homed".

This change has just been submitted: sr#1100898

Since rpmlint whitelistings are tied to individual packages it needs to be
updated accordingly.

For the logs of the build failure, see:
https://build.opensuse.org/package/live_build_log/Base:System/systemd/stand=
ard/x86_64

Could anyone take care of this ?

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

--16903886333.6d31Ed30.27060
Date: Wed, 26 Jul 2023 16:23:53 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1213692

          Summary
          AUDIT-WHITELIST: org.freedesktop.home1.service is being moved=
 from systemd-experimental to systemd-homed

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

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Hi,

systemd-homed is no more considered as an experimental feature and as such =
it
has been moved to a dedicated sub-package named "systemd-homed".

This change has just been submitted: sr#1100898

Since rpmlint whitelistings are tied to individual packages it needs to be
updated accordingly.

For the logs of the build failure, see:
https://build.opensuse.org/package/live_build_log/Ba=
se:System/systemd/standard/x86_64

Could anyone take care of this ?

Thanks.

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

You are on the CC list for the bug.

=

--16903886333.6d31Ed30.27060--


--16904115501.037890B.27507
Date: Wed, 26 Jul 2023 22:45:50 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1213698
           Summary: We have .cpython-311.pyc in non-311 packages
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Python
          Assignee: python-maintainers-at-suse.com
          Reporter: mcepl-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: bwiedemann-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I have been reminded about this:

-/usr/lib/python3.9/site-packages/blinker/__pycache__/base.cpython-311.pyc
6e33550a94efe8668e6b60422f1a674c9844fd6c44e92c0afcc5d98e71cf51cb 0
+/usr/lib/python3.9/site-packages/blinker/__pycache__/base.cpython-311.pyc
0b7e8cb203ad88028706b7204f007bb66a860cf3cfd6ebde4964a4caf6c248ef 0

why are 311.pyc files in the 3.9 path?

We run make html without specifying Python used. It runs the Sphinx builder
with /usr/bin/python3 which is now Python 3.11 and it loads (and generates
*.pyc) when collecting information on the installed libraries.

Suggested solution is https://stackoverflow.com/q/34025113/164233 and I have
tried it in https://build.opensuse.org/request/show/1100942

However, it seems like too complicated problem (patching every package). Any
other ideas?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16904115501.037890B.27507
Date: Wed, 26 Jul 2023 22:45:50 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1213698

          Summary
          We have .cpython-311.pyc in non-311 packages

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Python

          Assignee
          python-maintainers@suse.com

          Reporter
          mcepl@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          bwiedemann@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I have been reminded about this:

-/usr/lib/python3.9/site-packages/blinker/__pycache__/base.cpython-311.pyc
6e33550a94efe8668e6b60422f1a674c9844fd6c44e92c0afcc5d98e71cf51cb 0
+/usr/lib/python3.9/site-packages/blinker/__pycache__/base.cpython-311.pyc
0b7e8cb203ad88028706b7204f007bb66a860cf3cfd6ebde4964a4caf6c248ef 0

why are 311.pyc files in the 3.9 path?

We run make html without specifying Python used. It runs the Sphinx builder
with /usr/bin/python3 which is now Python 3.11 and it loads (and generates
*.pyc) when collecting information on the installed libraries.

Suggested solution is https://stackoverflow.com/q/34025113/164233 and I have
tried it in htt=
ps://build.opensuse.org/request/show/1100942

However, it seems like too complicated problem (patching every package). Any
other ideas?

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

You are on the CC list for the bug.

=

--16904115501.037890B.27507--


body:
--16904690411.8BcF951.29412
Date: Thu, 27 Jul 2023 14:44:01 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1213721
           Summary: [SELinux] <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: jbohac-at-suse.com
        QA Contact: security-team-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

The new versions of kdump (since v1.9.0) save the initrd in
/var/lib/kdump/initrd and maintain a symlink to the kernel the initrd has b=
een
build for in /var/lib/kdump/kernel.

E.g.:
        dhcp198:~ # ls -lZ /var/lib/kdump/
        total 35476
        -rw-------. 1 root root system_u:object_r:kdump_var_lib_t:s0 363229=
84
Jul 27 14:28 initrd
        lrwxrwxrwx. 1 root root system_u:object_r:kdump_var_lib_t:s0       =
40
Jul 27 14:28 kernel -> /usr/lib/modules/6.3.9-5-default/vmlinuz

SELinux blocks the following of the symlink during kdump service start.

audit2allow suggests:
        allow kdump_t kdump_var_lib_t:lnk_file read;

To me (a comlete SELinux noob) this makes sense and indeed creating and loa=
ding
a module with
        audit2allow -M kdump-fix < /var/log/audit/audit.log=20
        semodule -i kdump-fix.pp
fixes the problem.

Operating System: openSUSE MicroOS

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

SELinux policy version and repository: <TODO>
        dhcp198:~ # rpm -qa|grep selinux-pol
        selinux-policy-20230622-2.1.noarch
        selinux-policy-targeted-20230622-2.1.noarch

The software (incl. version) that is affected by the SELinux issue and the
error message: kdump
SELinux Audit log:=20
        dhcp198:~ # ausearch -ts today -m avc
        ----
        time->Thu Jul 27 14:26:15 2023
        type=3DPROCTITLE msg=3Daudit(1690467975.028:134):
proctitle=3D2F7362696E2F6B65786563002D70002F7661722F6C69622F6B64756D702F6B6=
5726E656C002D2D617070656E643D2072642E74696D656F75743D36302072642E7265747279=
3D34352071756965742073797374656D642E73686F775F7374617475733D79657320636F6E7=
36F6C653D74747953302C31313532303020636F6E73
        type=3DSYSCALL msg=3Daudit(1690467975.028:134): arch=3Dc000003e sys=
call=3D257
success=3Dno exit=3D-13 a0=3Dffffff9c a1=3D7ffd0d633da7 a2=3D0 a3=3D0 items=
=3D0 ppid=3D4833
pid=3D4834 auid=3D4294967295 uid=3D0 gid=3D0 euid=3D0 suid=3D0 fsuid=3D0 eg=
id=3D0 sgid=3D0
fsgid=3D0 tty=3D(none) ses=3D4294967295 comm=3D"kexec" exe=3D"/usr/sbin/kex=
ec"
subj=3Dsystem_u:system_r:kdump_t:s0 key=3D(null)
        type=3DAVC msg=3Daudit(1690467975.028:134): avc:  denied  { read } =
for=20
pid=3D4834 comm=3D"kexec" name=3D"kernel" dev=3D"sda3" ino=3D48130
scontext=3Dsystem_u:system_r:kdump_t:s0
tcontext=3Dsystem_u:object_r:kdump_var_lib_t:s0 tclass=3Dlnk_file permissiv=
e=3D0
        ----
        time->Thu Jul 27 14:26:15 2023
        type=3DPROCTITLE msg=3Daudit(1690467975.032:135):
proctitle=3D2F7362696E2F6B65786563002D70002F7661722F6C69622F6B64756D702F6B6=
5726E656C002D2D617070656E643D2072642E74696D656F75743D36302072642E7265747279=
3D34352071756965742073797374656D642E73686F775F7374617475733D79657320636F6E7=
36F6C653D74747953302C31313532303020636F6E73
        type=3DSYSCALL msg=3Daudit(1690467975.032:135): arch=3Dc000003e sys=
call=3D257
success=3Dno exit=3D-13 a0=3Dffffff9c a1=3D7ffc2c117daa a2=3D0 a3=3D0 items=
=3D0 ppid=3D4835
pid=3D4836 auid=3D4294967295 uid=3D0 gid=3D0 euid=3D0 suid=3D0 fsuid=3D0 eg=
id=3D0 sgid=3D0
fsgid=3D0 tty=3D(none) ses=3D4294967295 comm=3D"kexec" exe=3D"/usr/sbin/kex=
ec"
subj=3Dsystem_u:system_r:kdump_t:s0 key=3D(null)
        type=3DAVC msg=3Daudit(1690467975.032:135): avc:  denied  { read } =
for=20
pid=3D4836 comm=3D"kexec" name=3D"kernel" dev=3D"sda3" ino=3D48130
scontext=3Dsystem_u:system_r:kdump_t:s0
tcontext=3Dsystem_u:object_r:kdump_var_lib_t:s0 tclass=3Dlnk_file permissiv=
e=3D0
        ----
        time->Thu Jul 27 14:26:15 2023
        type=3DPROCTITLE msg=3Daudit(1690467975.032:136):
proctitle=3D2F7362696E2F6B65786563002D70002F7661722F6C69622F6B64756D702F6B6=
5726E656C002D2D617070656E643D2072642E74696D656F75743D36302072642E7265747279=
3D34352071756965742073797374656D642E73686F775F7374617475733D79657320636F6E7=
36F6C653D74747953302C31313532303020636F6E73
        type=3DSYSCALL msg=3Daudit(1690467975.032:136): arch=3Dc000003e sys=
call=3D257
success=3Dno exit=3D-13 a0=3Dffffff9c a1=3D7ffc2c117daa a2=3D0 a3=3D0 items=
=3D0 ppid=3D4835
pid=3D4836 auid=3D4294967295 uid=3D0 gid=3D0 euid=3D0 suid=3D0 fsuid=3D0 eg=
id=3D0 sgid=3D0
fsgid=3D0 tty=3D(none) ses=3D4294967295 comm=3D"kexec" exe=3D"/usr/sbin/kex=
ec"
subj=3Dsystem_u:system_r:kdump_t:s0 key=3D(null)
        type=3DAVC msg=3Daudit(1690467975.032:136): avc:  denied  { read } =
for=20
pid=3D4836 comm=3D"kexec" name=3D"kernel" dev=3D"sda3" ino=3D48130
scontext=3Dsystem_u:system_r:kdump_t:s0
tcontext=3Dsystem_u:object_r:kdump_var_lib_t:s0 tclass=3Dlnk_file permissiv=
e=3D0
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16904690411.8BcF951.29412
Date: Thu, 27 Jul 2023 14:44:01 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1213721

          Summary
          [SELinux] <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
          jbohac@suse.com

          QA Contact
          security-team@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

The new versions of kdump (since v1.9.0) save the initrd in
/var/lib/kdump/initrd and maintain a symlink to the kernel the initrd has b=
een
build for in /var/lib/kdump/kernel.

E.g.:
        dhcp198:~ # ls -lZ /var/lib/kdump/
        total 35476
        -rw-------. 1 root root system_u:object_r:kdump_var_lib_t:s0 363229=
84
Jul 27 14:28 initrd
        lrwxrwxrwx. 1 root root system_u:object_r:kdump_var_lib_t:s0       =
40
Jul 27 14:28 kernel -> /usr/lib/modules/6.3.9-5-default/vmlinuz

SELinux blocks the following of the symlink during kdump service start.

audit2allow suggests:
        allow kdump_t kdump_var_lib_t:lnk_file read;

To me (a comlete SELinux noob) this makes sense and indeed creating and loa=
ding
a module with
        audit2allow -M kdump-fix < /var/log/audit/audit.log=20
        semodule -i kdump-fix.pp
fixes the problem.

Operating System: openSUSE MicroOS

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

SELinux policy version and repository: <TODO>
        dhcp198:~ # rpm -qa|grep selinux-pol
        selinux-policy-20230622-2.1.noarch
        selinux-policy-targeted-20230622-2.1.noarch

The software (incl. version) that is affected by the SELinux issue and the
error message: kdump
SELinux Audit log:=20
        dhcp198:~ # ausearch -ts today -m avc
        ----
        time->Thu Jul 27 14:26:15 2023
        type=3DPROCTITLE msg=3Daudit(1690467975.028:134):
proctitle=3D2F7362696E2F6B65786563002D70002F7661722F6C69622F6B64756D702F6B6=
5726E656C002D2D617070656E643D2072642E74696D656F75743D36302072642E7265747279=
3D34352071756965742073797374656D642E73686F775F7374617475733D79657320636F6E7=
36F6C653D74747953302C31313532303020636F6E73
        type=3DSYSCALL msg=3Daudit(1690467975.028:134): arch=3Dc000003e sys=
call=3D257
success=3Dno exit=3D-13 a0=3Dffffff9c a1=3D7ffd0d633da7 a2=3D0 a3=3D0 items=
=3D0 ppid=3D4833
pid=3D4834 auid=3D4294967295 uid=3D0 gid=3D0 euid=3D0 suid=3D0 fsuid=3D0 eg=
id=3D0 sgid=3D0
fsgid=3D0 tty=3D(none) ses=3D4294967295 comm=3D"kexec" exe=3D&quo=
t;/usr/sbin/kexec"
subj=3Dsystem_u:system_r:kdump_t:s0 key=3D(null)
        type=3DAVC msg=3Daudit(1690467975.028:134): avc:  denied  { read } =
for=20
pid=3D4834 comm=3D"kexec" name=3D"kernel" dev=3D"s=
da3" ino=3D48130
scontext=3Dsystem_u:system_r:kdump_t:s0
tcontext=3Dsystem_u:object_r:kdump_var_lib_t:s0 tclass=3Dlnk_file permissiv=
e=3D0
        ----
        time->Thu Jul 27 14:26:15 2023
        type=3DPROCTITLE msg=3Daudit(1690467975.032:135):
proctitle=3D2F7362696E2F6B65786563002D70002F7661722F6C69622F6B64756D702F6B6=
5726E656C002D2D617070656E643D2072642E74696D656F75743D36302072642E7265747279=
3D34352071756965742073797374656D642E73686F775F7374617475733D79657320636F6E7=
36F6C653D74747953302C31313532303020636F6E73
        type=3DSYSCALL msg=3Daudit(1690467975.032:135): arch=3Dc000003e sys=
call=3D257
success=3Dno exit=3D-13 a0=3Dffffff9c a1=3D7ffc2c117daa a2=3D0 a3=3D0 items=
=3D0 ppid=3D4835
pid=3D4836 auid=3D4294967295 uid=3D0 gid=3D0 euid=3D0 suid=3D0 fsuid=3D0 eg=
id=3D0 sgid=3D0
fsgid=3D0 tty=3D(none) ses=3D4294967295 comm=3D"kexec" exe=3D&quo=
t;/usr/sbin/kexec"
subj=3Dsystem_u:system_r:kdump_t:s0 key=3D(null)
        type=3DAVC msg=3Daudit(1690467975.032:135): avc:  denied  { read } =
for=20
pid=3D4836 comm=3D"kexec" name=3D"kernel" dev=3D"s=
da3" ino=3D48130
scontext=3Dsystem_u:system_r:kdump_t:s0
tcontext=3Dsystem_u:object_r:kdump_var_lib_t:s0 tclass=3Dlnk_file permissiv=
e=3D0
        ----
        time->Thu Jul 27 14:26:15 2023
        type=3DPROCTITLE msg=3Daudit(1690467975.032:136):
proctitle=3D2F7362696E2F6B65786563002D70002F7661722F6C69622F6B64756D702F6B6=
5726E656C002D2D617070656E643D2072642E74696D656F75743D36302072642E7265747279=
3D34352071756965742073797374656D642E73686F775F7374617475733D79657320636F6E7=
36F6C653D74747953302C31313532303020636F6E73
        type=3DSYSCALL msg=3Daudit(1690467975.032:136): arch=3Dc000003e sys=
call=3D257
success=3Dno exit=3D-13 a0=3Dffffff9c a1=3D7ffc2c117daa a2=3D0 a3=3D0 items=
=3D0 ppid=3D4835
pid=3D4836 auid=3D4294967295 uid=3D0 gid=3D0 euid=3D0 suid=3D0 fsuid=3D0 eg=
id=3D0 sgid=3D0
fsgid=3D0 tty=3D(none) ses=3D4294967295 comm=3D"kexec" exe=3D&quo=
t;/usr/sbin/kexec"
subj=3Dsystem_u:system_r:kdump_t:s0 key=3D(null)
        type=3DAVC msg=3Daudit(1690467975.032:136): avc:  denied  { read } =
for=20
pid=3D4836 comm=3D"kexec" name=3D"kernel" dev=3D"s=
da3" ino=3D48130
scontext=3Dsystem_u:system_r:kdump_t:s0
tcontext=3Dsystem_u:object_r:kdump_var_lib_t:s0 tclass=3Dlnk_file permissiv=
e=3D0

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

You are on the CC list for the bug.

=

--16904690411.8BcF951.29412--

summary: [SELinux] <topic>


ebKit/537.36
(KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36
Build Identifier:=20

Cannot create or import vpnc VPN connections in NetworkManager.  The VPN
creation form comes up normally, prefilled with information if importing a
configuration, but the save button is always grayed out.

Reproducible: Always

Steps to Reproduce:
1. Create or import a vpnc VPN configuration in Network Manager
2. Attempt to save the configuration
3.
Actual Results:=20=20
Save button is grayed out preventing saving of the created or imported
configuration.

Expected Results:=20=20
Save button should be active, allowing the configuration to be saved.

Able to work around the problem by replacing the NetworkManager-vpnc and
NetworkManger-vpnc-gnome packages by replacing them with the older packages
from Leap 15.4.  The save button works as expected in those versions.

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

You are on the CC list for the bug.

=

--16905681051.c01Bf.31939--


--16907600680.17C9.786
Date: Sun, 30 Jul 2023 23:34:28 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1213790
           Summary: Application tab in virt-manager is collapsed, therefore I can't read anything.
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: chamezard-at-outlook.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 868517
  --> https://bugzilla.suse.com/attachment.cgi?id=3D868517&action=3Dedit
This shows virt-manager with OS Information, it's detect applications
suscesfully, but it's collapsed and therefore not expandable by any way.

I installed Virt-Manager and libguestfs. I then enabled "Enable libguestfs
introspection" in Virt-Manager Settings. This successfully detected the
operating system and applications. However, the "Applications" tab remains
non-expandable and non-modifiable. I believe this is a package error that c=
an
only be fixed by recompiling. Thank you for looking into this error and fix=
ing
it.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16907600680.17C9.786
Date: Sun, 30 Jul 2023 23:34:28 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1213790

          Summary
          Application tab in virt-manager is collapsed, therefore I can=
't read anything.

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Virtualization:Tools

          Assignee
          virt-bugs@suse.de

          Reporter
          chamezard@outlook.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 868517 [details]
This shows virt-manager with OS Information, it's detect applications
suscesfully, but it's collapsed and therefore not expandable by any way.

I installed Virt-Manager and libguestfs. I then enabled "Enable libgue=
stfs
introspection" in Virt-Manager Settings. This successfully detected the
operating system and applications. However, the "Applications" ta=
b remains
non-expandable and non-modifiable. I believe this is a package error that c=
an
only be fixed by recompiling. Thank you for looking into this error and fix=
ing
it.

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

You are on the CC list for the bug.

=

--16907600680.17C9.786--


--16908146871.e75f.2178
Date: Mon, 31 Jul 2023 14:44:47 +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=3D1213822

            Bug ID: 1213822
           Summary: invalid grub.cfg created with INITRD_IN_POSTTRANS=3D1
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: martin.wilck-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Invalid boot entry is generated with latest TW update and INITRD_IN_POSTTRA=
NS=3D1
set:

        echo    'Loading Linux 6.4.6-1-default ...'
        linux   /boot/vmlinuz-6.4.6-1-default root=3D/dev/sda7
/dev/sda5  ${extra_cmdline} sysrq_always_enabled panic=3D100 ignore_loglevel
unknown_nmi_panic resume=3D/dev/sda6 crashkernel=3D128M@256M showopts

The root device in question is a btrfs device with two members, where
grub2-probe prints this:

# grub2-probe --target=3Ddevice /
/dev/sda7
/dev/sda5

The issue happened because the update transaction comprised both a grub2 up=
date
and a kernel-default update. With INITRD_IN_POSTTRANS=3D1, if the posttrans
script of grub2-x86_64-efi is executed before the posttrans script of
kernel-default, the initrd will not exist at the time grub2-mkconfig is run,
and the following code from /etc/grub.d/10_linux will be executed:

  if test -z "${initramfs}" && test -z "${initrd_real}" ; then
    # "UUID=3D" and "ZFS=3D" magic is parsed by initrd or initramfs.  Since=
 there's
    # no initrd or builtin initramfs, it can't work here.
    if [ "x${GRUB_DEVICE_PARTUUID}" =3D "x" ] \
        || [ "x${GRUB_DISABLE_LINUX_PARTUUID}" =3D "xtrue" ]; then

        linux_root_device_thisversion=3D${GRUB_DEVICE}
    else
        linux_root_device_thisversion=3DPARTUUID=3D${GRUB_DEVICE_PARTUUID}
    fi
  fi

This will cause the wrong grub.cfg entry shown above. The script assumes th=
at
if no initrd exists at the time it is running, there will be none later,
either.

This assumption is arguably wrong under SUSE and openSUSE, where we always =
have
an initrd =E2=80=94 it would be smarter to assume that if no initrd exists,=
 it will be
created later. Also, it's very questionable to create a syntactically wrong
boot entry rather than a (possibly) unparseable UUID=3D entry.

The initramfs is created later in the installation process, when the posttr=
ans
script of kernel-default is run; but that won't cause the grub.cfg file to =
be
regenerated.

We need to make sure that grub2-mkconfig is run after initrd creation.
This needs to be fixed in suse-module-tools.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16908146871.e75f.2178
Date: Mon, 31 Jul 2023 14:44:47 +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
          1213822

          Summary
          invalid grub.cfg created with INITRD_IN_POSTTRANS=3D1

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          martin.wilck@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Invalid boot entry is generated with latest TW update and IN=
ITRD_IN_POSTTRANS=3D1
set:

        echo    'Loading Linux 6.4.6-1-default ...'
        linux   /boot/vmlinuz-6.4.6-1-default root=3D/dev/sda7
/dev/sda5  ${extra_cmdline} sysrq_always_enabled panic=3D100 ignore_loglevel
unknown_nmi_panic resume=3D/dev/sda6 crashkernel=3D128M@256M showopts

The root device in question is a btrfs device with two members, where
grub2-probe prints this:

# grub2-probe --target=3Ddevice /
/dev/sda7
/dev/sda5

The issue happened because the update transaction comprised both a grub2 up=
date
and a kernel-default update. With INITRD_IN_POSTTRANS=3D1, if the posttrans
script of grub2-x86_64-efi is executed before the posttrans script of
kernel-default, the initrd will not exist at the time grub2-mkconfig is run,
and the following code from /etc/grub.d/10_linux will be executed:

  if test -z "${initramfs}" && test -z "${initrd_rea=
l}" ; then
    # "UUID=3D" and "ZFS=3D" magic is parsed by initrd =
or initramfs.  Since there's
    # no initrd or builtin initramfs, it can't work here.
    if [ "x${GRUB_DEVICE_PARTUUID}" =3D "x" ] \
        || [ "x${GRUB_DISABLE_LINUX_PARTUUID}" =3D "xtrue&qu=
ot; ]; then

        linux_root_device_thisversion=3D${GRUB_DEVICE}
    else
        linux_root_device_thisversion=3DPARTUUID=3D${GRUB_DEVICE_PARTUUID}
    fi
  fi

This will cause the wrong grub.cfg entry shown above. The script assumes th=
at
if no initrd exists at the time it is running, there will be none later,
either.

This assumption is arguably wrong under SUSE and openSUSE, where we always =
have
an initrd =E2=80=94 it would be smarter to assume that if no initrd exists,=
 it will be
created later. Also, it's very questionable to create a syntactically wrong
boot entry rather than a (possibly) unparseable UUID=3D entry.

The initramfs is created later in the installation process, when the posttr=
ans
script of kernel-default is run; but that won't cause the grub.cfg file to =
be
regenerated.

We need to make sure that grub2-mkconfig is run after initrd creation.
This needs to be fixed in suse-module-tools.

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

You are on the CC list for the bug.

=

--16908146871.e75f.2178--


--16908231175.F8FB23Ee5.2402
Date: Mon, 31 Jul 2023 17:05:17 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1213829
           Summary: [kublet v1.27.4] `/usr/bin/kubelet` contains not what it should
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Containers
          Assignee: containers-bugowner-at-suse.de
          Reporter: eich-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: Development
           Blocker: ---

The wrapper script `/usr/bin/kubelet` contains script code unrelated to it's
task and without proper file magic see:

https://build.opensuse.org/package/view_file/openSUSE:Factory/kubernetes1.2=
7/kubelet.sh?expand=3D1)=20
- it rather looks like a copy of genmanpages.sh - a script that's used duri=
ng
package build.

AFAIKT, this has been broken since the advent of kubernetes 1.26.

Version 1.25 still contains what one would expect.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16908231175.F8FB23Ee5.2402
Date: Mon, 31 Jul 2023 17:05:17 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          <a class=3D"bz_bug_link=20
          bz_status_NEW "
   title=3D"NEW - [kublet v1.27.4] `/usr/bin/kubelet` contains not what it =
should"
   href=3D"https://bugzilla.suse.com/show_bug.cgi?id=3D1213829">1213829

          Summary
          [kublet v1.27.4] `/usr/bin/kubelet` contains not what it shou=
ld

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          All

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Containers

          Assignee
          containers-bugowner@suse.de

          Reporter
          eich@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          Development

          Blocker
          ---

The wrapper script `/usr/bin/kubelet` contains script code u=
nrelated to it's
task and without proper file magic see:

https://build.opensuse.org/package/view=
_file/openSUSE:Factory/kubernetes1.27/kubelet.sh?expand=3D1)=20
- it rather looks like a copy of genmanpages.sh - a script that's used duri=
ng
package build.

AFAIKT, this has been broken since the advent of kubernetes 1.26.

Version 1.25 still contains what one would expect.

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

You are on the CC list for the bug.

=

--16908231175.F8FB23Ee5.2402--


--16909420170.88aC185.4537
Date: Wed, 2 Aug 2023 02:06:57 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1213884
           Summary: Rebase patches on accountsservice as-fate318433-prevent-same-account-multi-logins.patch.
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: gnome-bugs-at-suse.de
          Reporter: yfjiang-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

The patch needs some alignment to the latest accountsservice (referred to
https://build.opensuse.org/package/live_build_log/home:yfjiang:test:gnome45=
/accountsservice/SLE_15_SP5/x86_64):

[   26s] + echo 'Patch #1000
(as-fate318433-prevent-same-account-multi-logins.patch):'
[   26s] Patch #1000 (as-fate318433-prevent-same-account-multi-logins.patch=
):
[   26s] + /usr/bin/patch --no-backup-if-mismatch -p1 --fuzz=3D0
[   26s] patching file src/libaccountsservice/act-user.c
[   26s] patching file src/libaccountsservice/act-user.h
[   26s] Hunk #1 FAILED at 61.
[   26s] 1 out of 1 hunk FAILED


--16909974001.715c2FBbA.6201
Date: Wed, 2 Aug 2023 17:30:00 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1213915
           Summary: Kernel panic - illegal instruction (4) at 7fffb6a4f874 nip 7fffb6a4f874 lr 7fffb6a4380c code 1 in ld64.so.2
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: PowerPC-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: jrivrain-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 868604
  --> https://bugzilla.suse.com/attachment.cgi?id=3D868604&action=3Dedit
serial output

All ppc64 Tumbleweed tests in Openqa are failing right now with a kernel pa=
nic.
All the workers are on power8 cpus, this does not happen on a qemu emulated
power9 cpu.

Example of failing test:

https://openqa.opensuse.org/tests/3476697

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

--16909974001.715c2FBbA.6201
Date: Wed, 2 Aug 2023 17:30:00 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1213915

          Summary
          Kernel panic - illegal instruction (4) at 7fffb6a4f874 nip 7f=
ffb6a4f874 lr 7fffb6a4380c code 1 in ld64.so.2

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          PowerPC-64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          jrivrain@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 868604 [details]
serial output

All ppc64 Tumbleweed tests in Openqa are failing right now with a kernel pa=
nic.
All the workers are on power8 cpus, this does not happen on a qemu emulated
power9 cpu.

Example of failing test:

https://openqa.opensu=
se.org/tests/3476697

See attached serial output.

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

You are on the CC list for the bug.

=

--16909974001.715c2FBbA.6201--


--16911394970.EBfDfC.10031
Date: Fri, 4 Aug 2023 08:58:17 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1213976
           Summary: Missing dependency from glu-devel to the package providing gl.h
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: gfx-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: gfx-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I have seen a few build fails in Factory that all boiled down to:

[   38s] /usr/include/GL/glu.h:34:10: fatal error: GL/gl.h: No such file or
directory

i.e. the consumer includes glu.h - but then glu.h (glu-devel) does not brin=
g in
all the deps it needs to be functional, namely it misses a dependency on
Mesa-libGL-devel

This seems like a bug in glu-devel (pkgconfig(gl) would probably be the best
dep to be added)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16911394970.EBfDfC.10031
Date: Fri, 4 Aug 2023 08:58:17 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1213976

          Summary
          Missing dependency from glu-devel to the package providing gl=
.h

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X.Org

          Assignee
          gfx-bugs@suse.de

          Reporter
          dimstar@opensuse.org

          QA Contact
          gfx-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I have seen a few build fails in Factory that all boiled dow=
n to:

[   38s] /usr/include/GL/glu.h:34:10: fatal error: GL/gl.h: No such file or
directory

i.e. the consumer includes glu.h - but then glu.h (glu-devel) does not brin=
g in
all the deps it needs to be functional, namely it misses a dependency on
Mesa-libGL-devel

This seems like a bug in glu-devel (pkgconfig(gl) would probably be the best
dep to be added)

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

You are on the CC list for the bug.

=

--16911394970.EBfDfC.10031--


--16912069510.9EB6.11708
Date: Sat, 5 Aug 2023 03:42: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=3D1214008

            Bug ID: 1214008
           Summary: emacs: after upgrade to 29.1 can't start
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: david.alpha.fox-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

After the rolling upgrade.
The emacs is upgraded to 29.1 and it can't be started.
And when I run it in the terminal=20
The result is

Loading loadup.el (source)...
Dump mode: nil
Using load-path (/usr/share/emacs/29.1/site-lisp /usr/share/emacs/site-lisp
/usr/share/emacs/29.1/lisp /usr/share/emacs/29.1/lisp/emacs-lisp
/usr/share/emacs/29.1/lisp/progmodes /usr/share/emacs/29.1/lisp/language
/usr/share/emacs/29.1/lisp/international /usr/share/emacs/29.1/lisp/textmod=
es
/usr/share/emacs/29.1/lisp/vc)
Loading emacs-lisp/debug-early...
Symbol's function definition is void: file-name-sans-extension

and it refuse to start.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16912069510.9EB6.11708
Date: Sat, 5 Aug 2023 03:42: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
          1214008

          Summary
          emacs: after upgrade to 29.1 can't start

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          david.alpha.fox@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

After the rolling upgrade.
The emacs is upgraded to 29.1 and it can't be started.
And when I run it in the terminal=20
The result is

Loading loadup.el (source)...
Dump mode: nil
Using load-path (/usr/share/emacs/29.1/site-lisp /usr/share/emacs/site-lisp
/usr/share/emacs/29.1/lisp /usr/share/emacs/29.1/lisp/emacs-lisp
/usr/share/emacs/29.1/lisp/progmodes /usr/share/emacs/29.1/lisp/language
/usr/share/emacs/29.1/lisp/international /usr/share/emacs/29.1/lisp/textmod=
es
/usr/share/emacs/29.1/lisp/vc)
Loading emacs-lisp/debug-early...
Symbol's function definition is void: file-name-sans-extension

and it refuse to start.

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

You are on the CC list for the bug.

=

--16912069510.9EB6.11708--


--16911831560.1EEa61370.11564
Date: Fri, 4 Aug 2023 21:05: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=3D1214003

            Bug ID: 1214003
           Summary: Chromium crashed on page loading since last update
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: egor.kuznetsov.26-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

OS: openSUSE Tumbleweed 20230803
Chromium version: 115.0.5790.170-1.1
Codecs (if necessary): Packman repo latest

Since last update Chromium instantly crashed when I type something in search
bar and press Enter. Two second browser try to load page normally, but afte=
r a
couple of seconds freezed and crashed. I try to run it from console to debug
and see stacktrace, that maybe helpful:=20
https://paste.opensuse.org/pastes/7c467c7afe54
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16911831560.1EEa61370.11564
Date: Fri, 4 Aug 2023 21:05: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
          1214003

          Summary
          Chromium crashed on page loading since last update

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          egor.kuznetsov.26@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

OS: openSUSE Tumbleweed 20230803
Chromium version: 115.0.5790.170-1.1
Codecs (if necessary): Packman repo latest

Since last update Chromium instantly crashed when I type something in search
bar and press Enter. Two second browser try to load page normally, but afte=
r a
couple of seconds freezed and crashed. I try to run it from console to debug
and see stacktrace, that maybe helpful:=20
https://paste.op=
ensuse.org/pastes/7c467c7afe54

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

You are on the CC list for the bug.

=

--16911831560.1EEa61370.11564--


--16914833643.FdebB2f.15284
Date: Tue, 8 Aug 2023 08:29:24 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1214060
           Summary: html2ps conversion fails with perl >=3D 5.26
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: christophe-at-krop.fr
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Affected: Tumbleweed, Leap, SLE 15

html2ps -f <file> fails with this error:

Unimplemented: POSIX::tmpnam(): use File::Temp instead at /usr/bin/html2ps =
line
498.

We're apparently having an old version in openSUSE (some distro have 1.0b7)=
 and
it needs patching.

Debian has a collection of improvements and fixes:
https://salsa.debian.org/debian/html2ps/-/tree/master/debian/patches

The important one for this report is perl-deprecation.patch
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16914833643.FdebB2f.15284
Date: Tue, 8 Aug 2023 08:29:24 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1214060

          Summary
          html2ps conversion fails with perl >=3D 5.26

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          christophe@krop.fr

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Affected: Tumbleweed, Leap, SLE 15

html2ps -f <file> fails with this error:

Unimplemented: POSIX::tmpnam(): use File::Temp instead at /usr/bin/html2ps =
line
498.

We're apparently having an old version in openSUSE (some distro have 1.0b7)=
 and
it needs patching.

Debian has a collection of improvements and fixes:
https://salsa.debian.org/debian/html2ps/-/tree/master/debian/patches<=
/a>

The important one for this report is perl-deprecation.patch

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

You are on the CC list for the bug.

=

--16914833643.FdebB2f.15284--


--16915548192.ADa0.17281
Date: Wed, 9 Aug 2023 04:20:19 +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=3D1214093

            Bug ID: 1214093
           Summary: openSUSE-SLE-15.4-2023-3233 fails to install due to missing libwebkit2gtk3 =3D 2.40.5
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Maintenance
          Assignee: maintenance-at-opensuse.org
          Reporter: arvidjaar-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

bor@10:~> sudo zypper patch
[sudo] password for root:=20
Loading repository data...
Reading installed packages...
Patch 'openSUSE-SLE-15.4-2023-3146-1' is optional. Use 'zypper in
patch:openSUSE-SLE-15.4-2023-3146' to install it, or '--with-optional' to
include all optional patches.
Resolving package dependencies...

Problem: nothing provides 'libwebkit2gtk3 =3D 2.40.5' needed by the to be
installed libwebkit2gtk3-lang-2.40.5-150200.78.1.noarch
 Solution 1: deinstallation of libwebkit2gtk3-lang-2.38.6-150200.75.2.noarch
 Solution 2: do not install patch:openSUSE-SLE-15.4-2023-3233-1.noarch
 Solution 3: break libwebkit2gtk3-lang-2.40.5-150200.78.1.noarch by ignoring
some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):=20

Normally libwebkit2gtk3 is provided by=20

bor@10:~> zypper se --provides -x 'libwebkit2gtk3'
Loading repository data...
Reading installed packages...

S | Name                 | Summary                                     | Ty=
pe
--+----------------------+---------------------------------------------+---=
-----
i | libwebkit2gtk-4_0-37 | Library for rendering web content, GTK+ P-> |
package
  | libwebkit2gtk-4_1-0  | Library for rendering web content, GTK+ P-> |
package
bor@10:~>
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16915548192.ADa0.17281
Date: Wed, 9 Aug 2023 04:20:19 +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
          1214093

          Summary
          openSUSE-SLE-15.4-2023-3233 fails to install due to missing l=
ibwebkit2gtk3 =3D 2.40.5

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.4

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Maintenance

          Assignee
          maintenance@opensuse.org

          Reporter
          arvidjaar@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

bor@10:~> sudo zypper patch
[sudo] password for root:=20
Loading repository data...
Reading installed packages...
Patch 'openSUSE-SLE-15.4-2023-3146-1' is optional. Use 'zypper in
patch:openSUSE-SLE-15.4-2023-3146' to install it, or '--with-optional' to
include all optional patches.
Resolving package dependencies...

Problem: nothing provides 'libwebkit2gtk3 =3D 2.40.5' needed by the to be
installed libwebkit2gtk3-lang-2.40.5-150200.78.1.noarch
 Solution 1: deinstallation of libwebkit2gtk3-lang-2.38.6-150200.75.2.noarch
 Solution 2: do not install patch:openSUSE-SLE-15.4-2023-3233-1.noarch
 Solution 3: break libwebkit2gtk3-lang-2.40.5-150200.78.1.noarch by ignoring
some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):=20

Normally libwebkit2gtk3 is provided by=20

bor@10:~> zypper se --provides -x 'libwebkit2gtk3'
Loading repository data...
Reading installed packages...

S | Name                 | Summary                                     | Ty=
pe
--+----------------------+---------------------------------------------+---=
-----
i | libwebkit2gtk-4_0-37 | Library for rendering web content, GTK+ P-> |
package
  | libwebkit2gtk-4_1-0  | Library for rendering web content, GTK+ P-> |
package
bor@10:~>

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

You are on the CC list for the bug.

=

--16915548192.ADa0.17281--


--16915666770.e3BCFE.17413
Date: Wed, 9 Aug 2023 07:37:57 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1214101
           Summary: AUDIT-0: deepin-api: Please keep the old com.deepin.* in whitelist for a while
    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: hillwoodroc-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

According to boo#1211376, com.deepin.* will be renamed to org.deepin.*. But=
 the
new version of deepin-api still is testing in X11:Deepin:Factory. We need to
keep the old version in the com.deepin.* for a while.=20

[  124s] deepin-api.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/usr/share/dbus-1/system-services/com.deepin.api.Device.service (sha256 file
digest default
filter:613bfd2b5d6373ecaa519a1c8a4d2351106cb5986cb9acb04f13df1ba9aef7d6 she=
ll
filter:613bfd2b5d6373ecaa519a1c8a4d2351106cb5986cb9acb04f13df1ba9aef7d6 xml
filter:<failed-to-calculate>)
[  124s] deepin-api.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/usr/share/dbus-1/system.d/com.deepin.api.Device.conf (sha256 file digest
default filter:e3effdf083da39eaddce7997c2c4c16f8268c9b9579dd30141f4c2f10a99=
2a4d
shell filter:3822da73f18676a6ddaa980449bf4051e1c9d234591a4222448c69830adcbd=
71
xml filter:36ecf94f509650ce97381a3af592319a124bb8c70e4b664a84fd2a2fb971c9f5)
[  124s] deepin-api.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/usr/share/dbus-1/system.d/com.deepin.api.SoundThemePlayer.conf (sha256 file
digest default
filter:93a5dbb3545ec99317914663407d8608046805a9b0718c592cd19ff47bcc9481 she=
ll
filter:d4ec55c10193024a44eef60c9f08a581a45c377e954293bcad3b0a8fcb94c155 xml
filter:0e6254e6d3905934d3fa5db5e58815f32fcea5dbac93dbed2a9e15214c8f10eb)
[  124s] deepin-api.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/usr/share/dbus-1/system-services/com.deepin.api.SoundThemePlayer.service
(sha256 file digest default
filter:f906b7c664c7e0f3cf740cad1b63ed9ff668e1ac5233ba5c9a9734b6425b3763 she=
ll
filter:f906b7c664c7e0f3cf740cad1b63ed9ff668e1ac5233ba5c9a9734b6425b3763 xml
filter:<failed-to-calculate>)
[  124s] deepin-api.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/usr/share/dbus-1/system-services/com.deepin.api.LocaleHelper.service (sha2=
56
file digest default
filter:c4896ab305c8dff7fa6cfeef2ba194aeec85e649c3d72d3afaa16cc0ac7b7b55 she=
ll
filter:c4896ab305c8dff7fa6cfeef2ba194aeec85e649c3d72d3afaa16cc0ac7b7b55 xml
filter:<failed-to-calculate>)
[  124s] deepin-api.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/usr/share/dbus-1/system.d/com.deepin.api.LocaleHelper.conf (sha256 file di=
gest
default filter:7f339a4292fbd17478ff455471743c5a92f72183ca3c1c884f62e28a806a=
e893
shell
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16915666770.e3BCFE.17413
Date: Wed, 9 Aug 2023 07:37:57 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1214101

          Summary
          AUDIT-0: deepin-api: Please keep the old com.deepin.* in whit=
elist for a while

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

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

According to boo#1211376, com.deepin.* will be renamed to org.de=
epin.*. But the
new version of deepin-api still is testing in X11:Deepin:Factory. We need to
keep the old version in the com.deepin.* for a while.=20

[  124s] deepin-api.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/usr/share/dbus-1/system-services/com.deepin.api.Device.service (sha256 file
digest default
filter:613bfd2b5d6373ecaa519a1c8a4d2351106cb5986cb9acb04f13df1ba9aef7d6 she=
ll
filter:613bfd2b5d6373ecaa519a1c8a4d2351106cb5986cb9acb04f13df1ba9aef7d6 xml
filter:<failed-to-calculate>)
[  124s] deepin-api.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/usr/share/dbus-1/system.d/com.deepin.api.Device.conf (sha256 file digest
default filter:e3effdf083da39eaddce7997c2c4c16f8268c9b9579dd30141f4c2f10a99=
2a4d
shell filter:3822da73f18676a6ddaa980449bf4051e1c9d234591a4222448c69830adcbd=
71
xml filter:36ecf94f509650ce97381a3af592319a124bb8c70e4b664a84fd2a2fb971c9f5)
[  124s] deepin-api.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/usr/share/dbus-1/system.d/com.deepin.api.SoundThemePlayer.conf (sha256 file
digest default
filter:93a5dbb3545ec99317914663407d8608046805a9b0718c592cd19ff47bcc9481 she=
ll
filter:d4ec55c10193024a44eef60c9f08a581a45c377e954293bcad3b0a8fcb94c155 xml
filter:0e6254e6d3905934d3fa5db5e58815f32fcea5dbac93dbed2a9e15214c8f10eb)
[  124s] deepin-api.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/usr/share/dbus-1/system-services/com.deepin.api.SoundThemePlayer.service
(sha256 file digest default
filter:f906b7c664c7e0f3cf740cad1b63ed9ff668e1ac5233ba5c9a9734b6425b3763 she=
ll
filter:f906b7c664c7e0f3cf740cad1b63ed9ff668e1ac5233ba5c9a9734b6425b3763 xml
filter:<failed-to-calculate>)
[  124s] deepin-api.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/usr/share/dbus-1/system-services/com.deepin.api.LocaleHelper.service (sha2=
56
file digest default
filter:c4896ab305c8dff7fa6cfeef2ba194aeec85e649c3d72d3afaa16cc0ac7b7b55 she=
ll
filter:c4896ab305c8dff7fa6cfeef2ba194aeec85e649c3d72d3afaa16cc0ac7b7b55 xml
filter:<failed-to-calculate>)
[  124s] deepin-api.x86_64: E: dbus-file-unauthorized (Badness: 10000)
/usr/share/dbus-1/system.d/com.deepin.api.LocaleHelper.conf (sha256 file di=
gest
default filter:7f339a4292fbd17478ff455471743c5a92f72183ca3c1c884f62e28a806a=
e893
shell

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

You are on the CC list for the bug.

=

--16915666770.e3BCFE.17413--


--16917788670.8c8AE.4857
Date: Fri, 11 Aug 2023 18:34: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=3D1214205

            Bug ID: 1214205
           Summary: python-pynput and %global pythons %{primary_python}
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Python
          Assignee: python-maintainers-at-suse.com
          Reporter: mcepl-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

This is just evil. Either the packager meant to make the package just for
python3- and then it should do it, or this doesn=E2=80=99t make any sense.

https://build.opensuse.org/package/view_file/openSUSE:Factory/python-pynput=
/python-pynput.spec?expand=3D1
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16917788670.8c8AE.4857
Date: Fri, 11 Aug 2023 18:34: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
          1214205

          Summary
          python-pynput and %global pythons %{primary_python}

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Python

          Assignee
          python-maintainers@suse.com

          Reporter
          mcepl@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

This is just evil. Either the packager meant to make the pac=
kage just for
python3- and then it should do it, or this doesn=E2=80=99t make any sense.

https://build.opensuse.org/packa=
ge/view_file/openSUSE:Factory/python-pynput/python-pynput.spec?expand=3D1</=
a>

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

You are on the CC list for the bug.

=

--16917788670.8c8AE.4857--


--16920012082.7FCdEF.6241
Date: Mon, 14 Aug 2023 08:20:08 +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=3D1214237

            Bug ID: 1214237
           Summary: VUL-0: CVE-2023-40274: zola: directory traversal when using the "serve" subcommand
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
               URL: https://smash.suse.de/issue/375225/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: socvirnyl.estela-at-gmail.com
          Reporter: carlos.lopez-at-suse.com
        QA Contact: security-team-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

CVE-2023-40274

An issue was discovered in zola 0.13.0 through 0.17.2. The custom
implementation
of a web server, available via the "zola serve" command, allows directory
traversal. The handle_request function, used by the server to process HTTP
requests, does not account for sequences of special path control characters
(../) in the URL when serving a file, which allows one to escape the webroo=
t of
the server and read arbitrary files from the filesystem.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2023-40274
https://www.cve.org/CVERecord?id=3DCVE-2023-40274
https://github.com/getzola/zola/issues/2257
https://github.com/getzola/zola/pull/2258
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16920012082.7FCdEF.6241
Date: Mon, 14 Aug 2023 08:20:08 +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
          1214237

          Summary
          VUL-0: CVE-2023-40274: zola: directory traversal when using t=
he "serve" subcommand

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.4

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          socvirnyl.estela@gmail.com

          Reporter
          carlos.lopez@suse.com

          QA Contact
          security-team@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

CVE-2023-40274

An issue was discovered in zola 0.13.0 through 0.17.2. The custom
implementation
of a web server, available via the "zola serve" command, allows d=
irectory
traversal. The handle_request function, used by the server to process HTTP
requests, does not account for sequences of special path control characters
(../) in the URL when serving a file, which allows one to escape the webroo=
t of
the server and read arbitrary files from the filesystem.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2023-40274
https://www.c=
ve.org/CVERecord?id=3DCVE-2023-40274
https://github.com/=
getzola/zola/issues/2257
https://github.com/ge=
tzola/zola/pull/2258

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

You are on the CC list for the bug.

=

--16920012082.7FCdEF.6241--


body:
--16920154321.5160.6742
Date: Mon, 14 Aug 2023 12:17:12 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1214255
           Summary: Cava is not working
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: satishlakkimsetti-at-outlook.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 868789
  --> https://bugzilla.suse.com/attachment.cgi?id=3D868789&action=3Dedit
Here is the screenshot. Even it is not working after reinstall.

The "cava" package is not working. The package used to work fine but after
updating the error "Error loading config. cava was built without 'pipewire'
input support". I didn't have this kind of error in the before snapshots. T=
he
latest snapshot is causing the issue.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16920154321.5160.6742
Date: Mon, 14 Aug 2023 12:17:12 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1214255

          Summary
          Cava is not working

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          satishlakkimsetti@outlook.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 868789 [details]
Here is the screenshot. Even it is not working after reinstall.

The "cava" package is not working. The package used to work fine =
but after
updating the error "Error loading config. cava was built without 'pipe=
wire'
input support". I didn't have this kind of error in the before snapsho=
ts. The
latest snapshot is causing the issue.

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

You are on the CC list for the bug.

=

--16920154321.5160.6742--

summary: Cava is not working


body:
--16921197712.67DACa80.9056
Date: Tue, 15 Aug 2023 17:16:11 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1214301
           Summary: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 116.0.5845.96
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: Andreas.Stieger-at-gmx.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: gmbr3-at-opensuse.org, m.szczepaniak.000-at-gmail.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

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

CVE-2023-2312: Use after free in Offline
CVE-2023-4349: Use after free in Device Trust Connectors
CVE-2023-4350: Inappropriate implementation in Fullscreen
CVE-2023-4351: Use after free in Network
CVE-2023-4352: Type Confusion in V8
CVE-2023-4353: Heap buffer overflow in ANGLE
CVE-2023-4354: Heap buffer overflow in Skia
CVE-2023-4355: Out of bounds memory access in V8
CVE-2023-4356: Use after free in Audio
CVE-2023-4357: Insufficient validation of untrusted input in XML
CVE-2023-4358: Use after free in DNS
CVE-2023-4359: Inappropriate implementation in App Launcher
CVE-2023-4360: Inappropriate implementation in Color
CVE-2023-4361: Inappropriate implementation in Autofill
CVE-2023-4362: Heap buffer overflow in Mojom IDL
CVE-2023-4363: Inappropriate implementation in WebShare
CVE-2023-4364: Inappropriate implementation in Permission Prompts
CVE-2023-4365: Inappropriate implementation in Fullscreen
CVE-2023-4366: Use after free in Extensions
CVE-2023-4367: Insufficient policy enforcement in Extensions API
CVE-2023-4368: Insufficient policy enforcement in Extensions API
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16921197712.67DACa80.9056
Date: Tue, 15 Aug 2023 17:16:11 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1214301

          Summary
          VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities =
fixed in 116.0.5845.96

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          Andreas.Stieger@gmx.de

          Reporter
          Andreas.Stieger@gmx.de

          QA Contact
          qa-bugs@suse.de

          CC
          gmbr3@opensuse.org, m.szczepaniak.000@gmail.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

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

CVE-2023-2312: Use after free in Offline
CVE-2023-4349: Use after free in Device Trust Connectors
CVE-2023-4350: Inappropriate implementation in Fullscreen
CVE-2023-4351: Use after free in Network
CVE-2023-4352: Type Confusion in V8
CVE-2023-4353: Heap buffer overflow in ANGLE
CVE-2023-4354: Heap buffer overflow in Skia
CVE-2023-4355: Out of bounds memory access in V8
CVE-2023-4356: Use after free in Audio
CVE-2023-4357: Insufficient validation of untrusted input in XML
CVE-2023-4358: Use after free in DNS
CVE-2023-4359: Inappropriate implementation in App Launcher
CVE-2023-4360: Inappropriate implementation in Color
CVE-2023-4361: Inappropriate implementation in Autofill
CVE-2023-4362: Heap buffer overflow in Mojom IDL
CVE-2023-4363: Inappropriate implementation in WebShare
CVE-2023-4364: Inappropriate implementation in Permission Prompts
CVE-2023-4365: Inappropriate implementation in Fullscreen
CVE-2023-4366: Use after free in Extensions
CVE-2023-4367: Insufficient policy enforcement in Extensions API
CVE-2023-4368: Insufficient policy enforcement in Extensions API

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

You are on the CC list for the bug.

=

--16921197712.67DACa80.9056--

pkgs: chromium ungoogled-chromium


body:
--16922643070.Facf1bCE.11230
Date: Thu, 17 Aug 2023 09:25:07 +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=3D1214354

            Bug ID: 1214354
           Summary: Snapshot 20230813 installs python 3.10 again, although no python 3.10 is installed
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Python
          Assignee: python-maintainers-at-suse.com
          Reporter: axel.braun-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Following up on
https://lists.opensuse.org/archives/list/factory-at-lists.opensuse.org/thread/=
WIORVWUEIGKG3KYQUTTTOO5IE3NWANEE/
python 3.10 should be installed, although no python 3.10 is on the system.

Seems to be an issue in python-jupyterlab or zypper that needs a resolution
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16922643070.Facf1bCE.11230
Date: Thu, 17 Aug 2023 09:25:07 +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
          1214354

          Summary
          Snapshot 20230813 installs python 3.10 again, although no pyt=
hon 3.10 is installed

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Python

          Assignee
          python-maintainers@suse.com

          Reporter
          axel.braun@gmx.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Following up on
https://lists.opensuse.or=
g/archives/list/factory@lists.opensuse.org/thread/WIORVWUEIGKG3KYQUTTTO=
O5IE3NWANEE/
python 3.10 should be installed, although no python 3.10 is on the system.

Seems to be an issue in python-jupyterlab or zypper that needs a resolution=

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

You are on the CC list for the bug.

=

--16922643070.Facf1bCE.11230--

pkgs: python-ipyevents python-ipyleaflet python-ipympl python-ipysheet python-ipyvolume python-ipyvue python-ipyvuetify python-ipywebrtc python-jupyter-lsp python-nbclassic python-nbconvert python-nbdime python-notebook-shim python-sidecar


--16922721551.dFbEBc4Ad.11494
Date: Thu, 17 Aug 2023 11:35:55 +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=3D1214360

            Bug ID: 1214360
           Summary: suse-module-tools: kmp-install still needed? (it's perl)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: martin.wilck-at-suse.com
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1170066
  Target Milestone: ---
          Found By: ---
           Blocker: ---

kmp-install in suse-module-tools is one of very few scripts left in a minim=
al
system that require Perl. Not sure it's worth rewriting in some other langu=
age.
Is the tool actually still needed all? I didn't even know about it :-)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16922721551.dFbEBc4Ad.11494
Date: Thu, 17 Aug 2023 11:35:55 +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
          1214360

          Summary
          suse-module-tools: kmp-install still needed? (it's perl)

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          martin.wilck@suse.com

          Reporter
          lnussel@suse.com

          QA Contact
          qa-bugs@suse.de

          Blocks
          1170066

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

kmp-install in suse-module-tools is one of very few scripts =
left in a minimal
system that require Perl. Not sure it's worth rewriting in some other langu=
age.
Is the tool actually still needed all? I didn't even know about it :-)

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

You are on the CC list for the bug.

=

--16922721551.dFbEBc4Ad.11494--


body:
--16923513634.0DBa427Bf.12792
Date: Fri, 18 Aug 2023 09:36:03 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1214391
           Summary: vbox:kmp fails with kernel 6.4.10
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Other
          Assignee: Larry.Finger-at-gmail.com
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: llrainey15-at-gmail.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

It looks like since commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?=
id=3D3fe617ccafd6f5bb33c2391d6f4eeb41c1fd0151

(present in 6.4.10), virtualbox needs to include net/gso.h too:
> vboxnetflt/linux/VBoxNetFlt-linux.c:1577:40: error: implicit declaration =
of function 'skb_gso_segment'; did you mean 'skb_gso_reset'?

in:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:=
K/virtualbox:kmp/standard/x86_64

Can you take care of it?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16923513634.0DBa427Bf.12792
Date: Fri, 18 Aug 2023 09:36:03 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1214391

          Summary
          vbox:kmp fails with kernel 6.4.10

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Virtualization:Other

          Assignee
          Larry.Finger@gmail.com

          Reporter
          jslaby@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          llrainey15@gmail.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

It looks like since commit:
https://git.kerne=
l.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3D3fe617ccafd6=
f5bb33c2391d6f4eeb41c1fd0151

(present in 6.4.10), virtualbox needs to include net/gso.h too:
> vboxnetflt/linux/VBoxNetFlt-linux.c:1577:40: err=
or: implicit declaration of function 'skb_gso_segment'; did you mean 'skb_g=
so_reset'?

in:
https://build.opensuse.org/pac=
kage/live_build_log/openSUSE:Factory:Staging:K/virtualbox:kmp/standard/x86_=
64

Can you take care of it?

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

You are on the CC list for the bug.

=

--16923513634.0DBa427Bf.12792--

summary: vbox:kmp fails with kernel 6.4.10


body:
--16925752670.900c05.14331
Date: Sun, 20 Aug 2023 23:47:47 +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=3D1214420

            Bug ID: 1214420
           Summary: [LXQt]compton-conf / picom
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LXQt
          Assignee: mvetter-at-suse.com
          Reporter: psi089-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Problem: After installation picom did not start because it lacked a config
file.

lxqt-config starts compton-conf which writes to .config/compton.conf but pi=
com
is used as compositor and expects to read from .config/picom.conf

Further: on manual startup picom complains about deprecated config entries =
that
got written by the currently used tool.

What is the solution? For now I just softlinked picom.conf to compton.conf,=
 but
it looks like some clean fix is needed and to make it work out of the box.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16925752670.900c05.14331
Date: Sun, 20 Aug 2023 23:47:47 +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
          1214420

          Summary
          [LXQt]compton-conf / picom

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          LXQt

          Assignee
          mvetter@suse.com

          Reporter
          psi089@gmx.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Problem: After installation picom did not start because it l=
acked a config
file.

lxqt-config starts compton-conf which writes to .config/compton.conf but pi=
com
is used as compositor and expects to read from .config/picom.conf

Further: on manual startup picom complains about deprecated config entries =
that
got written by the currently used tool.

What is the solution? For now I just softlinked picom.conf to compton.conf,=
 but
it looks like some clean fix is needed and to make it work out of the box.<=
/pre>

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

You are on the CC list for the bug.

=

--16925752670.900c05.14331--

summary: [LXQt]compton-conf / picom