--1679857017.fDe4fd21.10158
Date: Sun, 26 Mar 2023 18:56:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1209741

            Bug ID: 1209741
           Summary: pam session keyring creating during KDE GUI login not available to cifscreds
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: jmscdba-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

*** Background Info

Please note that although I am reporting this bug against TW 20230324
the bug actually started occurring with builds created roughly
6 to 9 months ago.

I did not submit earlier because I was having trouble with how to best
document the situation to allow you to easily replicate the bug.

After reading the Linux-PAM System Administrators Guide, I come up with
the following steps to document the bug.

I went with most recent TW build in a VM to replicate the problem so
that you could easily do the same in your debugging, however, the
problem occurs on all of my TW installs on other machines which have
been zypper dup'd for years.

There are NO changes to the newly installed system and it is using
the default configuration for everything.

*** Short description of the problem

Based on my test case research it appears that one of the following
is the source of the problem:

1)  Either pam_keyinit.so is not creating the session keyring during
    login or it is somehow created but does not end up attached
    correctly to the user's GUI login session.

2)  cifscreds is not reading/finding the session keyring

*** Research and Steps to Recreate the problem

Perform new TW build 20230324 installation

    As mentioned above this replicates on my other TW machines which
    have been update for years but I used this as a base so that
    all of the default configuration is in place.

    After installation is completed the rest of the steps are performed
    using my joe user logged into KDE and from a konsole prompt.

keyctl show @u

    Keyring
     725340159 --alswrv   1000 65534  keyring: _uid.1000

keyctl show @s

    Keyring
     900237848 --alswrv   1000 65534  keyring: _uid_ses.1000
     725340159 --alswrv   1000 65534   \_ keyring: _uid.1000

cifscreds add -u joe fileserver

    Warning: you have no persistent session keyring. cifscreds keys will
    not persist after this process exits. See pam_keyinit(8).

Since cifscreds says there is no persistent keyring the credentials do not
exist after cifscrds terminates as shown by the following:

keyctl show @s

    Keyring
     900237848 --alswrv   1000 65534  keyring: _uid_ses.1000
     725340159 --alswrv   1000 65534   \_ keyring: _uid.1000

Based on those results it "appears" that either cifscreds is not finding
the session keyring and therefore that is the problem OR pam_keyinit.so
is somehow not creating a new session keyring ( but it seems to be
creating it based on the above ) or it is creating in a way that is not seen by
the cifscreds program.

Since cifsceds is unable to add the user credentials to the session keyring
and have them persist this means that the user cannot access CIFS shares
which have been mounted with the multiuser mount option.

In testing further I tried the following:

Show starting point keyrings again

    keyctl show @u

        Keyring
         725340159 --alswrv   1000 65534  keyring: _uid.1000

    keyctl show @s

        Keyring
         900237848 --alswrv   1000 65534  keyring: _uid_ses.1000
         725340159 --alswrv   1000 65534   \_ keyring: _uid.1000

Create a new session keyring using:

    keyctl session

        Joined session keyring: 446515518

Show keyring state after creating new one

    keyctl show @u

        Keyring
         725340159 --alswrv   1000 65534  keyring: _uid.1000

    keyctl show @s

        Keyring
         446515518 --alswrv   1000  1000  keyring: _ses

Attempt to add credentials to newly created keyring

    cifscreds add -u joe fileserver

    No warning is displayed and credentials are added to the newly
    created session keyring

    keyctl show @s

        Keyring
         446515518 --alswrv   1000  1000  keyring: _ses
         480791877 ----sw-v   1000  1000   \_ logon: cifs:a:192.168.1.1

User joe can now successfully access the mounted multiuser CIFS shares
using the credentials that it retrieves from session keyring.

Note that I did not include the mount steps ( done as root ) because
they are not part of the problem, as the real issue is with the
session keyring not being available when cifscreds is run.

My initial thought that something was wrong with cifscreds, however,
the following test seems to confirm that the actual problem is with
the PAM configuration and how pam_keyinit.so is creating the session
keyring when logging into the KDE GUI.

To perform this test to demonstrate that:

    Reboot the machine to start clean

    Instead of logging into KDE GUI press Ctrl+Alt+F1 to get a console.

    login

    keyctl show @u

        Keyring
         766463839 --alswrv   1000 65534  keyring: _uid.1000

    keyctl show @s

        Keyring
         576175083 --alswrv   1000  1000  keyring: _ses
         766463839 --alswrv   1000 65534   \_ keyring: _uid.1000

    cifscreds add -u joe fileserver

        No warning is displayed and credentials are successfully added

    keyctl show @u

        Keyring
         766463839 --alswrv   1000 65534  keyring: _uid.1000

    keyctl show @s

        Keyring
         576175083 --alswrv   1000  1000  keyring: _ses
         766463839 --alswrv   1000 65534   \_ keyring: _uid.1000
         673617333 ----sw-v   1000  1000   \_ logon: cifs:a:192.168.1.1

    User joe can now successfully access the mounted multiuser CIFS shares
    using the credentials that it retrieves from session keyring.

Since the session keying and cifscreds work correctly from the tty console
but do NOT when you log into the KDE GUI and do the exact same thing it
would appear that something is wrong with how pam_keyinit is creating
the session keyring and it being available in when logging into the GUI.

I have tried varies other tests to see if I could "fix" the default pam
config to resolve the issue which did not work.

As I final test I tried the following:

    NOTE:

        I understand that we should NOT modify the
        /etc/pam.d/common-*-pc files and I only did this as a test
        to see if it resolved the issue and recognize that
        the real fix is/may be something totally different.

    Modify /etc/pam.d/common-session-pc to add the following to the end

        session optional        pam_keyinit.so revoke force

    reboot

    login to KDE gui

    cifscreds add -u joe fileserver

        No warning is displayed and credentials are successfully added

    User joe can now successfully access the mounted multiuser CIFS shares
    using the credentials that it retrieves from session keyring.

Other research

    grep -ir 'pam_keyinit.so' /etc/pam.d/* /usr/lib//pam.d/*

        Shows that it is included in MANY pam config files

    man pam_keyinit.so says

        The pam_keyinit PAM module ensures that the invoking process has a
        session keyring other than the user default session keyring.

        In order to allow other PAM modules to attach tokens to the keyring,
        this module provides both an auth (limited to pam_setcred(3)
        and a session component.

        The session keyring is created in the module called.

        Moreover this module should be included as early as possible
        in a PAM configuration.

    man cifscreds NOTES say

       The cifscreds utility requires a kernel built with support for the
       login key type.

       That key type was added in v3.3 in mainline Linux kernels.

       Since cifscreds adds keys to the session keyring, it is highly
recommended
       that one use pam_keyinit to ensure that a session keyring is established
       at login time.

*** Conclusion

It appears that the session keyring is being creating improperly during
GUI login such that cifscreds cannot use it, possibly it is not attached
to the correct process ?

This item on kernel org is from 2012 !!!

https://patchwork.kernel.org/project/cifs-client/patch/1342704916-2224-1-git-send-email-jlayton-at-samba.org/

Seems to describe the problem I am seeing and also demonstrated how the issue
does not exist at the tty console ( Ctrl+Alt+F1 ) but did when done from the
GUI ( xfec4 in that case ) they have the same issue I am reporting.

In one of the comments where somebody tested on a fairly stock Fedora 17 they
said

    An excellent question. I see the same behavior on a fairly stock Fedora
    17 host too. I can only assume that the actual desktop session is
    ending up with a different keyring session than gdm had.

It sure seems like that old issue is exactly what I am seeing here since
the Ctrl+Alt+F1 console does not have the issue and the GUI login does.

The bottom line is that something is wrong with the default pam config for
pam_keyinit.so when you log into the KDE GUI such that the session
keyring is not seen/available to cifscreds and adding to
common-session-pc works around the issue for now but may not be the best
solution or could have other security issues.

I suspect that the real solution is to make sure that KDE GUI login has the
session keyring created in the same way and attached to the same process
as the Ctrl+Alt+F1 login.

I am happy to perform any other tests or gather other information just
provide the steps for whatever other information you need.

Hopefully this very detailed bug report provides you with most of the
legwork completed to debug and now we only need the fix created.


--1680187810.1CC13e0.9081
Date: Thu, 30 Mar 2023 14:50:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1209970

            Bug ID: 1209970
           Summary: Trimmed "Leap" logo on the default wallpaper
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Xfce
          Assignee: bnc-team-xfce-at-forge.provo.novell.com
          Reporter: tiwai-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 866004
  --> http://bugzilla.opensuse.org/attachment.cgi?id=866004&action=edit
Desktop screenshot

When installing on Lenovo Thinkpad T14s Gen 3, the "Leap" logo appears at the
upper right corner, but it's trimmed.
It still works from functionality POV, but it's not nice at all.

The problem is likely the screen aspect ratio.  T14s has the screen size
1920x1200, while the default wallpeper for xfce is 1600x1200.

Can the artwork be adjusted to place the logo at a bit lower position?


body:
Build Identifier:

Booting today, I got a message:

Something has gone wrong.  Security violation.

It mentioned "shim", so I assume it was problem with validating "shim.efi".

The message goes past very quickly, so it is hard to get the exact wording.
After that it shuts the system down.

Microsoft Windows 8.1 still boots normally.  However, I get this failure with
both the Tumbleweed/openSUSE shim and with Leap/SUSE shim.

Earlier today, I booted to Tumbleweed.  That boot used the shim from Leap 15.4.
 I then updated Tumbleweed (previous update was 2 weeks earlier).  On rebooting
after that update, I ran into this problem.  I'm suspecting that something
happened during the update to cause this

summary: Secure boot violation


--1680479922.4EBfDF0.26974
Date: Sun, 2 Apr 2023 23:58:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1210033

            Bug ID: 1210033
           Summary: [Build 20230401] no access to repos in wsl
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/3206199/modules/wsl_
                    cmd_check/steps/26
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: WSL
          Assignee: sle-ms-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-c-at-suse.de
          Found By: openQA
           Blocker: Yes

## Observation

openQA test in scenario opensuse-Tumbleweed-WSL-x86_64-wsl-main@64bit_win fails
in
[wsl_cmd_check](https://openqa.opensuse.org/tests/3206199/modules/wsl_cmd_check/steps/26)

## Test suite description
The base test suite is used for job templates defined in YAML documents. It has
no settings of its own.

## Reproducible

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

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=WSL&machine=64bit_win&test=wsl-main&version=Tumbleweed)


--1680626499.cEa8F1A30.9069
Date: Tue, 4 Apr 2023 16:41:39 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1210115

            Bug ID: 1210115
           Summary: mame fails to build on Leap 15.5 because of find-debuginfo.sh
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: lubos.kocman-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello

meme fails to build on Leap 15.5 the build failure seems to be related to
generation of debuginfo packages

[ 2447s] + test -z
/home/abuild/rpmbuild/BUILDROOT/mame-0.193-bp155.2.26.x86_64//usr/share/mame/bgfx/effects/README.md
[ 2447s] + test -z ''
[ 2447s] + _target=
[ 2447s] + continue
[ 2447s] + read _file
[ 2447s] + /usr/lib/rpm/find-debuginfo.sh -j08 --build-id-seed 0.193-bp155.2.26
--unique-debug-suffix -0.193-bp155.2.26.x86_64 --unique-debug-src-base
mame-0.193-bp155.2.26.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000
--dwz-max-die-limit 50000000 -S debugsourcefiles.list
/home/abuild/rpmbuild/BUILD/mame-mame0193
[ 2447s] /usr/lib/rpm/find-debuginfo.sh: line 513: ((: 08: value too great for
base (error token is "08")
[ 2447s] /usr/lib/rpm/find-debuginfo.sh: line 521:
/tmp/find-debuginfo.NU1Guv/res.*: No such file or directory
[ 2447s] error: Bad exit status from /var/tmp/rpm-tmp.XCr6Ge (%install)
[ 2447s]

We'd like to have the build failure fixed prior to the RC build in April. See
https://en.opensuse.org/openSUSE:Roadmap for more details.


--1680647685.012d6A0A1.3864
Date: Tue, 4 Apr 2023 22:34:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1210126

            Bug ID: 1210126
           Summary: VUL-0: chromium: multiple security issues fixed in 112.0.5615.49
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: gmbr3-at-opensuse.org
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: security-team-at-suse.de
          Found By: ---
           Blocker: ---

https://chromereleases.googleblog.com/2023/04/stable-channel-update-for-desktop.html

Fixed in Chromium 112.0.5615.49:

CVE-2023-1810: Heap buffer overflow in Visuals
CVE-2023-1811: Use after free in Frames
CVE-2023-1812: Out of bounds memory access in DOM Bindings
CVE-2023-1813: Inappropriate implementation in Extensions
CVE-2023-1814: Insufficient validation of untrusted input in Safe Browsing
CVE-2023-1815: Use after free in Networking APIs
CVE-2023-1816: Incorrect security UI in Picture In Picture
CVE-2023-1817: Insufficient policy enforcement in Intents
CVE-2023-1818: Use after free in Vulkan
CVE-2023-1819: Out of bounds read in Accessibility
CVE-2023-1820: Heap buffer overflow in Browser History
CVE-2023-1821: Inappropriate implementation in WebShare
CVE-2023-1822: Incorrect security UI in Navigation
CVE-2023-1823: Inappropriate implementation in FedCM
Various fixes from internal audits, fuzzing and other initiatives


body:
--1680715932.3BdA6B30.27766
Date: Wed, 5 Apr 2023 17:32:12 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1210176

            Bug ID: 1210176
           Summary: LLVM16 breaks Thunderbird 102 build
    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: wolfgang-at-rosenauer.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since LLVM16 landed on Tumbleweed Thunderbird fails to build.

https://build.opensuse.org/package/live_build_log/mozilla:Factory/MozillaThunderbird/openSUSE_Factory_pure/x86_64

As long as we don't find a solution to make TB compile again (which we might
not be able to w/o upstream) there are no TB updates possible anymore in
Tumbleweed.

summary: LLVM16 breaks Thunderbird 102 build


--1680787601.7A1521f20.9737
Date: Thu, 6 Apr 2023 13:26:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1210220

            Bug ID: 1210220
           Summary: Amarok Crashes on Startup - Tumbleweed 20230404
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: cygnix-at-protonmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On Tumbleweed 20230404, Amarok crashes upon startup, and here is the backtrace
provided:

Application: Amarok (amarok), signal: Aborted

[KCrash Handler]
#4  0x00007f8c37e94d7c in __pthread_kill_implementation () at /lib64/libc.so.6
#5  0x00007f8c37e43356 in raise () at /lib64/libc.so.6
#6  0x00007f8c37e2b897 in abort () at /lib64/libc.so.6
#7  0x00007f8c384bb4e9 in  () at /lib64/libQt5Core.so.5
#8  0x00007f8c384bbd86 in  () at /lib64/libQt5Core.so.5
#9  0x00007f8c39ca9ac3 in  () at /lib64/libamaroklib.so.1
#10 0x00007f8c39c7f9d3 in Playlist::Actions::playlistModeChanged() () at
/lib64/libamaroklib.so.1
#11 0x00007f8c39c82d69 in Playlist::Actions::init() () at
/lib64/libamaroklib.so.1
#12 0x00007f8c39c82dc0 in Playlist::Actions::instance() () at
/lib64/libamaroklib.so.1
#13 0x00007f8c39e593bf in MainWindow::createActions() () at
/lib64/libamaroklib.so.1
#14 0x00007f8c39e4f1cb in MainWindow::MainWindow() () at
/lib64/libamaroklib.so.1
#15 0x00007f8c39e494de in App::continueInit() () at /lib64/libamaroklib.so.1
#16 0x0000561ec3cf3f71 in  ()
#17 0x00007f8c37e2cbb0 in __libc_start_call_main () at /lib64/libc.so.6
#18 0x00007f8c37e2cc79 in __libc_start_main_impl () at /lib64/libc.so.6
#19 0x0000561ec3cf4815 in  ()
[Inferior 1 (process 21607) detached]


body:
--1680993504.D2Cd600.31080
Date: Sat, 8 Apr 2023 22:38:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1210267

            Bug ID: 1210267
           Summary: Trouble with newest package amavisd-new
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: freek-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The new version of /etc/amavisd.conf in package amvisd-new, which came in
20230407, changes the working directory for amavis.service from /var/spool/
amavis into /var/amavis.
However this change is not reflected in creating the necessary folders in
/var/amavis like /var/amavis/{tmp,db} with the owner/group vscan:vscan.
Also the working directory in /usr/lib/systemd/system/amavis.service needs to
be changed in the same way.

summary: Trouble with newest package amavisd-new


--16880202512.46447.28742
Date: Thu, 29 Jun 2023 06:30:51 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1212834
           Summary: The %python_subpackages macro produces an error on 15.5
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: asn-at-cryptomilk.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

[   41s] error: parse error in expression
[   41s] error: /home/abuild/rpmbuild/SOURCES/python-mailmanclient.spec:51:=
 bad
%if condition

See e.g.:

https://build.opensuse.org/package/show/devel:languages:python:mailman:back=
ports/python-mailmanclient

Note that this project uses devel:languages:python:backports!
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16880202512.46447.28742
Date: Thu, 29 Jun 2023 06:30:51 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1212834

          Summary
          The %python_subpackages macro produces an error on 15.5

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          asn@cryptomilk.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

[   41s] error: parse error in expression
[   41s] error: /home/abuild/rpmbuild/SOURCES/python-mailmanclient.spec:51:=
 bad
%if condition

See e.g.:

https://build.opensuse.org/package/s=
how/devel:languages:python:mailman:backports/python-mailmanclient

Note that this project uses devel:languages:python:backports!

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

You are on the CC list for the bug.

=

--16880202512.46447.28742--


--16880207192.e17e.28751
Date: Thu, 29 Jun 2023 06:38:39 +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=3D1212835

            Bug ID: 1212835
           Summary: make modules_install fails with kmod-30-4.1
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: msuchanek-at-suse.com
          Reporter: ptesarik-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

With the usrmerge patches, depmod now accesses $base/usr/lib/modules instea=
d of
$base/lib/modules. Unfortunately, scripts/depmod.sh in the kernel sources
cannot cope with that and fails with a slightly confusing message:

depmod: ERROR: could not open directory
/srv/research/dynswiotlb-9p/usr/lib/modules/99.98.6.5.0-devel+: No such fil=
e or
directory

I can see how this is fixed for RPM builds
(https://github.com/SUSE/kernel-source/commit/da84579e78f4c4efa5b3b910484fd=
aedc79fefec),
but I can no longer run "make modules_install" from the expanded kernel tre=
e.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16880207192.e17e.28751
Date: Thu, 29 Jun 2023 06:38:39 +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
          1212835

          Summary
          make modules_install fails with kmod-30-4.1

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          msuchanek@suse.com

          Reporter
          ptesarik@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

With the usrmerge patches, depmod now accesses $base/usr/lib=
/modules instead of
$base/lib/modules. Unfortunately, scripts/depmod.sh in the kernel sources
cannot cope with that and fails with a slightly confusing message:

depmod: ERROR: could not open directory
/srv/research/dynswiotlb-9p/usr/lib/modules/99.98.6.5.0-devel+: No such fil=
e or
directory

I can see how this is fixed for RPM builds
(https://github.com/SUSE/kernel-source/commit/da8457=
9e78f4c4efa5b3b910484fdaedc79fefec),
but I can no longer run "make modules_install" from the expanded =
kernel tree.

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

You are on the CC list for the bug.

=

--16880207192.e17e.28751--


--16880230080.2E29ed5.28799
Date: Thu, 29 Jun 2023 07:16:48 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1212837
           Summary: zgrep complains about lua-lmod files permissions
    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: ---

# zgrep --help
/usr/bin/zgrep: /usr/share/lmod/8.7.17/init/bash: Permission non accord=C3=
=A9e
Usage: /usr/bin/zgrep [OPTION]... [-e] PATTERN [FILE]...

[...]

# ls -l /usr/share/lmod/8.7.17/init=20=20=20=20=20
total 92
-rw-r--r


--16880245133.7Fb2.28877
Date: Thu, 29 Jun 2023 07:41: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=3D1212840

            Bug ID: 1212840
           Summary: colord-gtk segfault when turning monitors on again
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: All
                OS: openSUSE Leap 15.5
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mkubecek-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

(tracking only, issue identified and fixed in upstream bug tracker)

upstream tracker link: https://github.com/hughsie/colord-gtk/issues/22

On a system with two DisplayPort attached monitors, turning them off and
on again results in a reproducible crash of darktable application. The
segfault is caused by a bug in colord-gtk which has been fixed in upstream
by commit 8a395709fa0c9:

  https://github.com/hughsie/colord-gtk/commit/8a395709fa0c9

Going to submit a SR today.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16880245133.7Fb2.28877
Date: Thu, 29 Jun 2023 07:41: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
          1212840

          Summary
          colord-gtk segfault when turning monitors on again

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          All

          OS
          openSUSE Leap 15.5

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          mkubecek@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

(tracking only, issue identified and fixed in upstream bug t=
racker)

upstream tracker link: https://github.com/hughsie/colord-gtk/issues/22

On a system with two DisplayPort attached monitors, turning them off and
on again results in a reproducible crash of darktable application. The
segfault is caused by a bug in colord-gtk which has been fixed in upstream
by commit 8a395709fa0c9:

  ht=
tps://github.com/hughsie/colord-gtk/commit/8a395709fa0c9

Going to submit a SR today.

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

You are on the CC list for the bug.

=

--16880245133.7Fb2.28877--


--16882317970.48dBb91aD.465
Date: Sat, 1 Jul 2023 17:16:37 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1212913
           Summary: ldc-runtime-devel and ldc-phobos-devel conflicts with gcc-d
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: kuroki@Live.com.sg
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 867923
  --> https://bugzilla.suse.com/attachment.cgi?id=3D867923&action=3Dedit
gdc compilation error message

ldc2 and gdc(gcc-d) are two compilers of D programming language. Each has i=
ts
separate runtime library. They cannot be mixed together.

`ldc-runtime-devel` and `ldc-phobos-devel` installs runtime and std library=
 at
/usr/include/d.=20

`gdc` installs its runtime and std library at
/usr/lib64/gcc/x86_64-suse-linux/13/include/d.

Unfortunately, when both `ldc-runtime-devel` and `gdc` are installed, gdc w=
ould
look into /usr/include/d first, instead of its own accompanying source. And=
 a
compilation of a hello-world.d fails.

I reported the problems to `gdc` maintainer at dlang forum,
https://forum.dlang.org/post/kvhckvmmfdocfbxukesc-at-forum.dlang.org.=20

Iain's suggestion is to move ldc's runtime and standard library to another
location instead of /usr/include/d.

Attached is the stderr message of gdc compilation.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16882317970.48dBb91aD.465
Date: Sat, 1 Jul 2023 17:16:37 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1212913

          Summary
          ldc-runtime-devel and ldc-phobos-devel conflicts with gcc-d

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          kuroki@Live.com.sg

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachme=
nt 867923 [details]
gdc compilation error message

ldc2 and gdc(gcc-d) are two compilers of D programming language. Each has i=
ts
separate runtime library. They cannot be mixed together.

`ldc-runtime-devel` and `ldc-phobos-devel` installs runtime and std library=
 at
/usr/include/d.=20

`gdc` installs its runtime and std library at
/usr/lib64/gcc/x86_64-suse-linux/13/include/d.

Unfortunately, when both `ldc-runtime-devel` and `gdc` are installed, gdc w=
ould
look into /usr/include/d first, instead of its own accompanying source. And=
 a
compilation of a hello-world.d fails.

I reported the problems to `gdc` maintainer at dlang forum,
https://forum.dlang.org/post/kvhckvmmfdocfbxukesc@forum.dlang.or=
g.=20

Iain's suggestion is to move ldc's runtime and standard library to another
location instead of /usr/include/d.

Attached is the stderr message of gdc compilation.

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

You are on the CC list for the bug.

=

--16882317970.48dBb91aD.465--


--16883736791.bFD4874b.1424
Date: Mon, 3 Jul 2023 08:41: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=3D1212936

            Bug ID: 1212936
           Summary: [Build 20230701] qgis fails to build against updated exiv2
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/3399778/modules/qgis
                    /steps/21
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

## Observation

exiv2 was updated to version 0.28.x; as a result, qgis now fails to build:

[  868s]
/home/abuild/rpmbuild/BUILD/qgis-3.30.3/src/core/raster/qgsexiftools.cpp:69=
:40:
error: 'const class Exiv2::Xmpdatum' has no member named 'toLong'
[  868s]    69 |         val =3D QVariant::fromValue( it->toLong() );

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_gnome@64=
bit
fails in
[qgis](https://openqa.opensuse.org/tests/3399778/modules/qgis/steps/21)

## Test suite description
Maintainer: QE Core, asmorodskyi. Extra tests which were designed to run on
gnome

## Reproducible

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

## Expected result

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

## Further details

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

--16883736791.bFD4874b.1424
Date: Mon, 3 Jul 2023 08:41: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
          1212936

          Summary
          [Build 20230701] qgis fails to build against updated exiv2

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          URL
          https://openqa.opensuse.org/tests/3399778/modules/qgis/steps/=
21

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          dimstar@opensuse.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

## Observation

exiv2 was updated to version 0.28.x; as a result, qgis now fails to build:

[  868s]
/home/abuild/rpmbuild/BUILD/qgis-3.30.3/src/core/raster/qgsexiftools.cpp:69=
:40:
error: 'const class Exiv2::Xmpdatum' has no member named 'toLong'
[  868s]    69 |         val =3D QVariant::fromValue( it->toLong() );

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_gnome&#6=
4;64bit
fails in
[qgis](https://openqa.opensuse.org/tests/3399778/modules/qgis/steps/21)

## Test suite description
Maintainer: QE Core, asmorodskyi. Extra tests which were designed to run on
gnome

## Reproducible

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

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/la=
test?arch=3Dx86_64&distri=3Dopensuse&flavor=3DDVD&machine=3D64b=
it&test=3Dextra_tests_gnome&version=3DTumbleweed)

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

You are on the CC list for the bug.

=

--16883736791.bFD4874b.1424--


--16883861610.97EB.1808
Date: Mon, 3 Jul 2023 12:09:21 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1212947
           Summary: Disable fbdev userspace interfaces and programs
    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: tzimmermann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

We want to remove fbdev from kernel and userspace as far as possible. Linux=
 6.6
will allow us to disable fbdev's userspace interfaces, most noteably /dev/f=
b*.
Enable this feature in the TW kernel.

Framebuffer support has been an endless source of bugs. Not giving userspace
access to it's internals and framebuffer memory will close a possible entry
point for all sorts of malware.

Please note that the framebuffer console is implemented entirely within the
kernel and will not be affected by this change.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16883861610.97EB.1808
Date: Mon, 3 Jul 2023 12:09:21 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1212947

          Summary
          Disable fbdev userspace interfaces and programs

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

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

We want to remove fbdev from kernel and userspace as far as =
possible. Linux 6.6
will allow us to disable fbdev's userspace interfaces, most noteably /dev/f=
b*.
Enable this feature in the TW kernel.

Framebuffer support has been an endless source of bugs. Not giving userspace
access to it's internals and framebuffer memory will close a possible entry
point for all sorts of malware.

Please note that the framebuffer console is implemented entirely within the
kernel and will not be affected by this change.

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

You are on the CC list for the bug.

=

--16883861610.97EB.1808--


--16883934374.FC535B297.2027
Date: Mon, 3 Jul 2023 14:10:37 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1212949
           Summary: sshuttle.service: sshuttle: sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: vetter-at-physik.uni-wuerzburg.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

sshuttle cannot run as a service using "systemctl start sshuttle":

sshuttle[27072]: sudo: The "no new privileges" flag is set, which prevents =
sudo
from running as root.

This might be due to the hardenings from #1181400, since most of the
Private*=3DTrue and Protect*=3DTrue setting also imply NoNewPrivileges=3Dye=
s.

A plain "sudo -u sshuttle sshuttle -r root-at-sever.com 10.1.2.3/16" does work.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16883934374.FC535B297.2027
Date: Mon, 3 Jul 2023 14:10:37 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1212949

          Summary
          sshuttle.service: sshuttle: sudo: The "no new privileges=
" flag is set, which prevents sudo from running as root.

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          vetter@physik.uni-wuerzburg.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

sshuttle cannot run as a service using "systemctl start=
 sshuttle":

sshuttle[27072]: sudo: The "no new privileges" flag is set, which=
 prevents sudo
from running as root.

This might be due to the hardenings from #1181400, since most of the
Private*=3DTrue and Protect*=3DTrue setting also imply NoNewPrivileges=3Dye=
s.

A plain "sudo -u sshuttle sshuttle -r root@sever.com 10.1.2.3/16" does work.

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

You are on the CC list for the bug.

=

--16883934374.FC535B297.2027--


--16883997042.7fcd41f3.2287
Date: Mon, 3 Jul 2023 15:55:04 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1212956
           Summary: Linphone 5.0.16 fails to launch. Symbol lookup error
    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: lair.retention968@4wrd.cc
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

When launching Linphone, the following symbol lookup error message is shown:

linphone: symbol lookup error: /lib64/liblinphone.so.10: undefined symbol:
_ZN4lime11LimeManager6updateERKSt8functionIFvNS_14CallbackReturnENSt7__cxx1=
112basic_stringIcSt11char_traitsIcESaIcEEEEE

linphone - 5.0.16-1.3

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

--16883997042.7fcd41f3.2287
Date: Mon, 3 Jul 2023 15:55:04 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1212956

          Summary
          Linphone 5.0.16 fails to launch. Symbol lookup error

          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
          lair.retention968@4wrd.cc

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

When launching Linphone, the following symbol lookup error m=
essage is shown:

linphone: symbol lookup error: /lib64/liblinphone.so.10: undefined symbol:
_ZN4lime11LimeManager6updateERKSt8functionIFvNS_14CallbackReturnENSt7__cxx1=
112basic_stringIcSt11char_traitsIcESaIcEEEEE

linphone - 5.0.16-1.3

liblime - 5.2.73-1.1

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

You are on the CC list for the bug.

=

--16883997042.7fcd41f3.2287--


--16884555070.da1d.3292
Date: Tue, 4 Jul 2023 07: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=3D1212970

            Bug ID: 1212970
           Summary: [JeOS] systemd-vconsole-setup[165]: /usr/bin/setfont failed with exit status 71.
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
               URL: https://openqa.opensuse.org/tests/3403981/modules/jour
                    nal_check/steps/9
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: qa-bugs-at-suse.de
                CC: antonio.teixeira-at-suse.com, dmueller-at-suse.com,
                    fvogt-at-suse.com
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

Created attachment 867964
  --> https://bugzilla.suse.com/attachment.cgi?id=3D867964&action=3Dedit
main packages changes

## Observation

openQA test in scenario
opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-extra@aarch64-HD20G fails=
 in
[journal_check](https://openqa.opensuse.org/tests/3403981/modules/journal_c=
heck/steps/9)

openQA found erros in journal on aarch64 JeOS images (only):
localhost systemd-vconsole-setup[165]: /usr/bin/setfont failed with exit st=
atus
71.
localhost systemd-vconsole-setup[169]: setfont: ERROR kdfontop.c:183
put_font_kdfontop: Unable to load such font with such kernel version
localhost systemd-vconsole-setup[165]: Setting fonts failed with a "system
error", ignoring.

The list of main changes would point to kbd update:
https://build.opensuse.org/request/show/1096363

## Test suite description
Same as jeos, plus some more tests.

## Reproducible

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

## Expected result

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

## Further details

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

--16884555070.da1d.3292
Date: Tue, 4 Jul 2023 07: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
          1212970

          Summary
          [JeOS] systemd-vconsole-setup[165]: /usr/bin/setfont failed w=
ith exit status 71.

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          aarch64

          URL
          https://openqa.opensuse.org/tests/3403981/modules/journal_che=
ck/steps/9

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          guillaume.gardet@arm.com

          QA Contact
          qa-bugs@suse.de

          CC
          antonio.teixeira@suse.com, dmueller@suse.com, fvogt&#=
64;suse.com

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

Created attachment 86796=
4 [details]
main packages changes

## Observation

openQA test in scenario
opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-extra@aarch64-HD20G f=
ails in
[journal_check](https://openqa.opensuse.org/tests/3403981/modules/=
journal_check/steps/9)

openQA found erros in journal on aarch64 JeOS images (only):
localhost systemd-vconsole-setup[165]: /usr/bin/setfont failed with exit st=
atus
71.
localhost systemd-vconsole-setup[169]: setfont: ERROR kdfontop.c:183
put_font_kdfontop: Unable to load such font with such kernel version
localhost systemd-vconsole-setup[165]: Setting fonts failed with a "sy=
stem
error", ignoring.

The list of main changes would point to kbd update:
https://build.o=
pensuse.org/request/show/1096363

## Test suite description
Same as jeos, plus some more tests.

## Reproducible

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

## Expected result

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

## Further details

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

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

You are on the CC list for the bug.

=

--16884555070.da1d.3292--


--16885457351.4cB1AD.5712
Date: Wed, 5 Jul 2023 08:28: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=3D1213005

            Bug ID: 1213005
           Summary: python-setuptools-rust hangs in %check on armv6
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: armv5
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Python
          Assignee: python-maintainers-at-suse.com
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: qa-bugs-at-suse.de
                CC: afaerber-at-suse.com, dmueller-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

python-setuptools-rust hangs in %check on armv6:

[   32s] Processing
/home/abuild/rpmbuild/BUILD/setuptools-rust-1.6.0/examples/hello-world
[   32s]   Preparing metadata (pyproject.toml): started
[   32s]   Preparing metadata (pyproject.toml): finished with status 'done'
[   32s] Building wheels for collected packages: hello-world
[   32s]   Building wheel for hello-world (pyproject.toml): started
***** Hangs here *****

This prevents python-cryptography to build and prevents all armv6 images to
build.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16885457351.4cB1AD.5712
Date: Wed, 5 Jul 2023 08:28: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
          1213005

          Summary
          python-setuptools-rust hangs in %check on armv6

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          armv5

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Python

          Assignee
          python-maintainers@suse.com

          Reporter
          guillaume.gardet@arm.com

          QA Contact
          qa-bugs@suse.de

          CC
          afaerber@suse.com, dmueller@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

python-setuptools-rust hangs in %check on armv6:

[   32s] Processing
/home/abuild/rpmbuild/BUILD/setuptools-rust-1.6.0/examples/hello-world
[   32s]   Preparing metadata (pyproject.toml): started
[   32s]   Preparing metadata (pyproject.toml): finished with status 'done'
[   32s] Building wheels for collected packages: hello-world
[   32s]   Building wheel for hello-world (pyproject.toml): started
***** Hangs here *****

This prevents python-cryptography to build and prevents all armv6 images to
build.

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

You are on the CC list for the bug.

=

--16885457351.4cB1AD.5712--


--16885469043.28D37935b.5754
Date: Wed, 5 Jul 2023 08:48: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=3D1213006

            Bug ID: 1213006
           Summary: VUL-0: CVE-2023-34457: python-MechanicalSoup: malicious web server can read arbitrary files on client using file input inside HTML form
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: toddrme2178-at-gmail.com
          Reporter: carlos.lopez-at-suse.com
        QA Contact: security-team-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

CVE-2023-34457

A malicious web server can read arbitrary files on the client using a <input
type=3D"file" ...> inside HTML form. All users of MechanicalSoup's form
submission are affected, unless they took very specific (and manual) steps =
to
reset HTML form field values.

https://github.com/MechanicalSoup/MechanicalSoup/security/advisories/GHSA-x=
456-3ccm-m6j4

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2023-34457
https://bugzilla.redhat.com/show_bug.cgi?id=3D2219755
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16885469043.28D37935b.5754
Date: Wed, 5 Jul 2023 08:48: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
          1213006

          Summary
          VUL-0: CVE-2023-34457: python-MechanicalSoup: malicious web s=
erver can read arbitrary files on client using file input inside HTML form

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.4

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          toddrme2178@gmail.com

          Reporter
          carlos.lopez@suse.com

          QA Contact
          security-team@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

CVE-2023-34457

A malicious web server can read arbitrary files on the client using a <i=
nput
type=3D"file" ...> inside HTML form. All users of MechanicalSo=
up's form
submission are affected, unless they took very specific (and manual) steps =
to
reset HTML form field values.

https://github.com/MechanicalSoup/MechanicalSoup/=
security/advisories/GHSA-x456-3ccm-m6j4

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2023-34457
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2219755

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

You are on the CC list for the bug.

=

--16885469043.28D37935b.5754--


body:
t/537.36 (KHTML,
like Gecko) Chrome/114.0.0.0 Safari/537.36
Build Identifier:=20

When creating a new container using "distrobox-create" the contai=
ner fails to
display directory names properly.

For example the directory named "Sta=C5=BEen=C3=A9" shows up as
"'Sta'$'\305\276''en'$'\303\251'" when using ls.

Reproducible: Always

Steps to Reproduce:
1. Use the czech locale
2. Create a directory inside the home that uses one of the offending symbols
3. Create a new distrobox container and run "ls"
Actual Results:=20=20
Directory name isn't properly displayed.

Expected Results:=20=20
Directory name is properly displayed.

A workaround is to install the "glibc-locale" package.

This can be automated by adding 'container_additional_packages=3D"glib=
c-locale"'
into the distrobox configuration.

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

You are on the CC list for the bug.

=

--16885876170.F1F1d03fB.7136--

summary: locale problems in the default distrobox configuration


body:
--16889881433.bBa2799.12728
Date: Mon, 10 Jul 2023 11:22:23 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1213178
           Summary: lddtree fails to run
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: x86-64
                OS: openSUSE Leap 15.5
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: bugzilla.opensuse.org-at-urbanec.net
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Leap 15.5 system with
 * pax-utils-1.3.7-bp155.1.5.x86_64
 * python3-pyelftools-0.29-150500.1.4.noarch

$ lddtree /lib64/libc.so.6
  File "/usr/bin/lddtree", line 53
    assert sys.version_info >=3D (3, 6), f"Python 3.6+ required, but found
{sys.version}"
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
      ^
SyntaxError: invalid syntax

Attempt a workaround by specifying a python3 interpreter:

$ python3 /usr/bin/lddtree /lib64/libc.so.6
Traceback (most recent call last):
  File "/usr/bin/lddtree", line 128, in <module>
    def dedupe(items: list[str]) -> list[str]:
TypeError: 'type' object is not subscriptable

This is a regression from Leap 15.4, where `lddtree` used to work without
issues.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16889881433.bBa2799.12728
Date: Mon, 10 Jul 2023 11:22:23 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1213178

          Summary
          lddtree fails to run

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          x86-64

          OS
          openSUSE Leap 15.5

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          bugzilla.opensuse.org@urbanec.net

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Leap 15.5 system with
 * pax-utils-1.3.7-bp155.1.5.x86_64
 * python3-pyelftools-0.29-150500.1.4.noarch

$ lddtree /lib64/libc.so.6
  File "/usr/bin/lddtree", line 53
    assert sys.version_info >=3D (3, 6), f"Python 3.6+ required, bu=
t found
{sys.version}"
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
      ^
SyntaxError: invalid syntax

Attempt a workaround by specifying a python3 interpreter:

$ python3 /usr/bin/lddtree /lib64/libc.so.6
Traceback (most recent call last):
  File "/usr/bin/lddtree", line 128, in <module>
    def dedupe(items: list[str]) -> list[str]:
TypeError: 'type' object is not subscriptable

This is a regression from Leap 15.4, where `lddtree` used to work without
issues.

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

You are on the CC list for the bug.

=

--16889881433.bBa2799.12728--

summary: lddtree fails to run


--16893492933.d7a2D5c8D.2776
Date: Fri, 14 Jul 2023 15:41:33 +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=3D1213351

            Bug ID: 1213351
           Summary: python-lxml contains non-free file (RNG scheme for ISO Schematron)
    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: ---

Red Hat lawyers concluded
(https://gitlab.com/fedora/legal/fedora-license-data/-/issues/154) that the
license included in
https://github.com/lxml/lxml/blob/master/src/lxml/isoschematron/resources/r=
ng/iso-schematron.rng
is confusing, misworded, and most likely non-Free (distribute-only-for-grat=
is
problem).

They started to remove the schema file from their project (e.g.,
https://src.fedoraproject.org/rpms/python-lxml/c/9d95f5a04edc386313fa854541=
971b3af07bcae1?branch=3Drawhide).

This issue has been reported upstream as
https://bugs.launchpad.net/lxml/+bug/2024343 and they created patch which
allows the test suite to pass even without RNG file in the question.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16893492933.d7a2D5c8D.2776
Date: Fri, 14 Jul 2023 15:41:33 +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
          1213351

          Summary
          python-lxml contains non-free file (RNG scheme for ISO Schema=
tron)

          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
          ---

Red Hat lawyers concluded
(https://gitlab.com/fedora/legal/fedora-license-data/-/issues/154) th=
at the
license included in
https://github.com/lxml/lxml/blob/master/=
src/lxml/isoschematron/resources/rng/iso-schematron.rng
is confusing, misworded, and most likely non-Free (distribute-only-for-grat=
is
problem).

They started to remove the schema file from their project (e.g.,
https://src.fedoraproject.org/r=
pms/python-lxml/c/9d95f5a04edc386313fa854541971b3af07bcae1?branch=3Drawhide=
).

This issue has been reported upstream as
https://bugs.launc=
hpad.net/lxml/+bug/2024343 and they created patch which
allows the test suite to pass even without RNG file in the question.

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

You are on the CC list for the bug.

=

--16893492933.d7a2D5c8D.2776--


--16895231693.25a7F.3563
Date: Sun, 16 Jul 2023 15:59:29 +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=3D1213366

            Bug ID: 1213366
           Summary: Steam sync not working in Lutris on Leap 15.5 (and likely also 15.4)
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: marix-at-marix.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Syncing the Steam library does not work in Lutris on Leap 15.5. I get the
following error:

2023-07-16 17:47:05,984: Error while completing task <bound method
BaseService.reload of <steam.SteamService object at 0x7f7b64cd87e0
(lutris+services+steam+SteamService at 0x557eb4432500)>>: <class 'KeyError'>
'contentstatsid'
  File "/usr/lib/python3.6/site-packages/lutris/util/jobs.py", line 34, in
target
    result =3D self.function(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/lutris/services/base.py", line 85,=
 in
reload
    self.add_installed_games()
  File "/usr/lib/python3.6/site-packages/lutris/services/steam.py", line 15=
9,
in add_installed_games
    for steamapps_path in self.steamapps_paths:
  File "/usr/lib/python3.6/site-packages/lutris/services/steam.py", line 15=
4,
in steamapps_paths
    return get_steamapps_paths()
  File "/usr/lib/python3.6/site-packages/lutris/util/steam/config.py", line
170, in get_steamapps_paths
    return steam.steam().get_steamapps_dirs()
  File "/usr/lib/python3.6/site-packages/lutris/runners/steam.py", line 243=
, in
get_steamapps_dirs
    library_config =3D self.get_library_config()
  File "/usr/lib/python3.6/site-packages/lutris/runners/steam.py", line 149=
, in
get_library_config
    return read_library_folders(self.steam_data_dir)
  File "/usr/lib/python3.6/site-packages/lutris/util/steam/config.py", line
161, in read_library_folders
    library["libraryfolders"].pop("contentstatsid")

Well, most users will only get a popup that says "contentstatsid" and notice
the sync not working. But this backtrace is shown on the terminal when star=
ting
Lutris from there.

The issue has been tracked upstream as
https://github.com/lutris/lutris/issues/4175 and is fixed in 0.5.10. But Le=
ap
still ships 0.5.9.

The specific commit fixing it seems to be
https://github.com/lutris/lutris/commit/072e72a4aefd91101b79dd05d8ce9f100a4=
b6b0c.

If I manually apply the fix from the commit on my system, the issue is
resolved. We might want to consider applying the patch during packaging or =
just
upgrading the Leap version.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16895231693.25a7F.3563
Date: Sun, 16 Jul 2023 15:59:29 +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
          1213366

          Summary
          Steam sync not working in Lutris on Leap 15.5 (and likely als=
o 15.4)

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X11 Applications

          Assignee
          screening-team-bugs@suse.de

          Reporter
          marix@marix.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Syncing the Steam library does not work in Lutris on Leap 15=
.5. I get the
following error:

2023-07-16 17:47:05,984: Error while completing task <bound method
BaseService.reload of <steam.SteamService object at 0x7f7b64cd87e0
(lutris+services+steam+SteamService at 0x557eb4432500)>>: <class '=
KeyError'>
'contentstatsid'
  File "/usr/lib/python3.6/site-packages/lutris/util/jobs.py", li=
ne 34, in
target
    result =3D self.function(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/lutris/services/base.py"=
, line 85, in
reload
    self.add_installed_games()
  File "/usr/lib/python3.6/site-packages/lutris/services/steam.py&quot=
;, line 159,
in add_installed_games
    for steamapps_path in self.steamapps_paths:
  File "/usr/lib/python3.6/site-packages/lutris/services/steam.py&quot=
;, line 154,
in steamapps_paths
    return get_steamapps_paths()
  File "/usr/lib/python3.6/site-packages/lutris/util/steam/config.py&q=
uot;, line
170, in get_steamapps_paths
    return steam.steam().get_steamapps_dirs()
  File "/usr/lib/python3.6/site-packages/lutris/runners/steam.py"=
, line 243, in
get_steamapps_dirs
    library_config =3D self.get_library_config()
  File "/usr/lib/python3.6/site-packages/lutris/runners/steam.py"=
, line 149, in
get_library_config
    return read_library_folders(self.steam_data_dir)
  File "/usr/lib/python3.6/site-packages/lutris/util/steam/config.py&q=
uot;, line
161, in read_library_folders
    library["libraryfolders"].pop("contentstatsid")

Well, most users will only get a popup that says "contentstatsid"=
 and notice
the sync not working. But this backtrace is shown on the terminal when star=
ting
Lutris from there.

The issue has been tracked upstream as
https://github.com=
/lutris/lutris/issues/4175 and is fixed in 0.5.10. But Leap
still ships 0.5.9.

The specific commit fixing it seems to be
https://github.com/lutris/lutris/commit/072e72a4aefd91101=
b79dd05d8ce9f100a4b6b0c.

If I manually apply the fix from the commit on my system, the issue is
resolved. We might want to consider applying the patch during packaging or =
just
upgrading the Leap version.

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

You are on the CC list for the bug.

=

--16895231693.25a7F.3563--


--16895379243.168Ea601.3650
Date: Sun, 16 Jul 2023 20:05: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=3D1213370

            Bug ID: 1213370
           Summary: tesseract-ocr should not be built with experimantal opencl support
    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: opensuse-at-titlis.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

opencl in tesseract-ocr is considered experimental, according to this thread
(https://groups.google.com/g/tesseract-ocr/c/eIQbsurfSEM/m/mVb_4GF1BgAJ) it=
 is
considered just an entry point for possible developers. Their own
doucmentantion (https://tesseract-ocr.github.io/tessdoc/TesseractOpenCL.htm=
l)
states: "Important note: OpenCL support in Tesseract is still considered
experimental. There are some major bugs associated with it (see issue 837).
Building Tesseract with OpenCL support is not recommended (for any version =
of
Tesseract), unless you are a developer and want to improve the OpenCL code"

Please remove the flag "--enable-opencl" from
https://build.opensuse.org/package/view_file/openSUSE:Factory/tesseract-ocr=
/tesseract-ocr.spec

This would also resolve https://bugzilla.opensuse.org/show_bug.cgi?id=3D120=
7570

PS: I indeed encounter problems with the opencl code path
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16895379243.168Ea601.3650
Date: Sun, 16 Jul 2023 20:05: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
          1213370

          Summary
          tesseract-ocr should not be built with experimantal opencl su=
pport

          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
          opensuse@titlis.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

opencl in tesseract-ocr is considered experimental, accordin=
g to this thread
(https://groups.google.com/g/tesseract-ocr/c/eIQbsurfSEM/m/mVb_4GF1=
BgAJ) it is
considered just an entry point for possible developers. Their own
doucmentantion (https://tesseract-ocr.github.io/tessdoc/TesseractOpenCL.html<=
/a>)
states: "Important note: OpenCL support in Tesseract is still consider=
ed
experimental. There are some major bugs associated with it (see issue 837).
Building Tesseract with OpenCL support is not recommended (for any version =
of
Tesseract), unless you are a developer and want to improve the OpenCL code&=
quot;

Please remove the flag "--enable-opencl" from
https://build.opensuse.org/package/view_fil=
e/openSUSE:Factory/tesseract-ocr/tesseract-ocr.spec

This would also resolve https://bugzilla.opensuse.org/show_bug.cgi?id=3D1207570

PS: I indeed encounter problems with the opencl code path

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

You are on the CC list for the bug.

=

--16895379243.168Ea601.3650--


--16897133642.06c9e6.13725
Date: Tue, 18 Jul 2023 20:49: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=3D1213439

            Bug ID: 1213439
           Summary: [WINE] Wine desktop file does not work correctly
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: thaynan.mdsilva-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Hello!

The key `Exec' of the WINE `wine.desktop' file is looks like this:

> Exec=3Dwine %f

This makes EXE programs to start with the startup directory (PWD) set to the
user home, and programs causes programs that look for files in their startup
directory to fail execution.

The ideal value for the key `Exec' is as followed:

> Exec=3Dwine start /unix %f

This makes it so WINE sets the program working directory to the path of the
EXE, making the program work correctly.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16897133642.06c9e6.13725
Date: Tue, 18 Jul 2023 20:49: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
          1213439

          Summary
          [WINE] Wine desktop file does not work correctly

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          All

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Enhancement

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          thaynan.mdsilva@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Hello!

The key `Exec' of the WINE `wine.desktop' file is looks like this:

> Exec=3Dwine %f

This makes EXE programs to start with the startup directory (PWD) set to the
user home, and programs causes programs that look for files in their startup
directory to fail execution.

The ideal value for the key `Exec' is as followed:

> Exec=3Dwine start /unix %f

This makes it so WINE sets the program working directory to the path of the
EXE, making the program work correctly.

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

You are on the CC list for the bug.

=

--16897133642.06c9e6.13725--


body:
t/537.36 (KHTML,
like Gecko) Chrome/114.0.0.0 Safari/537.36
Build Identifier:=20

So I spent a couple evenings hunting down a very frustating bug involving
Lutris, Wine and EasyAntiCheat (EAC). The bug appears when trying to run Tom
Clancy's The Division 2 using the Ubisoft Connect launcher through Lutris a=
nd
Wine-GE v8.10. The game will install and launch fine, but upon selecting the
character (i.e., logging into the game) the game will crash with a Delta er=
ror.
This is indicative of a network problem.

To rule out the problem was with the game itself I installed the game using=
 the
same runner in bottles (Flatpak) and the problem did not appear. However, I=
 do
not desire to use Flatpak and bottles for gaming on my system so I persiste=
d to
find the underlying problem. Google didn't offer much help until I stumbled
across this recent thread by accident (from another game):=20

https://forum.albiononline.com/index.php=
/Thread/177592-Disconnected-by-EasyAntiCheat-on-OpenSuse/

It appears EAC tries to establish a connection but fails due to missing CA
certificates. Thus, other games using EAC may also be affected. Installing =
the
ca-certificates-steamtricks package manually resolves the problem. It also
appears to not affect users that have both steam and lutris installed, beca=
use
steam pulls in steamtricks, which has ca-certificates-steamtricks as a
recommended dependency. However, lutris should not depend on steam being
installed for a specific subsection of games (using EAC) to work. Therefore,
adding  ca-certificates-steamtricks to lutris as a recommended dependency
should suffice to resolve the bug.

Reproducible: Always

Steps to Reproduce:
1. Install lutris from official TW repos
2. Download and install Wine-GE 8.10 runner
3. Install Ubisoft Connect using the installer provided by Ubisoft and the
Wine-GE v8.10 runner
4. Launch Ubisoft Connect, login and install Tom Clancy's The Division 2.
5. Launch the game and login
Actual Results:=20=20
The game crashes with a network related error

Expected Results:=20=20
The game loads normally without an error

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

You are on the CC list for the bug.

=

--16897163100.bD3f21850.13740--

summary: Add ca-certificates-steamtricks to lutris recommended deps


--16897563672.CF25430F3.14310
Date: Wed, 19 Jul 2023 08:46: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=3D1213459

            Bug ID: 1213459
           Summary: suse-module-tools: allow to replace regenerate-initrd-posttrans
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          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
  Target Milestone: ---
          Found By: ---
           Blocker: ---

There's currently no integration of dracut with the way the systemd-boot
prototype support works (https://en.opensuse.org/Systemd-boot).
So calling dracut to generate an initrd would lead to the initrd in the wro=
ng
place aka useless. Instead one would have to call "sdbootutil add-kernel" r=
esp
"sdbootutil add-all-kernels".

The interface is still WIP so I wouldn't want to ask for adding those calls
actually. Instead I'd like to have a way to override the script.
The rpm scriptlets are already in a subpackage so I can provide alternative=
s.
How about  moving regenerate-initrd-posttrans there too?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16897563672.CF25430F3.14310
Date: Wed, 19 Jul 2023 08:46: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
          1213459

          Summary
          suse-module-tools: allow to replace regenerate-initrd-posttra=
ns

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.4

          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

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

There's currently no integration of dracut with the way the =
systemd-boot
prototype support works (h=
ttps://en.opensuse.org/Systemd-boot).
So calling dracut to generate an initrd would lead to the initrd in the wro=
ng
place aka useless. Instead one would have to call "sdbootutil add-kern=
el" resp
"sdbootutil add-all-kernels".

The interface is still WIP so I wouldn't want to ask for adding those calls
actually. Instead I'd like to have a way to override the script.
The rpm scriptlets are already in a subpackage so I can provide alternative=
s.
How about  moving regenerate-initrd-posttrans there too?

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

You are on the CC list for the bug.

=

--16897563672.CF25430F3.14310--


body:
--16897583941.E9BE.14391
Date: Wed, 19 Jul 2023 09:19:54 +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=3D1213462

            Bug ID: 1213462
           Summary: VUL-0: chromium: multiple security issues fixed in 115.0.5790.98
    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: security-team-at-suse.de
                CC: gmbr3-at-opensuse.org, m.szczepaniak.000-at-gmail.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

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

CVE-2023-3727: Use after free in WebRTC
CVE-2023-3728: Use after free in WebRTC
CVE-2023-3730: Use after free in Tab Groups
CVE-2023-3732: Out of bounds memory access in Mojo
CVE-2023-3733: Inappropriate implementation in WebApp Installs
CVE-2023-3734: Inappropriate implementation in Picture In Picture
CVE-2023-3735: Inappropriate implementation in Web API Permission Prompts
CVE-2023-3736: Inappropriate implementation in Custom Tabs
CVE-2023-3737: Inappropriate implementation in Notifications
CVE-2023-3738: Inappropriate implementation in Autofill
CVE-2023-3740: Insufficient validation of untrusted input in Themes
Various fixes from internal audits, fuzzing and other initiatives
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16897583941.E9BE.14391
Date: Wed, 19 Jul 2023 09:19:54 +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
          1213462

          Summary
          VUL-0: chromium: multiple security issues fixed in 115.0.5790=
.98

          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
          security-team@suse.de

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

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

https://chromereleases.googleblog.com/=
2023/07/stable-channel-update-for-desktop.html

CVE-2023-3727: Use after free in WebRTC
CVE-2023-3728: Use after free in WebRTC
CVE-2023-3730: Use after free in Tab Groups
CVE-2023-3732: Out of bounds memory access in Mojo
CVE-2023-3733: Inappropriate implementation in WebApp Installs
CVE-2023-3734: Inappropriate implementation in Picture In Picture
CVE-2023-3735: Inappropriate implementation in Web API Permission Prompts
CVE-2023-3736: Inappropriate implementation in Custom Tabs
CVE-2023-3737: Inappropriate implementation in Notifications
CVE-2023-3738: Inappropriate implementation in Autofill
CVE-2023-3740: Insufficient validation of untrusted input in Themes
Various fixes from internal audits, fuzzing and other initiatives

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

You are on the CC list for the bug.

=

--16897583941.E9BE.14391--

pkgs: chromium ungoogled-chromium


body:
--16897584150.693a0a.14400
Date: Wed, 19 Jul 2023 09:20:15 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1213463
           Summary: python310 unreproducible pyc part2
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: bwiedemann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: mcepl-at-suse.com
  Target Milestone: ---
          Found By: Development
           Blocker: ---

After bug 1211765 was fixed, there were still issues with 1-byte-changes
in python310's .pyc files.

Please cherry-pick this fixing commit from 3.11 into 3.10:

commit 6dcfd6c5e3cb46543e82dc3f7234546adf4bb04a
Author: Inada Naoki <songofacandy-at-gmail.com>
Date:   Wed May 4 10:01:15 2022 +0900

    gh-78214: marshal: Stabilize FLAG_REF usage (GH-8226)

    Use FLAG_REF always for interned strings.

    Refcounts of interned string is very unstable.
    When compiling same source, refcounts of interned string in the output =
may
be 1 or >1.
    It makes FLAG_REF usage unstable.

    To help reproducible build, use FLAG_REF for interned string even if
refcnt(obj)=3D=3D1.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16897584150.693a0a.14400
Date: Wed, 19 Jul 2023 09:20:15 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1213463

          Summary
          python310 unreproducible pyc part2

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          All

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          bwiedemann@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          mcepl@suse.com

          Target Milestone
          ---

          Found By
          Development

          Blocker
          ---

After bug 1211765 was fixed, there were=
 still issues with 1-byte-changes
in python310's .pyc files.

Please cherry-pick this fixing commit from 3.11 into 3.10:

commit 6dcfd6c5e3cb46543e82dc3f7234546adf4bb04a
Author: Inada Naoki <songo=
facandy@gmail.com>
Date:   Wed May 4 10:01:15 2022 +0900

    gh-78214: marshal: Stabilize FLAG_REF usage (GH-8226)

    Use FLAG_REF always for interned strings.

    Refcounts of interned string is very unstable.
    When compiling same source, refcounts of interned string in the output =
may
be 1 or >1.
    It makes FLAG_REF usage unstable.

    To help reproducible build, use FLAG_REF for interned string even if
refcnt(obj)=3D=3D1.

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

You are on the CC list for the bug.

=

--16897584150.693a0a.14400--

summary: python310 unreproducible pyc part2


--16898625932.CEda.17104
Date: Thu, 20 Jul 2023 14:16:33 +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=3D1213521

            Bug ID: 1213521
           Summary: shairport-sync: missing dependency: avahi
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: wolfgang.frisch-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

openSUSE:Factory/shairport-sync shairport-sync.spec is missing:
Requires: avahi

Steps to reproduce on a minimal Tumbleweed installation:
# zypper in shairport-sync
# systemctl start shairport-sync

> Failed to start shairport-sync.service: Unit avahi-daemon.service not fou=
nd.

`zypper in avahi` fixes this.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16898625932.CEda.17104
Date: Thu, 20 Jul 2023 14:16:33 +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
          1213521

          Summary
          shairport-sync: missing dependency: avahi

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Sound

          Assignee
          tiwai@suse.com

          Reporter
          wolfgang.frisch@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

openSUSE:Factory/shairport-sync shairport-sync.spec is missi=
ng:
Requires: avahi

Steps to reproduce on a minimal Tumbleweed installation:
# zypper in shairport-sync
# systemctl start shairport-sync

> Failed to start shairport-sync.service: Unit ava=
hi-daemon.service not found.

`zypper in avahi` fixes this.

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

You are on the CC list for the bug.

=

--16898625932.CEda.17104--