body:
--1644319584.E1bAB0.7537
Date: Tue, 8 Feb 2022 11:26:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195675
           Summary: xdmbgrd logos need updating
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dmueller-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Stefan Dirsch made screenshots and it indicates that it isn't using the SUSE
logo from https://brand.suse.com/ but an older incarnation. I'm attching the
screenshots

summary: xdmbgrd logos need updating


--1644335163.E7CA80.23261
Date: Tue, 8 Feb 2022 15:46:03 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195690
           Summary: virsh snapshot-revert broken after libvirt update from 2022-01-25
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: felix.niederwanger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hi there,

after the libvirt update on the 25th of January, `virsh snapshot-revert` and
virt-manager refuse to restore a VM snapshot with the following error:

> error: An error occurred, but the cause is unknown

I have an automatic VM update script in place, which stopped working after
2022-01-24. According to my /var/log/zypp/history, there was a big libvirt
update on the 25th of January, so I shamelessly blame this update :-)

dmesg and the journal do not show any output when running `virsh
snapshot-revert`.

# Reproducer

> phoenix@racetrack-7290:~> virsh snapshot-list sles15sp1
>  Name                 Creation Time               State
> -----------------------------------------------------------
>  fresh                2021-08-09 09:43:00 +0200   shutoff
>  updated-2022-01-20   2022-01-20 12:21:15 +0100   shutoff
>  updated-2022-01-21   2022-01-21 12:21:20 +0100   shutoff
>  updated-2022-01-24   2022-01-24 12:21:02 +0100   shutoff
>
> phoenix@racetrack-7290:~> virsh snapshot-revert --domain sles15sp1 --snapshotname updated-2022-01-24
> error: An error occurred, but the cause is unknown


--1644411424.7D03E1.8051
Date: Wed, 9 Feb 2022 12:57:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195729
           Summary: yast2-registration fails test suite when using ruby 3.1 with jemalloc enabled
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

A ruby 3.1 submission (https://build.opensuse.org/request/show/951956) is being
staged.

Ruby enables jemalloc in this request:

 3+Sun Feb  6 18:40:18 UTC 2022 - Marcus Rueckert <mrueckert-at-suse.de>
 4+
 5+- Build ruby with jemalloc for sle 15 up

 5-%if 0%{?sle_version} >= 150000
 6+%if 0%{?suse_version} >= 1500
 7 %bcond_without jemalloc

Prior to this change, jemalloc was enabled on SLE, but not on Tumbleweed

With this change in, though, yast2-registration fails the test suite with a
segfault:

[   58s] /usr/lib64/ruby/vendor_ruby/3.1.0/suse/connect/yast.rb:10: [BUG]
Segmentation fault at 0x00000000000000


body:
--1644414267.bEd8bc0.4125
Date: Wed, 9 Feb 2022 13:44:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195732
           Summary: munin: missing group www requires
    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: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The munin-cgi-*.service files require the group "wwww", but munin does not
require them and thus they don't get installed and created.

summary: munin: missing group www requires


body:
--1644497753.5DBfC520.15455
Date: Thu, 10 Feb 2022 12:55:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195782
           Summary: [HPC] PETSc module cannot be loaded
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: zed.three-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

With libpetsc_3_14_5-gnu-openmpi4-hpc:

$ module load gnu openmpi/4.1.1 petsc
Lmod has detected the following error:
/usr/share/lmod/moduledeps/gnu-11-openmpi-4/petsc/3.14.5: (petsc/3.14.5): wrong
# args: should be "file isdirectory name"
While processing the following module(s):
    Module fullname  Module Filename
    -------------

summary: [HPC] PETSc module cannot be loaded


--1644508729.e0f3Db0.13879
Date: Thu, 10 Feb 2022 15:58:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195792
           Summary: openssl-1_1 should "Requires" libopenssl1_1
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: zzhou-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

We were facing the following error,

(32/39) Installing: csync2-2.0+git.1600444747.83b3644-1.4.x86_64
[..........done]
Additional rpm output:
/usr/bin/openssl: symbol lookup error: /usr/bin/openssl: undefined symbol:
BIO_f_zlib, version OPENSSL_1_1_0
/usr/bin/openssl: symbol lookup error: /usr/bin/openssl: undefined symbol:
BIO_f_zlib, version OPENSSL_1_1_0

Here is the reproducer:

tw1:~ # rpm -qf /usr/bin/openssl
openssl-1_1-1.1.1l-1.2.x86_64
tw1:~ # rpm -qa libopenssl1_1
libopenssl1_1-1.1.1l-1.1.x86_64
tw1:~ # zypper -n in openssl-1_1
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 2 packages are going to be upgraded:
  openssl openssl-1_1

2 packages to upgrade.
Overall download size: 754.2 KiB. Already cached: 0 B. After the operation,
additional 23.6 KiB will be used.
Continue? [y/n/v/...? shows all options] (y): y
Retrieving package openssl-1_1-1.1.1m-2.1.x86_64
 (1/2), 744.6 KiB (  1.6 MiB unpacked)
Retrieving: openssl-1_1-1.1.1m-2.1.x86_64.rpm
..................................................................[done]
Retrieving package openssl-1.1.1m-1.1.noarch
 (2/2),   9.6 KiB (  246   B unpacked)
Retrieving: openssl-1.1.1m-1.1.noarch.rpm
......................................................................[done]

Checking for file conflicts:
...................................................................................[done]
(1/2) Installing: openssl-1_1-1.1.1m-2.1.x86_64
................................................................[done]
(2/2) Installing: openssl-1.1.1m-1.1.noarch
....................................................................[done]

tw1:~ # openssl
openssl: symbol lookup error: openssl: undefined symbol: BIO_f_zlib, version
OPENSSL_1_1_0

To resolve that, we add one step beforehand to install
libopenssl1_1-1.1.1m-2.1.x86_64.rpm.

Does it rings the bell to add a Requires dependency of openssl-1_1.rpm,
something like, or similar to,
Requires:       libopenssl1_1 = %{version}


--1644510548.bDaa2DE70.22811
Date: Thu, 10 Feb 2022 16:29:08 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195796
           Summary: [HPC, warewulf] - Do not copy Repo Data from Build Host to Chroot when sharing this Data
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: x86-64
                OS: SLES 15
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: eich-at-suse.com
          Reporter: eich-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

TO build a chroot of the same OS as the host, one does not need to specify
package repositories as this data can be shared with the client. This data can
be taken from the installation host. This feature is convenient when building
images for SLE nodes as the registration of the host can be reused.

So far, this data used to be copied. This is not required however when using
the --installroot zypper argument.


body:
--1644656884.7eD3Cc2B0.18984
Date: Sat, 12 Feb 2022 09:08:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195865
           Summary: No mouse pointer after restoring zoom
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: frans-at-fransdb.nl
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The mouse pointer is not restored after returning from the zoom-in function
(meta+=). This happens since the last one or two updates.

The behavior is the same as reported under ID 842128, but differ in that it is
always not restored and switching to text console does not resolve it.

summary: No mouse pointer after restoring zoom


--1644682369.8D1de0.9409
Date: Sat, 12 Feb 2022 16:12:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195873
           Summary: Xpra (4.2.3-15.5) "failed to connect" with "received uninterpretable nonsense" when testing on SAME MACHINE
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: aloisio-at-gmx.com
          Reporter: opensuse@this-house.net
        QA Contact: qa-bugs-at-suse.de
          Found By: Community User
           Blocker: ---

In one (Konsole) terminal . . .
xpra start --daemon=no --start=xterm

(I see "connected to X11 display :1 with 24 bit colors" among the messages)

In a second terminal on the same maching . . .
xpra attach :1

Below is a clip of the output:

. . .
2022-02-12 10:36:55,790 Using accelerated ArrayDatatype
2022-02-12 10:36:55,957 Warning: cannot handle window transparency
2022-02-12 10:36:55,957  screen is not composited
2022-02-12 10:36:55,973 OpenGL enabled with NV136
2022-02-12 10:36:56,908 missing some source information: cannot import name
'COMMIT' from 'xpra.src_info'
(/usr/lib64/python3.8/site-packages/xpra/src_info.py)
2022-02-12 10:36:56,913  keyboard settings: rules=evdev, model=pc105, layout=us
2022-02-12 10:36:57,927  desktop size is 3840x2160 with 1 screen:
2022-02-12 10:36:57,928   :0.0 (1016x571 mm - DPI: 96x96) workarea: 3840x2114
2022-02-12 10:36:57,928     DEL DP-1 (609x349 mm - DPI: 160x157)
2022-02-12 10:36:58,513 Error: failed to connect
2022-02-12 10:36:58,513  received uninterpretable nonsense: 'invalid packet
header byte: 0x646973636f6e6e65 read buffer=b"disconnect: invalid packet header
byte: 0x0101 .. 3\\\\xe5/\\\\xbe\\\\xf8?\\\\x15u\\\\xc7^\' (63593 bytes)\\n"
(186 bytes)'
2022-02-12 10:36:58,513  packet no 0 data: disconnect: invalid packet header
byte: 0x010100 .. .=2`)\x83\xe5/\xbe\xf8?\x15u\xc7^' (63593 bytes)
2022-02-12 10:36:58,529 removing unix domain socket
'/run/user/1000/xpra/clients/ . . .

I suspect the upstream Xpra developer will say something like "The package is
missing a dependency."
Did this package work when it was updated released (this January?)?


--1644763486.17aCA0.22248
Date: Sun, 13 Feb 2022 14:44:46 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195880
           Summary: VUL-0: firejail: private-cwd leaks access to the entire filesystem
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: sebix+novell.com-at-sebix.at
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

It was discovered in firejail before 0.9.68 private-cwd may leak access to the
entire file system

firejail --private --private-cwd=. /usr/bin/sh

References:
https://github.com/netblue30/firejail/issues/4780


--1644913318.7de0E0.1987
Date: Tue, 15 Feb 2022 08:21:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195945
           Summary: [Build 20220213] nvme_checks: nvme read: Device or resource busy
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/2188653/modules/nvme
                    _checks/steps/41
                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
          Found By: openQA
           Blocker: Yes

## Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-nvme@uefi fails in
[nvme_checks](https://openqa.opensuse.org/tests/2188653/modules/nvme_checks/steps/41)

Next one in line, after https://bugzilla.opensuse.org/show_bug.cgi?id=1195637
has been addressed (nvme id-ns)

The test executes
nvme read /dev/nvme0n1 --start-block=0 --block-count=0 --data-size=512
--data=lba.0.read

and receives as a result:
 Device or resource busy
 Failed to open nvme0n1
 Namespace is currently busy
 Use the force [--force] option to ignore that

## Test suite description
Maintainer: rbrown-at-suse.de; Basic installation test to confirm that installing
and booting to an nvme as your root disk works

## Reproducible

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

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=uefi&test=nvme&version=Tumbleweed)


--1644917567.d2034dCa0.17661
Date: Tue, 15 Feb 2022 09:32:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195954
           Summary: VUL-1: CVE-2021-45005: mujs: heap buffer overflow caused by conflicting JumpList of nested try/finally statements
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
               URL: https://smash.suse.de/issue/323776/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: ilya-at-ilya.pp.ua
          Reporter: carlos.lopez-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2021-45005

Artifex MuJS v1.1.3 was discovered to contain a heap buffer overflow which is
caused by conflicting JumpList of nested try/finally statements.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45005
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45005
https://github.com/ccxvii/mujs/commit/df8559e7bdbc6065276e786217eeee70f28fce66
https://bugs.ghostscript.com/show_bug.cgi?id=704749


--1644942677.3e0C00.24097
Date: Tue, 15 Feb 2022 16:31:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195986
           Summary: VUL-0: chromium: multiple security issues fixed in 98.0.4758.102
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: gmbr3-at-opensuse.org
          Reporter: gabriele.sonnu-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: ---
           Blocker: ---

[$15000][1290008] High CVE-2022-0603: Use after free in File Manager. Reported
by Chaoyuan Peng (@ret2happy) on 2022-01-22

[$7000][1273397] High CVE-2022-0604: Heap buffer overflow in Tab Groups.
Reported by Krace on 2021-11-24

[$7000][1286940] High CVE-2022-0605: Use after free in Webstore API. Reported
by Thomas Orlita  on 2022-01-13

[$7000][1288020] High CVE-2022-0606: Use after free in ANGLE. Reported by
Cassidy Kim of Amber Security Lab, OPPO Mobile Telecommunications Corp. Ltd. on
2022-01-17

[$TBD][1250655] High CVE-2022-0607: Use after free in GPU. Reported by 0x74960
on 2021-09-17

[$NA][1270333] High CVE-2022-0608: Integer overflow in Mojo. Reported by Sergei
Glazunov of Google Project Zero on 2021-11-16

[$NA][1296150] High CVE-2022-0609: Use after free in Animation. Reported by
Adam Weidemann and Cl?ment Lecigne of Google's Threat Analysis Group on
2022-02-10

[$TBD][1285449] Medium CVE-2022-0610: Inappropriate implementation in Gamepad
API. Reported by Anonymous on 2022-01-08

We would also like to thank all security researchers that worked with us during
the development cycle to prevent security bugs from ever reaching the stable
channel.

Google is aware of reports that an exploit for CVE-2022-0609 exists in the
wild.As usual, our ongoing internal security work was responsible for a wide
range of fixes:

    [1297168] Various fixes from internal audits, fuzzing and other initiatives


--1644946434.AcBaC0.31251
Date: Tue, 15 Feb 2022 17:33:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1195989
           Summary: VUL-0: CVE-2022-24976: atheme: General authentication bypass in Atheme IRC services with InspIRCd 3
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
               URL: https://smash.suse.de/issue/323711/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: jengelh-at-inai.de
          Reporter: carlos.lopez-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2022-24976

Atheme IRC Services before 7.2.12, when used in conjunction with InspIRCd,
allows authentication bypass by ending an IRC handshake at a certain point
during a challenge-response login sequence.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24976
https://www.openwall.com/lists/oss-security/2022/01/30/4
https://github.com/atheme/atheme/compare/v7.2.11...v7.2.12
https://github.com/inspircd/inspircd/commit/407b2e004cf66e442771ec5d2bbe700dee1f3760
https://github.com/inspircd/inspircd/commit/6703b8065ccaa0acb50380736f25780e3a8e549d
https://github.com/atheme/atheme/commit/4e664c75d0b280a052eb8b5e81aa41944e593c52
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24976


--1645008519.cAb8FCC0.7936
Date: Wed, 16 Feb 2022 10:48:39 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196017
           Summary: LibreOffice fails to build against KDE Frameworks 5.91
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LibreOffice
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

KDE Frameworks has been submitted for inclusion into Tumbleweed; this is
currently all staged in
https://build.opensuse.org/staging_workflows/openSUSE:Factory/staging_projects/openSUSE:Factory:Staging:K

LibreOffice fails to build against this stack:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:K/libreoffice/standard/x86_64

```
[  119s] checking for QT5_GOBJECT... yes
[  119s] checking for kf5-config... no
[  119s] checking for KF5 headers... no
[  119s] configure: error: KF5 headers not found.  Please specify the root of
your KF5 installation by exporting KF5DIR before running "configure".
[  119s] error: Bad exit status from /var/tmp/rpm-tmp.77XFO4 (%build)
[  119s]
[  119s]
```


body:
--1645029585.866F12.31965
Date: Wed, 16 Feb 2022 16:39:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196047
           Summary: pyenv conflicts with fish3 on
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          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: ---

Generated from
http://botmaster.suse.de:8153/go/tab/build/detail/AdiChecker.Backports.SLE-15-SP4/1207/Run/1/Run#tab-console

### [install check & file conflicts for x86_64]

found conflict of fish3-3.3.1-bp154.5.1.x86_64 with
pyenv-fish-completion-1.2.9-bp154.1.4.noarch
  /usr/share/fish/completions/pyenv.fish

Can we please get the conflict resolved? this blocks us from the fish3 update
that was requested by community.

Thank you

summary: pyenv conflicts with fish3 on


--1645089380.8D252.19627
Date: Thu, 17 Feb 2022 09:16:20 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196072
           Summary: VUL-0: MozillaThunderbird: Crafted email could trigger an out-of-bounds write
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: martin.sirringhaus-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: security-team-at-suse.de
                CC: wolfgang-at-rosenauer.org
          Found By: Security Response Team
           Blocker: ---

It may be possible for an attacker to craft an email message that causes
Thunderbird to perform an out-of-bounds write of one byte when processing the
message.

Fixed in 91.6.1

References:
https://www.mozilla.org/en-US/security/advisories/mfsa2022-07/#CVE-2022-0566
https://bugzilla.mozilla.org/show_bug.cgi?id=1753094


--1645110356.4b06Ee6.27848
Date: Thu, 17 Feb 2022 15:05:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196096
           Summary: wireguard-tools: Systemd service hardening breaks dns configuration
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dheidler-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

#ProtectSystem=full
#ProtectHome=false
#ProtectHostname=true
#ProtectKernelModules=true
#ProtectKernelLogs=true
#ProtectControlGroups=true
#RestrictRealtime=true

The dns configuration in wg-quick only works when commenting out these entries
in the service file.

wg-quick will do these crude steps to set the dns for the tunnel:

set_dns() {
    [[ ${#DNS[@]} -gt 0 ]] || return 0

    if [[ $(resolvconf --version 2>/dev/null) == openresolv\ * ]]; then
        { printf 'nameserver %s\n' "${DNS[@]}"
          [[ ${#DNS_SEARCH[@]} -eq 0 ]] || printf 'search %s\n'
"${DNS_SEARCH[*]}"
        } | cmd resolvconf -a "$INTERFACE" -m 0 -x
    else
        echo "[#] mount \`${DNS[*]}' /etc/resolv.conf" >&2
        [[ -e /etc/resolv.conf ]] || touch /etc/resolv.conf
        { cat <<-_EOF
            # This file was generated by wg-quick(8) for use with
            # the WireGuard interface $INTERFACE. It cannot be
            # removed or altered directly. You may remove this file
            # by running \`wg-quick down $INTERFACE', or if that
            # poses problems, run \`umount /etc/resolv.conf'.

        _EOF
        printf 'nameserver %s\n' "${DNS[@]}"
        [[ ${#DNS_SEARCH[@]} -eq 0 ]] || printf 'search %s\n'
"${DNS_SEARCH[*]}"
        } | unshare -m --propagation shared bash -c "$(cat <<-_EOF
            set -e
            context="\$(stat -c %C /etc/resolv.conf 2>/dev/null)" || unset
context
            mount --make-private /dev/shm
            mount -t tmpfs none /dev/shm
            cat > /dev/shm/resolv.conf
            [[ -z \$context || \$context == "?" ]] || chcon "\$context"
/dev/shm/resolv.conf 2>/dev/null || true
            mount -o remount,ro /dev/shm
            mount -o bind,ro /dev/shm/resolv.conf /etc/resolv.conf
        _EOF
        )"
    fi


--1645180771.AEc707.2314
Date: Fri, 18 Feb 2022 10:39:31 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196145
           Summary: AUDIT-0:  network:cluster/apptainer: apptainer is the successor of singularity
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: cgoll-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

apptainer is the opensource successor for singularity. Due to name change a new
review is needed.


body:
--1645186497.C54aff530.24153
Date: Fri, 18 Feb 2022 12:14:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196156
           Summary: info now recommend texinfo
    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: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Change happened in https://build.opensuse.org/request/show/955207

With this, 'info' no recommends 'texinfo-lang', which in turn requires texinfo
and that then pulls in a whole pletora of texlive packages on all default
installs.

summary: info now recommend texinfo


body:
--1645272891.2f32Cd0.16633
Date: Sat, 19 Feb 2022 12:14:51 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196198
           Summary: libdwarf-devel installation fails
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: dmueller-at-suse.com
          Reporter: jengelh-at-inai.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

( 77/186) Installing: libdwarf-tools-0.3.3-1.1.x86_64
............................................................................[done]
error: unpacking of archive failed on file /usr/include/libdwarf;6210de03:
cpio: File from package already exists as a directory in system
error: libdwarf-devel-0.3.3-1.1.x86_64: install failed
error: libdwarf-devel-20210528-1.4.x86_64: erase skipped
( 78/186) Installing: libdwarf-devel-0.3.3-1.1.x86_64
...........................................................................[error]
Installation of libdwarf-devel-0.3.3-1.1.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a): ^Z

You can't replace /usr/include/libdwarf (directory) by a non-directory.

summary: libdwarf-devel installation fails


--1645275995.CA4Cd3C30.20743
Date: Sat, 19 Feb 2022 13:06:35 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196199
           Summary: Update references to download.kde.org in knewstuff components
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: fabian@ritter-vogt.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

download.kde.org and distribute.kde.org can no longer be used as OCS provider
endpoints. They were removed after multiple bugs in discover lead to an
effective DDoS on the infrastructure. The endpoints on the CDN need to be used
instead.

Discover 5.18 does not include the component affected by the bugs, so we just
need to backport the URL changes.


body:
--1645299797.0BC0134.5286
Date: Sat, 19 Feb 2022 19:43:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196205
           Summary: Tracker  extractor does not start
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: gnome-bugs-at-suse.de
          Reporter: petr-at-jevklidu.cz
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Gnome indexing stopped working after upgrade to latest Thumbleweed.

There is a message in log:
systemd[2756]: Failed to start Tracker metadata extractor.

When I try run it manually, t show:

/usr/libexec/tracker-extract-3
[1]    10029 invalid system call (core dumped)  /usr/libexec/tracker-extract-3

package version is tracker-miners-3.2.1-3.3

when I look at strace it looks like there is a problem with extracting metadata
from flac and m4a files. When I move all that files outside of indexing
directory and restart service with:

systemctl --user restart tracker-extract-3.service

it runs again without crash.

summary: Tracker  extractor does not start


--1645310374.1BE186ca0.10136
Date: Sat, 19 Feb 2022 22:39:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196206
           Summary: The user session log file for SDDM no longer contains any messages - ~/.local/share/sddm/xorg-session.log
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: jinesh-at-onelittlehope.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I don't know when this issue started but the user session log file created by
SDDM (https://man.archlinux.org/man/sddm.conf.5.en#SessionLogFile=) has stopped
collecting any messages from X applications.

The messages are not going into journald or
/var/lib/sddm/.local/share/sddm/xorg-session.log or /var/log/Xorg.0.log.


--1645400627.252E71.15566
Date: Sun, 20 Feb 2022 23:43:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196214
           Summary: tigervnc 1.12.0 vncviewer segfaults if the window is closed while one or more keys are held down
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: opensuse-at-arnavion.dev
        QA Contact: qa-bugs-at-suse.de
                CC: dleuenberger-at-suse.com, joan.torres-at-suse.com,
                    sndirsch-at-suse.com
          Found By: ---
           Blocker: ---

tigervnc-1.12.0-1.1

The easiest repro is:

1. Use `vncviewer some_host` to open a VNC connection to some_host

2. Use key combo to close the VNC Viewer window while it's focused. In my case
   the combo is Mod4-Shift-Q because I'm running sway.

3. VNC Viewer segfaults. `coredumpctl gdb /usr/bin/vncviewer-tigervnc` says:

    (gdb) bt
    #0  0x000055af59595761 in rfb::CMsgWriter::writeKeyEvent (this=0x0,
keysym=65505, keycode=42, down=false) at
/usr/src/debug/tigervnc-1.12.0-1.1.x86_64/common/rfb/CMsgWriter.cxx:150
    #1  0x000055af59588d0b in Viewport::~Viewport (this=<optimized out>,
this=<optimized out>) at /usr/include/c++/11/bits/stl_tree.h:281
    #2  0x000055af59579fe7 in Viewport::~Viewport (this=<optimized out>,
this=<optimized out>) at
/usr/src/debug/tigervnc-1.12.0-1.1.x86_64/vncviewer/Viewport.cxx:193
    #3  DesktopWindow::~DesktopWindow (this=<optimized out>, this=<optimized
out>) at
/usr/src/debug/tigervnc-1.12.0-1.1.x86_64/vncviewer/DesktopWindow.cxx:239
    #4  0x000055af5958169d in DesktopWindow::~DesktopWindow (this=<optimized
out>, this=<optimized out>) at
/usr/src/debug/tigervnc-1.12.0-1.1.x86_64/vncviewer/DesktopWindow.cxx:220
    #5  CConn::~CConn (this=<optimized out>, this=<optimized out>) at
/usr/src/debug/tigervnc-1.12.0-1.1.x86_64/vncviewer/CConn.cxx:138
    #6  0x000055af59581779 in CConn::~CConn (this=<optimized out>,
this=<optimized out>) at
/usr/src/debug/tigervnc-1.12.0-1.1.x86_64/vncviewer/CConn.cxx:144
    #7  0x000055af59575afa in mainloop (vncserver=0x55af595d6660
<vncServerName> "[::1]:5903", sock=0x0) at
/usr/src/debug/tigervnc-1.12.0-1.1.x86_64/vncviewer/vncviewer.cxx:195
    #8  main (argc=<optimized out>, argv=0x7ffc3a8666e8) at
/usr/src/debug/tigervnc-1.12.0-1.1.x86_64/vncviewer/vncviewer.cxx:849

The cause is `cc->writer()->writeKeyEvent()` being called in
`ViewPort::~ViewPort` but `cc->writer()` is NULL at this point. This code is
not present in upstream; it's added by TW-specific patch
tigervnc-clean-pressed-key-on-exit.patch. The problem did not happen with
the previous version 1.10.1 which also had the patch, so perhaps the patch
needs to be modified to work with 1.12.0

The issue occurs if any key is held down while the window is closed,
not necessarily the key combo itself closes the window. For example, I can run
`sleep 5; swaymsg kill` in a terminal which will close the focused window in
5s,
then switch to the vncviewer window and hold some key like Ctrl down, and when
the window closes in 5s vncviewer will segfault in the same way.


--1645435431.31aC2EE12.4729
Date: Mon, 21 Feb 2022 09:23:51 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196228
           Summary: Leap 15.4 autologin failed: sddm uses wrong path /usr/etc: Auth: sddm-helper exited with 2
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: lubos.kocman-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

sddm[1076]: Auth: sddm-helper exited with 2

Probably because it uses /usr/etc/ as path, which is wrong

Bug 1195679 is tracking the issue with macro itself, however Stefan Weiberg
said that the plan is to revert usage of %{_distconfdir}  from all packages
including systemd and sddm (this particular bug).

SLE will have %{_distconfdir}  set to /etc until issues in individual packages
get resolved.

This is an tracker to resolve it (remove the macro usage) for sddm.


--1645440561.c2D74Fce2.21575
Date: Mon, 21 Feb 2022 10:49:21 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196236
           Summary: VUL-0: CVE-2022-0699: shapelib: Double-free vulnerability in contrib/shpsort.c
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
               URL: https://smash.suse.de/issue/324410/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: opensuse-at-dstoecker.de
          Reporter: carlos.lopez-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#2054305

A double-free condition exists in contrib/shpsort.c of shapelib 1.5.0 and older
releases. This issue may allow an attacker to cause a denial of service or have
other unspecified impact via control over malloc.

Upstream issue:
https://github.com/OSGeo/shapelib/issues/39

Upstream commit:
https://github.com/OSGeo/shapelib/commit/c75b9281a5b9452d92e1682bdfe6019a13ed819f

References:
https://bugzilla.redhat.com/show_bug.cgi?id=2054305
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0699


--1645604843.ae4F0.13828
Date: Wed, 23 Feb 2022 08:27:23 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196322
           Summary: systemd-resolved.service fails with status=217/USER
    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: karl.mistelberger-at-nefkom.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

From journal:
notebook:~ # journalctl -b -g systemd-resolve -o short-monotonic
[    4.128451] notebook systemd-tmpfiles[649]:
/usr/lib/tmpfiles.d/systemd-resolve.conf:10: Duplicate line for path
"/etc/resolv.conf", ignoring.
[    4.236423] notebook dbus-daemon[691]: dbus[691]: Unknown username
"systemd-resolve" in message bus configuration file
[  111.859591] notebook systemd[2201]: systemd-resolved.service: Failed to
determine user credentials: No such process
[  111.859873] notebook systemd[2201]: systemd-resolved.service: Failed at step
USER spawning /usr/lib/systemd/systemd-resolved: No such process
[  111.859945] notebook systemd[1]: systemd-resolved.service: Main process
exited, code=exited, status=217/USER
[  111.860049] notebook systemd[1]: systemd-resolved.service: Failed with
result 'exit-code'.
[  111.861079] notebook systemd[1]: systemd-resolved.service: Scheduled restart
job, restart counter is at 1.
...
[  111.874320] notebook systemd[2215]: systemd-resolved.service: Failed to
determine user credentials: No such process
[  111.874646] notebook systemd[2215]: systemd-resolved.service: Failed at step
USER spawning /usr/lib/systemd/systemd-resolved: No such process
[  111.874882] notebook systemd[1]: systemd-resolved.service: Main process
exited, code=exited, status=217/USER
[  111.875044] notebook systemd[1]: systemd-resolved.service: Failed with
result 'exit-code'.
[  111.875878] notebook systemd[1]: systemd-resolved.service: Scheduled restart
job, restart counter is at 5.
[  111.876084] notebook systemd[1]: systemd-resolved.service: Start request
repeated too quickly.
[  111.876153] notebook systemd[1]: systemd-resolved.service: Failed with
result 'exit-code'.
notebook:~ #


body:
--1645628544.db5c40.1435
Date: Wed, 23 Feb 2022 15:02:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196359
           Summary: Most systemd units should not Want= or Require= network.target
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: Ulrich.Windl-at-rz.uni-regensburg.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I noticed that some units Wants= or Require= "network.target", but as I
understand it, that target should be used mostly for ordering of services (thus
not be "required").

Examples: chrony and ntpd Want=network.target
rpc-statd-notify.service Requires=network.target

Probably both of the above should have After=network.target instead.

pkgs: mednafen-server rp-pppoe


body:
--1645706816.F2fEd0.12541
Date: Thu, 24 Feb 2022 12:46:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196438
           Summary: Consider switching to 300HZ default
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: dmueller-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I recently stumbled over the 300 HZ option in the kernel
configuration. Currently we are using 250 HZ with IDLE_HZ. The HZ
setting is used
as far as I can see to determine when jiffies are advancing, so it
influences the granularity of a couple of things like kvmclock, timers
and so on. Also
USER_HZ is 100 HZ which is the granularity to which some metrics are
exported to user space. 300 is divisible without remainder by 100,
unlike 250.

so it appears there are good reasons for switching the default, and it
is "just" 20% more timer interrupts than before, so it should not be a
huge issue. I also
did a test build and a 300 HZ kernel is by a few bytes smaller than a
250 HZ kernel, indicating that the compiler can optimize away a few
things.

I am seeing an increase in a few small functions, and I'm looking into
making the code size increase go away with a source level tweak. I've
benchmarked both versions in a micro
benchmark that does a billion invocations of both, and while the code
is larger, it runs in exactly the same runtime (+/- 3% which I
consider my benchmark noise level) on a Ryzen Zen 2+.

In the Kconfig description of 300 HZ option, it appears this is more
recommended for multimedia usecases because it is divisible without
remainder for common rates, like 30 (fps), 60 fps , 120 fps, 44.1khZ
and others that are often needed.
This is imho not only usable for desktop, but also for servers that
are using multimedia related applications.

I've seen that fedora-like distributions use 1000 HZ, arch linux uses
300 Hz and debian defaults to 250 HZ. So there is no clear trend. I'd
be fine with 300 or 1000 HZ.

Comments? Would like to hear your feedback before sending a change to
the Tumbleweed configs.

summary: Consider switching to 300HZ default


--1645715324.befEcd80.1407
Date: Thu, 24 Feb 2022 15:08:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196459
           Summary: Simple Screen Recorder missing appstream metadata
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: sayan-at-e.email
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Searching for Simple Screen Recorder in KDE Plasma Discover or Gnome Software
does not show the package although it can be installed using YAST or through
zypper from terminal.


--1645722731.74f5D6470.13756
Date: Thu, 24 Feb 2022 17:12:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196467
           Summary: klogd.service: Standard output type syslog is obsolete
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: oliver-at-schwabedissen.name
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,

with every update of klogd I'm getting these messages in /var/log/messages:

2022-02-22T06:38:51.255738+01:00 frodo systemd[1]:
/usr/lib/systemd/system/klogd.service:42: Standard output type syslog is
obsolete, automatically updating to journal. Please update your unit file, and
consider removing the setting altogether.
2022-02-22T06:38:51.256108+01:00 frodo systemd[1]:
/usr/lib/systemd/system/klogd.service:43: Standard output type syslog is
obsolete, automatically updating to journal. Please update your unit file, and
consider removing the setting altogether.

So each time I edit /usr/lib/systemd/system/klogd.service and change the lines

StandardOutput=syslog
StandardError=syslog

to

StandardOutput=journal
StandardError=journal

As "syslog" is obsolete, why aren't the parameters changed to "journal"?


--1645794034.CBFa50.28812
Date: Fri, 25 Feb 2022 13:00:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196493
           Summary: VUL-0: CVE-2022-25643: seatd-launch: allows file deletion with escalated privledges
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: sndirsch-at-suse.com
          Reporter: gianluca.gabrielli-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: jubalh-at-iodoru.org
          Found By: ---
           Blocker: ---

seatd-launch in seatd 0.6.x before 0.6.4 allows removing files with
escalated privileges when installed setuid root. The attack vector is
a user-supplied socket pathname.

https://security-tracker.debian.org/tracker/CVE-2022-25643
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25643
https://lists.sr.ht/~kennylevinsen/seatd-announce/%3CETEO7R.QG8B1KGD531R1%40kl.wtf%3E


--1646039938.3D2CAaa30.23325
Date: Mon, 28 Feb 2022 09:18:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196542
           Summary: Upgrading Firejail version to 0.9.68 prevents connection to web pages
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: 64bit
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: listsetc-at-btopenworld.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Updating of firejail to version 0.9.68 in Main Repository results in "Server
Not Found" messages on attempting to load web pages. Reversion to version
0.9.64 (by a roll back) allows normal web browsing as before.

After upgrading again to version 0.9.68, adding the line
whitelist /run/netconfig/resolv.conf
to the file /etc//firejail/whitelist-run-common.inc corrects the problem and
allows use of the current version of firejail

This solution is suggested by the firejail suport group at
https://github.com/netblue30/firejail/issues/4954


body:
--1646041912.6356fbFF0.28524
Date: Mon, 28 Feb 2022 09:51:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196545
           Summary: GCC 12: xen package fails
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: martin.liska-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The package fails here:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:Gcc7/xen/standard/x86_64

due to:

[  127s] iommu_intr.c: In function 'amd_iommu_free_intremap_table':
[  127s]
/home/abuild/rpmbuild/BUILD/xen-4.16.0-testing/tools/firmware/xen-dir/xen-root/xen/include/asm/mm.h:20:32:
error: array subscript 0 is outside array bounds of 'struct page_info[0]'
[-Werror=array-bounds]
[  127s]    20 | #define PFN_ORDER(_pfn) ((_pfn)->v.free.order)

Note the warning is fuzzy, thus I would recommend disabling it for now.

summary: GCC 12: xen package fails


body:
--1646053137.d8fe3f0.23219
Date: Mon, 28 Feb 2022 12:58:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196553
           Summary: Initial Request for Release Notes
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Release Notes
          Assignee: lukas.kucharczyk-at-suse.com
          Reporter: fs-at-suse.com
        QA Contact: lubos.kocman-at-suse.com
          Found By: ---
           Blocker: ---

Initial 15.4 release notes build. Tracker bug.

summary: Initial Request for Release Notes


--1646087571.28e20.26528
Date: Mon, 28 Feb 2022 22:32:51 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196567
           Summary: Removing systemd-sysvcompat can break default target on older installations
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: aaronpuchert@alice-dsl.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since I didn't have anything in /etc/init.d/, I removed systemd-sysvcompat. But
then reboot landed my in a rescue shell. Reason: the default target was still
set to runlevel5.target, which no longer existed. I can't remember changing the
default target, but my installation goes back a few years. So who knows.

Perhaps we should have some kind of mechanism that either prevents removing the
package if the default is still a runlevel*.target, or just silently "fixes" it
by forwarding to the underlying systemd target.

Apparently "systemctl get-default" looks through symlinks and the runlevel*
targets are just symlinks to standard systemd targets, so we can't use that
command. Instead we probably need to check whether
/etc/systemd/system/default.target exists and what it points to.


--1646143852.c835BBf0.15980
Date: Tue, 1 Mar 2022 14:10:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196613
           Summary: pam-config doesn't handle /usr/etc properly
    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: fcrozat-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

This might be a follow-up of bsc#1187091

on a freshly installed openSUSE MicroOS desktop, I've tried to enable
pam_config:

pam-config --service login -a --mount

pam-config complained there was no /etc/pam.d/login and created one, which was
broken (couldn't login anymore)

It should have checked the presence of /usr/etc/pam.d/login and use this file
as "reference".

Workaround:
cp /usr/etc/pam.d/login /etc/pam.d/login
and run pam-config


body:
--1646153658.6FDD1.10537
Date: Tue, 1 Mar 2022 16:54:18 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196621
           Summary: AUDIT-0: usbguard: review of dbus service org.usbguard1.service and polkit rules
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: rfrohl-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

user requested to enable dbus support to usbguard. Some output for this
endeavor:

> [   98s] usbguard.x86_64: E: polkit-user-privilege (Badness: 10) org.usbguard.Policy1.listRules (no:no:auth_self_keep)
> [   98s] usbguard.x86_64: E: polkit-user-privilege (Badness: 10) org.usbguard.Devices1.listDevices (no:no:auth_self_keep)
> [   98s] usbguard.x86_64: E: polkit-user-privilege (Badness: 10) org.usbguard1.getParameter (no:no:auth_self_keep)

> [   98s] usbguard.x86_64: E: polkit-untracked-privilege (Badness: 10) org.usbguard.Policy1.appendRule (no:no:auth_admin)
> [   98s] usbguard.x86_64: E: polkit-untracked-privilege (Badness: 10) org.usbguard.Policy1.removeRule (no:no:auth_admin)
> [   98s] usbguard.x86_64: E: polkit-untracked-privilege (Badness: 10) org.usbguard.Devices1.applyDevicePolicy (no:no:auth_admin)
> [   98s] usbguard.x86_64: E: polkit-untracked-privilege (Badness: 10) org.usbguard1.setParameter (no:no:auth_admin)

> %{_datadir}/dbus-1/system-services/org.usbguard1.service
%{_datadir}/dbus-1/system.d/org.usbguard1.conf
%{_datadir}/polkit-1/actions/org.usbguard1.policy
> [   98s] usbguard.x86_64: E: dbus-file-unauthorized (Badness: 10) /usr/share/dbus-1/system.d/org.usbguard1.conf

pkgs: polkit-default-privs rpmlint


body:
--1646206157.D7cF0.26484
Date: Wed, 2 Mar 2022 07:29:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196630
           Summary: SCC: Leap 15.4 repos are not published
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          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 SCC team,

Lemon reached out to me today, regarding an issue with unpublished repos.

We do track only few SCC related tasks

Specifically  (initial ask to be present in SCC)
https://github.com/openSUSE/openSUSE-release-process/blob/master/Alpha.md#ask-for-scc-enablement

and that's pretty much it. I'm aware of a change from Beta to GA in SCC,
however I was not aware of any explicit ask for publish or at what point in
release process should it be requested.

Perhaps we should refine steps for Leap to ensure that they match reality.

lkocman@localhost:~/Workspace/opensuse/openSUSE-release-process> git grep -i
scc
Alpha.md:Blocks: ask for scc enablement
Alpha.md:#### ask for scc enablement
Alpha.md:openSUSE.product produces a product called "openSUSE" from vendor
"openSUSE". What we actually have are products called "Leap" and Tumbleweed"
from vendor "openSUSE" though. In order to properly support SCC registration
the information OBS has needs to be consistent. Therefore it's desirable to
rename the product from openSUSE to Leap.
conf/openSUSE-Leap-15.3.conf:scc = lkocman
conf/openSUSE-Leap-15.4.conf:scc = lkocman
redmine/redmine-export-openSUSE-Leap-15.2-20200211.csv:56093,openSUSE Leap
15.2,action,"",Closed,Normal,ask for scc enablement,lnussel,lnussel,02/09/2019
12:18 pm,Release Engineering,Alpha,29/08/2019,05/09/2019,"",0.00,100,29/08/2019
11:17 am,02/09/2019 12:18 pm,"",No,""
redmine/redmine-export-openSUSE-Leap-15.2-20200211.csv:openSUSE.product
produces a product called ""openSUSE"" from vendor ""openSUSE"". What we
actually have are products called ""Leap"" and Tumbleweed"" from vendor
""openSUSE"" though. In order to properly support SCC registration the
information OBS has needs to be consistent. Therefore it's desirable to rename
the product from openSUSE to Leap.
lines 1-7/7 (END)

summary: SCC: Leap 15.4 repos are not published


--1646216196.DCB32F7B1.21480
Date: Wed, 2 Mar 2022 10:16:36 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196638
           Summary: VUL-1: CVE-2022-0577: python-Scrapy: Exposure of Sensitive Information to an Unauthorized Actor
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
               URL: https://smash.suse.de/issue/325125/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: abergmann-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2022-0577

Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository
scrapy/scrapy prior to 2.6.1.

Only Factory is affected:

SUSE:Factory:Head  python-Scrapy

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0577
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0577
https://github.com/scrapy/scrapy/commit/8ce01b3b76d4634f55067d6cfdf632ec70ba304a
https://huntr.dev/bounties/3da527b1-2348-4f69-9e88-2e11a96ac585


body:
--1646218243.12fbEb0.29206
Date: Wed, 2 Mar 2022 10:50:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196640
           Summary: Mesa-drivers fails to build on ppc64
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: gfx-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: gfx-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since the update of Mesa to version 21.3.7, the version fails to build for
ppc64 (PPC and ppc64le are fine)

https://build.opensuse.org/package/show/openSUSE:Factory:PowerPC/Mesa-drivers

This results in the DVD not being able to be calculated as a blocking
side-effect:
[   11s] Mar-01 20:28:08 <2> : [W]    patterns-desktop-imaging uninstallable:
nothing provides Mesa-dri = 21.3.7 needed by Mesa-21.3.7-302.1.ppc64 not
available for ppc64 nor its fallbacks

The build actually fails with:

[ 1128s] [ 1115.228353][ T8944] Out of memory: Killed process 8575 (cc1plus)
total-vm:778752kB, anon-rss:532864kB, file-rss:0kB, shmem-rss:0kB, UID:399
pgtables:152kB oom_score_adj:0

(I'll try to retrigger it a few times; with some luck I end up on a worker with
sufficient memory - a reliably constraints file for PPC would be the solution)

summary: Mesa-drivers fails to build on ppc64


--1646218861.aEcaB6c80.969
Date: Wed, 2 Mar 2022 11:01:01 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196641
           Summary: VUL-0: chromium: multiple security issues fixed in 99.0.4844.51
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: gianluca.gabrielli-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

[$10000][1289383] High CVE-2022-0789: Heap buffer overflow in ANGLE. Reported
by SeongHwan Park (SeHwa)
[$7000][1274077] High CVE-2022-0790: Use after free in Cast UI. Reported by
Anonymous
[$7000][1278322] High CVE-2022-0791: Use after free in Omnibox. Reported by
Zhihua Yao of KunLun Lab
[$7000][1285885] High CVE-2022-0792: Out of bounds read in ANGLE. Reported by
Jaehun Jeong(@n3sk) of Theori
[$7000][1291728] High CVE-2022-0793: Use after free in Views. Reported by
Thomas Orlita
[$7000][1294097] High CVE-2022-0794: Use after free in WebShare. Reported by
Khalil Zhani
[$5000][1282782] High CVE-2022-0795: Type Confusion in Blink Layout. Reported
by 0x74960
[$5000][1295786] High CVE-2022-0796: Use after free in Media. Reported by
Cassidy Kim of Amber Security Lab, OPPO Mobile Telecommunications Corp. Ltd.
[$NA][1281908] High CVE-2022-0797: Out of bounds memory access in Mojo.
Reported by Sergei Glazunov of Google Project Zero
[$15000][1283402] Medium CVE-2022-0798: Use after free in MediaStream. Reported
by Samet Bekmezci @sametbekmezci
[$10000][1279188] Medium CVE-2022-0799: Insufficient policy enforcement in
Installer. Reported by Abdelhamid Naceri (halov)
[$7000][1242962] Medium CVE-2022-0800: Heap buffer overflow in Cast UI.
Reported by Khalil Zhani
[$5000][1231037] Medium CVE-2022-0801: Inappropriate implementation in HTML
parser. Reported by Micha?? Bentkowski of Securitum
[$3000][1270052] Medium CVE-2022-0802: Inappropriate implementation in Full
screen mode. Reported by Irvan Kurniawan (sourc7)
[$3000][1280233] Medium CVE-2022-0803: Inappropriate implementation in
Permissions. Reported by Abdulla Aldoseri
[$2500][1264561] Medium CVE-2022-0804: Inappropriate implementation in Full
screen mode. Reported by Irvan Kurniawan (sourc7)
[$2000][1290700] Medium CVE-2022-0805: Use after free in Browser Switcher.
Reported by raven at KunLun Lab
[$1000][1283434] Medium CVE-2022-0806: Data leak in Canvas. Reported by Paril
[$TBD][1287364] Medium CVE-2022-0807: Inappropriate implementation in Autofill.
Reported by Alesandro Ortiz
[$TBD][1292271] Medium CVE-2022-0808: Use after free in Chrome OS Shell.
Reported by @ginggilBesel
[$TBD][1293428] Medium CVE-2022-0809: Out of bounds memory access in WebXR.
Reported by @uwu7586


--1646293494.1aDfC6A50.3898
Date: Thu, 3 Mar 2022 07:44:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196685
           Summary: nothing provides 'ffmpeg-3' needed by the to be installed audacity-2.2.2-bp153.3.3.1.x86_64
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: michael.nickol@t-online.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

running openSUSE Leap 15.3:

cannot update (or install) audacity after last update:

 zypper lr -u
Repository priorities are without effect. All enabled repositories share the
same priority.

#  | Alias                       | Name
                        | Enabled | GPG Check | Refresh | URI
---+-----------------------------+----------------------------------------------------------------------+---------+-----------+---------+------------------------------------------------------------------------
 1 | repo-backports-debug-update | Update repository of openSUSE Backports
(Debug)                      | No      | --


--1646299598.cb711.15105
Date: Thu, 3 Mar 2022 09:26:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196692
           Summary: VUL-0: CVE-2022-0730: cacti: Authentication bypass under certain LDAP server environments
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
               URL: https://smash.suse.de/issue/325216/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: Andreas.Stieger-at-gmx.de
          Reporter: thomas.leroy-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#2057106

Under certain ldap conditions, Cacti authentication can be bypassed with
certain credential types.

References:

https://github.com/Cacti/cacti/issues/4562

References:
https://bugzilla.redhat.com/show_bug.cgi?id=2057106
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0730


--1646320169.1E116cFa1.11234
Date: Thu, 3 Mar 2022 15:09:29 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196707
           Summary: lxqt-config-appearance  fails to open due to missing liblxqt-config-cursor.so
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LXQt
          Assignee: mvetter-at-suse.com
          Reporter: slemke-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

slemke@notebook:~> zypper info lxqt-config
Loading repository data...
Reading installed packages...

Information for package lxqt-config:
------------------------------------
Repository     : Main Repository
Name           : lxqt-config
Version        : 1.0.0-bp154.1.1
Arch           : x86_64
Vendor         : openSUSE
Installed Size : 1.3 MiB
Installed      : Yes (automatically)
Status         : up-to-date
Source package : lxqt-config-1.0.0-bp154.1.1.src
Upstream URL   : http://www.lxqt.org
Summary        : LXQt Control Center
Description    :
    System Configuration and Control Center for LXQt
slemke@notebook:~>

slemke@notebook:~> lxqt-config-appearance
lxqt-config-appearance: error while loading shared libraries:
liblxqt-config-cursor.so: cannot open shared object file: No such file or
directory
slemke@notebook:~>

Some maybe useful outputs:
slemke@notebook:~> rpm -qa |grep -i lxqt |grep -c 1.0.0
25

slemke@notebook:~> rpm -qa |grep -ic lxqt
35

slemke@notebook:~> rpm -qa |grep -i lxqt |grep -v 1.0.0
patterns-lxqt-lxqt-20170319-lp154.1.2.x86_64
lxqt-theme-openSUSE-default-0.1-bp154.1.2.noarch
lxqt-globalkeys-1.0.1-bp154.1.1.x86_64
lxqt-theme-openSUSE-leaper-0.1-bp154.1.2.noarch
lxqt-globalkeys-lang-1.0.1-bp154.1.1.noarch
lxqt-archiver-0.5.0-bp154.1.1.x86_64
lxqt-archiver-lang-0.5.0-bp154.1.1.noarch
liblxqt-globalkeys-ui1-1.0.1-bp154.1.1.x86_64
liblxqt-globalkeys1-1.0.1-bp154.1.1.x86_64
lxqt-theme-openSUSE-light-0.1-bp154.1.2.noarch
slemke@notebook:~>


--1646398818.88ad58d0.18175
Date: Fri, 4 Mar 2022 13:00:18 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196758
           Summary: [Build 20220303] openvswitch not buildable
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/2225985/modules/open
                    vswitch_ssl/steps/12
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: openQA
           Blocker: Yes

## Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_misc@64bit
fails in
[openvswitch_ssl](https://openqa.opensuse.org/tests/2225985/modules/openvswitch_ssl/steps/12)

standard             x86_64     unresolvable:
      nothing provides dpdk-devel < 19.12
      (got version 21.11-1.1)

dpdk has been updated, openvswitch had a submission, but that one is/was not
acceptable

## Test suite description
Maintainer: zluo-at-suse.de
--
Tests: iotop, gd, perf and journalctlLevels --
see poo#93820 for details

## Reproducible

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

## Expected result

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

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=extra_tests_misc&version=Tumbleweed)


--1646463150.8B4Eae1.7725
Date: Sat, 5 Mar 2022 06:52:30 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196784
           Summary: [>=2.4.5] Fix to CVE-2022-25236 breaks biboumi, ClairMeta, jxmlease, libwbxml, openleadr-python, rnv, xmltodict
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: david.anes-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

It appears the recent security update for expat has broken many systems.

See https://github.com/libexpat/libexpat/issues/572


--1646647243.7a087cD81.16172
Date: Mon, 7 Mar 2022 10:00:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196814
           Summary: VUL-0: CVE-2022-26505: minidlna: DNS rebinding in v1.3.0 and below
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
               URL: https://smash.suse.de/issue/325418/
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: ro-at-suse.de
          Reporter: thomas.leroy-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2022-26505

A DNS rebinding issue in ReadyMedia (formerly MiniDLNA) before 1.3.1 allows a
remote web server to exfiltrate media files.

Upstream fix commit:
https://sourceforge.net/p/minidlna/git/ci/c21208508dbc131712281ec5340687e5ae89e940/

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-26505
https://seclists.org/oss-sec/2022/q1/169
https://www.openwall.com/lists/oss-security/2022/03/03/1
http://www.openwall.com/lists/oss-security/2022/03/06/1
http://www.cvedetails.com/cve/CVE-2022-26505/
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26505
https://sourceforge.net/p/minidlna/git/ci/c21208508dbc131712281ec5340687e5ae89e940/


body:
--1646658006.1CF08B0.31535
Date: Mon, 7 Mar 2022 13:00:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196829
           Summary: Failed to start auditd rules generation
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: armv7
                OS: openSUSE Leap 15.4
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: matwey.kornilov-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hi,

I am trying
openSUSE-Leap-15.4-ARM-JeOS-beaglebone.armv7l-2021.12.06-Build2.30.raw.xz image
on BeagleBone Black board.

I see that augenrules.service is failed at start with default configuration.

? augenrules.service - auditd rules generation
     Loaded: loaded (/usr/lib/systemd/system/augenrules.service; static)
     Active: failed (Result: exit-code) since Thu 2022-02-24 12:00:56 UTC; 1
week 4 days ago
       Docs: man:augenrules(8)
    Process: 1070 ExecStart=/sbin/augenrules --load (code=exited,
status=1/FAILURE)
   Main PID: 1070 (code=exited, status=1/FAILURE)

Feb 24 12:00:51 localhost systemd[1]: Starting auditd rules generation...
Feb 24 12:00:56 localhost augenrules[1070]: /sbin/augenrules: No change
Feb 24 12:00:56 localhost augenrules[1150]: Error sending add rule data request
(Invalid argument)
Feb 24 12:00:56 localhost augenrules[1150]: There was an error in line 5 of
/etc/audit/audit.rules
Feb 24 12:00:56 localhost augenrules[1150]: No rules
Feb 24 12:00:56 localhost systemd[1]: augenrules.service: Main process exited,
code=exited, status=1/FAILURE
Feb 24 12:00:56 localhost systemd[1]: augenrules.service: Failed with result
'exit-code'.
Feb 24 12:00:56 localhost systemd[1]: Failed to start auditd rules generation.

/etc/audit/audit.rules consists of the following lines:

## This file is automatically generated from /etc/audit/rules.d
-D

-a task,never

I am not sure if this issue is related specifically to armv7l architecture or
not.

summary: Failed to start auditd rules generation


body:
--1646735602.e05b6DC0.1848
Date: Tue, 8 Mar 2022 10:33:22 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196861
           Summary: gcc-ada built with incorrect target
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: x86-64
                OS: openSUSE Leap 15.3
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: opensuse@1.opensuse.bgcomp.co.uk
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The gcc compiler suit, such as the c & c++ compilers, have a target set to
x86_64-suse-linux.

The gcc-ada build however, thinks that the target is x86_64-suse-linux-gnu, as
can be seen from:
/usr/lib64/gcc/x86_64-suse-linux/7/adainclude/s-oscons.ads: Target_Name :
constant String  := "x86_64-suse-linux-gnu";

In other words, there is a mismatch.

This royally mucks up the building of gprbuild since the path is set to
/usr/lib64/gcc/x86_64-suse-linux, not /usr/lib64/gcc/x86_64-suse-linux-gnu.

This is the same with v10 & v11 compilers, on both x86_64 & aarch64, as well as
15.3 and tumbleweed.

We cannot modify /usr/lib64/gcc/x86_64-suse-linux/7/adainclude/s-oscons.ads,
since we would be required to rebuild the GNAT runtime library.

Indeed, from /usr/lib64/gcc/x86_64-suse-linux/11/adainclude/s-oscons.ads, it
states:

summary: gcc-ada built with incorrect target


--1646818632.82CCC881.28182
Date: Wed, 9 Mar 2022 09:37:12 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196913
           Summary: VUL-0: CVE-2022-24714: icingaweb2: Unwanted disclosure of hosts and related data, linked to decommissioned services
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
               URL: https://smash.suse.de/issue/325577/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: ecsos-at-schirra.net
          Reporter: thomas.leroy-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2022-24714

Icinga Web 2 is an open source monitoring web interface, framework and
command-line interface. Installations of Icinga 2 with the IDO writer enabled
are affected. If you use service custom variables in role restrictions, and you
regularly decommission service objects, users with said roles may still have
access to a collection of content. Note that this only applies if a role has
implicitly permitted access to hosts, due to permitted access to at least one
of
their services. If access to a host is permitted by other means, no sensible
information has been disclosed to unauthorized users. This issue has been
resolved in versions 2.8.6, 2.9.6 and 2.10 of Icinga Web 2.

Upstream fix:
https://github.com/Icinga/icingaweb2/commit/6e989d05a1568a6733a3d912001251acc51d9293

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24714
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24714
https://github.com/Icinga/icingaweb2/security/advisories/GHSA-qcmg-vr56-x9wf
https://github.com/Icinga/icingaweb2/commit/6e989d05a1568a6733a3d912001251acc51d9293


--1646817866.f68e234D1.8580
Date: Wed, 9 Mar 2022 09:24:26 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196911
           Summary: VUL-0: CVE-2022-24715: icingaweb2: SSH resources allow arbitrary code execution for authenticated users
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
               URL: https://smash.suse.de/issue/325576/
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: ecsos-at-schirra.net
          Reporter: thomas.leroy-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2022-24715

Icinga Web 2 is an open source monitoring web interface, framework and
command-line interface. Authenticated users, with access to the configuration,
can create SSH resource files in unintended directories, leading to the
execution of arbitrary code. This issue has been resolved in versions 2.8.6,
2.9.6 and 2.10 of Icinga Web 2. Users unable to upgrade should limit access to
the Icinga Web 2 configuration.

Upstream fix commit:
https://github.com/Icinga/icingaweb2/commit/a06d915467ca943a4b406eb9587764b8ec34cafb

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24715
https://github.com/Icinga/icingaweb2/security/advisories/GHSA-v9mv-h52f-7g63
https://github.com/Icinga/icingaweb2/commit/a06d915467ca943a4b406eb9587764b8ec34cafb
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24715


--1646815071.a5D6233.2091
Date: Wed, 9 Mar 2022 08:37:51 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196905
           Summary: VUL-1: CVE-2021-41239: nextcloud: user enumeration setting not obeyed in User Status API
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
               URL: https://smash.suse.de/issue/325580/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: ecsos-at-schirra.net
          Reporter: thomas.leroy-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2021-41239

Nextcloud server is a self hosted system designed to provide cloud style
services. In affected versions the User Status API did not consider the user
enumeration settings by the administrator. This allowed a user to enumerate
other users on the instance, even when user listings where disabled. It is
recommended that the Nextcloud Server is upgraded to 20.0.14, 21.0.6 or 22.2.1.
There are no known workarounds.

Upstream fix commit:
https://github.com/nextcloud/server/pull/29260/commits/3fe267b77279a44dcd9f4ccf75cd2f7ac8321c7b
https://github.com/nextcloud/server/pull/29260/commits/65cfe9df4650fbc877d2104a7f3c21e002e87b5d

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-41239
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41239
https://github.com/nextcloud/security-advisories/security/advisories/GHSA-g722-cm3h-8wrx
https://github.com/nextcloud/server/pull/29260
https://github.com/nextcloud/server/issues/27122


--1646816617.A3aeF2a8.5206
Date: Wed, 9 Mar 2022 09:03:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196908
           Summary: VUL-0: CVE-2021-41241: nextcloud: groupfolders advanced permissions is not obeyed for subfolders
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
               URL: https://smash.suse.de/issue/325579/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: ecsos-at-schirra.net
          Reporter: thomas.leroy-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2021-41241

Nextcloud server is a self hosted system designed to provide cloud style
services. The groupfolders application for Nextcloud allows sharing a folder
with a group of people. In addition, it allows setting "advanced permissions"
on
subfolders, for example, a user could be granted access to the groupfolder but
not specific subfolders. Due to a lacking permission check in affected
versions,
a user could still access these subfolders by copying the groupfolder to
another
location. It is recommended that the Nextcloud Server is upgraded to 20.0.14,
21.0.6 or 22.2.1. Users unable to upgrade should disable the "groupfolders"
application in the admin settings.

Upstream fix:
https://github.com/nextcloud/server/pull/29362/commits/9408f8ae6994666b685f5e2de588f9b2a79a00ed

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-41241
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41241
https://github.com/nextcloud/security-advisories/security/advisories/GHSA-m4wp-r357-4q94
https://github.com/nextcloud/server/pull/29362
https://github.com/nextcloud/groupfolders/issues/1692


--1646900720.31084.12363
Date: Thu, 10 Mar 2022 08:25:20 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196952
           Summary: VUL-1: CVE-2022-24741: nextcloud: High memory usage for generating preview of broken image
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
               URL: https://smash.suse.de/issue/325660/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: ecsos-at-schirra.net
          Reporter: thomas.leroy-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2022-24741

Nextcloud server is an open source, self hosted cloud style services platform.
In affected versions an attacker can cause a denial of service by uploading
specially crafted files which will cause the server to allocate too much memory
/ CPU. It is recommended that the Nextcloud Server is upgraded to 21.0.8 ,
22.2.4 or 23.0.1. Users unable to upgrade should disable preview generation
with
the `'enable_previews'` config flag.

Upstream fix:
https://github.com/nextcloud/server/pull/30291/commits/d3d65e5c889fc3922efc7a8c764027763bc4764f

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24741
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24741
https://github.com/nextcloud/server/pull/30291
https://github.com/nextcloud/security-advisories/security/advisories/GHSA-jf3h-xf4q-mh89
http://www.cvedetails.com/cve/CVE-2022-24741/
https://hackerone.com/reports/1261225


--1646915622.bBd10.13688
Date: Thu, 10 Mar 2022 12:33:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1196965
           Summary: openSUSE Tumbleweed unattended installation with libvirt fails
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Other
          Assignee: virt-bugs-at-suse.de
          Reporter: jroedel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 856908
  --> https://bugzilla.suse.com/attachment.cgi?id=856908&action=edit
Installation failure screenshot

Currently the unattended installation of an openSUSE Tumbleweed on a Tumbleweed
host fails. The command line to start the installation was:

virt-install \
    --arch x86_64 \
    --name "TW" \
    --vcpus 24 \
    --cpu EPYC \
    --memory 4096 \
    --machine q35 \
    --memtune hard_limit=4563402 \
    --disk size=64,target.bus=scsi \
    --controller type=scsi,model=virtio-scsi,driver.iommu=on \
    --network network=default,model=virtio,driver.iommu=on \
    --video vga \
    --boot
loader=/usr/share/qemu/ovmf-x86_64-code.bin,loader.readonly=yes,loader.type=pflash,nvram.template=/usr/share/qemu/ovmf-x86_64-vars.bin,loader_secure=no
\
    --install os=opensusetumbleweed \
    --unattended admin-password-file=pw,user-login=joro,user-password-file=pw

The installer errors out because of an invalid autoyast XML file. See attached
picture for details.


--1646996869.Ba0A51.3729
Date: Fri, 11 Mar 2022 11:07:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1197011
           Summary: VUL-0: CVE-2021-33293: libpano: out-of-bounds read in the function panoParserFindOLine() in parser.c.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
               URL: https://smash.suse.de/issue/325974/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: sbrabec-at-suse.com
          Reporter: thomas.leroy-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2021-33293

Panorama Tools libpano13 v2.9.20 was discovered to contain an out-of-bounds
read
in the function panoParserFindOLine() in parser.c.

Upstream commit:
https://sourceforge.net/p/panotools/libpano13/ci/62aa7eed8fae5d8f247a2508a757f31000de386f/

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-33293
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33293
https://groups.google.com/u/1/g/hugin-ptx/c/gLtz2vweD74
https://sourceforge.net/p/panotools/libpano13/ci/62aa7eed8fae5d8f247a2508a757f31000de386f/


--1647014855.2a7510.22166
Date: Fri, 11 Mar 2022 16:07:35 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1197041
           Summary: Postfix on start don't run postalias /etc/postfix/aliases (error open database /etc/postfix/aliases.lmdb).
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: ilya-at-ilya.cf
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 856943
  --> http://bugzilla.opensuse.org/attachment.cgi?id=856943&action=edit
postconf_-n.log

After postfix stopped supporting hash/db/interbase maps and switched to lmdb
maps, I noticed in the log message that /etc/postfix/aliases.lmdb was missing.
If you manually run "sudo postalias /etc/postfix/aliases", but before it
created itself.
sudo systemctl stop postfix && sudo rm /etc/postfix/*.lmdb && sudo systemctl
stop postfix again leads to this error.
This is fixed simply by sudo vim /usr/lib/postfix/systemd/update_postmaps &&
sudo systemctl daemon-reexec

-for i in /etc/aliases /etc/aliases.d/*; do
+for i in /etc/postfix/aliases /etc/aliases /etc/aliases.d/*; do

You might also have to write somewhere else in the scripts

spec-file postfix is very complicated, script update_postmaps comes in the
archive postfix-SUSE.tar.gz which is not clear how it is created. probably from
github and not clear how to unpack (I saw no explicit call to unpack the
archive), so that alone do SR not decided, please Peter @varkoly do it or
someone who knows this.


--1647114778.CDD0DDe11.7400
Date: Sat, 12 Mar 2022 19:52:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1197053
           Summary: AUDIT-0: NetworkManager-vpnc - sec review dbus-file-unauthorized
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: bjorn.lie-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

New version of NetworkManager-vpnc

Moves %{_sysconfdir}/dbus-1/system.d/nm-vpnc-service.conf to

{_datadir}/dbus-1/system.d/nm-vpnc-service.conf

rpmlint:

[   58s] NetworkManager-vpnc.ppc64le: W: dbus-file-unauthorized
/usr/share/dbus-1/system.d/nm-vpnc-service.conf (file digest
sha256:a64e917733e5e297a213dc878b9339cd08fbfb7dc9dcf85d1eb240ba6d68240b)
[   58s] Packaging D-Bus services requires a review and whitelisting by the
SUSE
[   58s] security team. If the package is intended for inclusion in any SUSE
product
[   58s] please open a bug report to request review of the package by the
security
[   58s] team. Please refer to
[   58s]
https://en.opensuse.org/openSUSE:Package_security_guidelines#audit_bugs for
[   58s] more information.

Package lives in

https://build.opensuse.org/package/show/GNOME:Next/NetworkManager-vpnc


--1647114995.10510f1.10987
Date: Sat, 12 Mar 2022 19:56:35 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1197054
           Summary: AUDIT-0: NetworkManager-pptp sec review dbus-file-unauthorized
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: bjorn.lie-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

New version of NetworkManager-pptp
Moves %{_sysconfdir}/dbus-1/system.d/nm-pptp-service.conf to

{_datadir}/dbus-1/system.d/nm-pptp-service.conf

rpmlint:

[   50s] NetworkManager-pptp.x86_64: W: dbus-file-unauthorized
/usr/share/dbus-1/system.d/nm-pptp-service.conf (file digest
sha256:c4f7b5f77bac397a949c74fd32d5add030cc520f1c2da8e716a7215e1927aa1a)
[   50s] Packaging D-Bus services requires a review and whitelisting by the
SUSE
[   50s] security team. If the package is intended for inclusion in any SUSE
product
[   50s] please open a bug report to request review of the package by the
security
[   50s] team. Please refer to
[   50s]
https://en.opensuse.org/openSUSE:Package_security_guidelines#audit_bugs for
[   50s] more information.

Package lives in

https://build.opensuse.org/package/show/GNOME:Next/NetworkManager-pptp


body:
--1647249161.B37b0.12625
Date: Mon, 14 Mar 2022 09:12:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1197065
           Summary: gcc11: 0ad lua i586 segfault
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: rguenther-at-suse.com
          Reporter: bwiedemann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

We encountered a segfault in i586 builds of 0ad/premake5/lua that even led
people to deactivate that build in
https://build.opensuse.org/request/show/961440

However, on closer inspection, this might be due to a compiler issue around
propagating constants that went away with -O2 or

+++ b/build/premake/premake5/contrib/lua/src/lua.h
-LUA_API void  (lua_rotate) (lua_State *L, int idx, int n);
+LUA_API __attribute__((noipa)) void  (lua_rotate) (lua_State *L, int idx, int
n);

+++ b/build/premake/premake5/contrib/lua/src/lapi.c
-LUA_API void lua_rotate (lua_State *L, int idx, int n) {
+LUA_API __attribute__((noipa)) void lua_rotate (lua_State *L, int idx, int n)
{

For reference the segfault was at
(gdb) bt
#0  reverse (L=<optimized out>, to=0x56774ffc, from=0x5677b9d4)
    at ../../contrib/lua/src/lapi.c:198
#1  lua_rotate.constprop.0 (L=<optimized out>, n=<optimized out>, idx=-2)
    at ../../contrib/lua/src/lapi.c:217
#2  0x565713d3 in luaL_requiref (L=0x567781a4, modname=0x566753d3 "_G",
    openf=0x565b2f90 <luaopen_base>, glb=1)
    at ../../contrib/lua/src/lauxlib.c:983
#3  0x5658e66f in luaL_openlibs (L=0x567781a4)
    at ../../contrib/lua/src/linit.c:64
#4  0x5656edc7 in main (argc=1, argv=0xffffd9c4)
    at ../../src/host/premake_main.c:15

summary: gcc11: 0ad lua i586 segfault