--1598996326.83E06110.24883
Date: Tue, 1 Sep 2020 21:38:46 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176034
           Summary: gpg2: Unable to import or evaluate ed25519 key: free(): invalid pointer
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: pmonrealgonzalez-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: ---
           Blocker: ---

Unable to import ed25519 key. It is partially imported but it's certificate/WOT
is not verified. With the key in the keyring, verifying a signature made with
this key fails.

An empty profile:

$ gpg --version -v
gpg (GnuPG) 2.2.21
libgcrypt 1.8.6
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/[...]/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

From https://www.gnupg.org/signature_key.html
fetch this key:

> pub   ed25519 2020-08-24 [expires: 2030-06-30]
>       Key fingerprint = 6DAA 6E64 A76D 2840 571B  4902 5288 97B8 2640 3ADA
> uid   Werner Koch (dist signing 2020)

$ gpg --import *.keyring
gpg: /home/[...]/.gnupg/trustdb.gpg: trustdb created
gpg: key 249B39D24F25E3B6: public key "Werner Koch (dist sig)" imported
gpg: key 2071B08A33BD3F06: public key "NIIBE Yutaka (GnuPG Release Key)
<gniibe-at-fsij.org>" imported
gpg: key BCEF7E294B092E28: public key "Andre Heinecke (Release Signing Key)"
imported
free(): invalid pointer
Aborted (core dumped)

Unable to list:

$ gpg --list-keys
free(): invalid pointer
Aborted (core dumped)

However it is locally stored:

$ gpg --armor --export 6DAA6E64A76D2840571B4902528897B826403ADA
-----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEX0PliRYJKwYBBAHaRw8BAQdAz75Hlekc16JhhfI0MKdEVxLdkxhcMCO0ZG6W
MBAmNpe0H1dlcm5lciBLb2NoIChkaXN0IHNpZ25pbmcgMjAyMCmImgQTFgoAQhYh
BG2qbmSnbShAVxtJAlKIl7gmQDraBQJfQ+w1AhsDBQkShccRBQsJCAcCAyICAQYV
CgkICwIEFgIDAQIeBwIXgAAKCRBSiJe4JkA62nmuAP9uL/HOdB0gvwWrH+FpURJL
s4bnaZaPIk9ARrU0EXRgJgD/YCGfHQXpIPT0ZaXuwJexK04Z+qMFR/bM1q1Leo5C
jgY=
=ukul
-----END PGP PUBLIC KEY BLOCK-----

$ gpg --armor --export 6DAA6E64A76D2840571B4902528897B826403ADA > gpg2.keyring
$ osc service localrun source_validator
gpg: assuming signed data in '/home/[...]/gpg2/gnupg-2.2.22.tar.bz2'
gpg: Signature made Thu 27 Aug 2020 02:44:50 PM CEST
gpg:                using EDDSA key 6DAA6E64A76D2840571B4902528897B826403ADA
free(): invalid pointer
/usr/lib/obs/service/source_validators/20-files-present-and-referenced: line
169: 11415 Aborted                 (core dumped) gpg $GPG_OPTIONS --verify "$i"
(E) signature /home/[...]/gpg2/gnupg-2.2.22.tar.bz2.sig does not validate


--1599060076.accc1.3034
Date: Wed, 2 Sep 2020 15:21:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176092
           Summary: network/bind: Bug file conflict in libns.so.1604
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: josef.moellers-at-suse.com
          Reporter: dcermak-at-suse.com
        QA Contact: screening-team-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Upgrading to Tumbleweed snapshot 20200831 does not work, it fails with:
Error: Transaction test error:
  file /usr/lib64/libns.so.1604 from install of libisc1606-9.16.6-2.1.x86_64
conflicts with file from package libisc1605-9.16.5-2.2.x86_64


--1599062729.AB7600.5919
Date: Wed, 2 Sep 2020 16:05:29 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176095
           Summary: pahole segfaults on SLE15 {SP1,SP2} kernel debuginfo
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: tdevries-at-suse.com
          Reporter: mkoutny-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I saw this on Tumbleweed [1]
dwarves-1.17-2.3.x86_64

## Steps to reproduce:

> $ sshfs l3mule.suse.de:/ ~/mule -o follow_symlinks
> $ pahole -C mem_cgroup ~/mule/var/cache/crash-setup/15sp2/x86_64/5.3.18-24.9-default

## Expected behavior

prints information about given struct

## Actual behavior

Loads (16309) of messages like:
> tag__recode_dwarf_type: couldn't find 0x734713 type for 0x3e (pointer_type)!
> tag__recode_dwarf_type: couldn't find 0x22 type for 0x75 (array_type)!
> tag__recode_dwarf_type: couldn't find 0x73472d type for 0x10d (pointer_type)!
> tag__recode_dwarf_type: couldn't find 0xf1 type for 0x128 (typedef)!
> tag__recode_dwarf_type: couldn't find 0x10d type for 0x15c (const_type)!
> tag__recode_dwarf_type: couldn't find 0x14 type for 0x133 (variable)!
> [...]
> namespace__recode_dwarf_types: couldn't find 0x1d6 type for 0x24c (member)!
> namespace__recode_dwarf_types: couldn't find 0x1d6 type for 0x258 (member)!
> [...]
> ftype__recode_dwarf_types: couldn't find 0x6436 type for 0x446c7 (formal_parameter)!
> ftype__recode_dwarf_types: couldn't find 0x22 type for 0x446cc (formal_parameter)!
> ftype__recode_dwarf_types: couldn't find 0x18e0d type for 0x446d1 (formal_parameter)!
> ftype__recode_dwarf_types: couldn't find 0x734761 type for 0x446d6 (formal_parameter)!

and eventually segfaults in

> #0  0x00007f8537ad351d tag__natural_alignment (libdwarves.so.1 + 0xf51d)
> #1  0x00007f8537ad359b tag__natural_alignment (libdwarves.so.1 + 0xf59b)
> #2  0x00007f8537ad4d29 type__check_structs_at_unnatural_alignments (libdwarves.so.1 + 0x10d29)
> #3  0x00007f8537ad4ebb class__infer_packed_attributes (libdwarves.so.1 + 0x10ebb)
> #4  0x00007f8537ada6f8 __class__fprintf (libdwarves.so.1 + 0x166f8)
> #5  0x00007f8537ada141 tag__fprintf (libdwarves.so.1 + 0x16141)
> #6  0x000055a77b4e50df pahole_stealer (pahole + 0x50df)
> #7  0x00007f8537ae8dbe cus__load_module (libdwarves.so.1 + 0x24dbe)
> #8  0x00007f8537ae9101 cus__process_dwflmod (libdwarves.so.1 + 0x25101)
> #9  0x00007f85378af6c1 dwfl_getmodules (libdw.so.1 + 0x506c1)
> #10 0x00007f8537ae107d dwarf__load_file.lto_priv.0 (libdwarves.so.1 + 0x1d07d)
> #11 0x00007f8537ad52e1 cus__load_file (libdwarves.so.1 + 0x112e1)
> #12 0x00007f8537ad8e28 cus__load_files (libdwarves.so.1 + 0x14e28)
> #13 0x000055a77b4e350a main (pahole + 0x350a)
> #14 0x00007f8537923cca __libc_start_main (libc.so.6 + 0x26cca)
> #15 0x000055a77b4e364a _start (pahole + 0x364a)

(Bug assignment is an educated guess.)

[1] pahole from Leap 15.2 (dwarves-1.11-lp152.3.9) failed at the task too
(didn't crash though) and it worked with 4.12 kernel debuginfo. I'm filing the
bug against the newer version.


body:
--1599071743.F8F6a0.26935
Date: Wed, 2 Sep 2020 18:35:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176101
           Summary: Gajim can't start - outdated nbxmpp
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: opensuse-at-trummer.xyz
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

OS: openSUSE Tumbleweed 20200831

Gajim was recently upgraded to 1.2.2 which requires python3-nbxmpp >= 1.0.2,
however only 0.6.10 is packaged at the moment, causing Gajim to fail to start.

-----snip-----

Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 583,
in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 900,
in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 791,
in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (nbxmpp 0.6.10
(/usr/lib/python3.8/site-packages), Requirement.parse('nbxmpp>=1.0.2'),
{'gajim'})

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/gajim", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3252,
in <module>
    def _initialize_master_working_set():
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3235,
in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3264,
in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 585,
in _build_master
    return cls._build_from_requirements(__requires__)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 598,
in _build_from_requirements
    dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 786,
in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'nbxmpp>=1.0.2' distribution was not
found and is required by gajim

-----snip-----

Might be the same problem as this older one
https://bugzilla.opensuse.org/show_bug.cgi?id=1072573

pkgs: gajim python-nbxmpp

summary: Gajim can't start - outdated nbxmpp


body:
--1599213221.Ad3330A2.16289
Date: Fri, 4 Sep 2020 09:53:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176164
           Summary: Craete budgie pattern
    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: callumjfarmer13-at-gmail.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

Create a pattern for budgie desktop.

* Add pattern icon to yast-theme
* Send pattern file to Factory

summary: Craete budgie pattern


--1599224245.82AE50d3.17704
Date: Fri, 4 Sep 2020 12:57:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176175
           Summary: [Jump] Add/update FPC compiler in Jump / SLE15SP2 Package Hub
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: qa-bugs-at-suse.de
                CC: afaerber-at-suse.com, dmueller-at-suse.com,
                    lubos.kocman-at-suse.com
          Found By: ---
           Blocker: ---

FPC compiler is missing for aarch64 (and ppc64le) in PackageHub and thus in
Jump, which breaks the rebuild of gdb
(https://progress.opensuse.org/issues/70393) and maybe more packages.

The easiest way is to provide an update to Leap:15.2:Update as the latest fpc
package contains the logic to auto-bootstrap fpc.

The plan is to update fpc to the current version 3.2.0.
Lazarus would require a rebuild as it is tightly tied to fpc version. As a
bugfix release (2.0.10) is available in devel project, we can submit this
update at the same time.

Also keep in mind that fpc fails to build/run on ThunderX2 machines [0] so the
builds may require to be restarted a few times for aarch64 until packages get
scheduled on a worker different from obs-arm-{7,8,9}.

[0]: https://bugzilla.opensuse.org/show_bug.cgi?id=1122855


body:
--1599327712.1DCCeD6F0.10081
Date: Sat, 5 Sep 2020 17:41:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176200
           Summary: Audio does not work on Dell XPS 17 9700
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: x86-64
                OS: openSUSE Leap 15.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: aleksey.rukhlenko-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Audio does not work on Dell XPS 17 9700 laptop (the newest one).

When I go to Yast and try to configure audio card, I get the following message:
"An error occurred during the installation of Comet Lake PCH cAVS. The kernel
module snd-soc-skl for sound support could not be loaded. This can be caused by
incorrect module parameters, including invalid IO or IRQ parameters.".

There is a blog with a guidance how to make it work on Arch Linux
https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio-working-on-linux/.
But trying to compile soundwire-dkms on OpenSUSE failed both on 5.3 and 5.8
kernels available in repos. Installing soundwire-dkms binary converted to rpm
from deb from Ubunty repo also did not help. There is a firmware for this
driver available (sof-firmware-1.5.1
https://www.reddit.com/r/Dell/comments/husu3r/how_to_get_fully_working_audio_in_ubuntu_2004_on/),
but without soundwire-dkms it will not work. I tried to compile both 1.3 and
1.2.1 versions of soundwire-dkms, none of these attempts was successful.

summary: Audio does not work on Dell XPS 17 9700


--1599371349.517b1.5471
Date: Sun, 6 Sep 2020 05:49:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176203
           Summary: X is unable to run on Build 20200904 on Raspberry Pi 3
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: gfx-bugs-at-suse.de
          Reporter: dillon.ang.h-at-gmail.com
        QA Contact: gfx-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Recently I updated my Raspberry Pi systems to Build 20200904 from 20200825. On
my Raspberry Pi 4, everything works normally, and I can get a graphical
environment. However, my Raspberry Pi 3 only boots the command line now. I
tried starting x manually by invoking the display manager I use, lightDM. My
systems all use a combination of XFCE and lightDM. Running lightDM does not
produce any output, however it does not run. Running startx results in warning
messages where it tells me the x.org is unable to start.

To isolate the problem, I booted the installation DVD on both my Raspberry Pi 4
and Raspberry Pi 3 off a USB stick. Typically when I run the installation DVD,
I can get to the graphical installation interface which relies on X on both
systems without any difficulty. I was able to get to graphical installation
interface on my Raspberry Pi 4, however on my Raspberry Pi 3, it gave a warning
that X had crashed and instead gave me the text-based installation interface.

All of my systems were installed off the installation DVD to the SD card. I
will attempt to get the output from startx and try to capture the output from
the installation DVD.


--1599390259.fBdC70.11755
Date: Sun, 6 Sep 2020 11:04:19 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176207
           Summary: Chromium: no hardware acceleration after updating to 85.0.4183.69
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: danrask-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 841416
  --> http://bugzilla.opensuse.org/attachment.cgi?id=841416&action=edit
Report from the chrome://gpu page

After updating to 85.0.4183.69 Chromium fails to initialize the GPU process:

[3245:3245:0906/123433.787250:ERROR:gl_implementation.cc(286)] : Failed to load
/usr/lib64/chromium/libGLESv2.so: /usr/lib64/chromium/libGLESv2.so: cannot open
shared object file: No such file or directory
[3245:3245:0906/123433.792599:ERROR:viz_main_impl.cc(150)] : Exiting GPU
process due to errors during initialization

Which leads to disabled hardware acceleration:

Gpu compositing has been disabled, either via blacklist, about:flags or the
command line. The browser will fall back to software compositing and hardware
acceleration will be unavailable.
Disabled Features: gpu_compositing

Happens with both Leap 15.2 boxes I have (one with the integrated Intel HD 520
graphics, another one with the proprietary Nvidia drivers). This issue does not
happen with the previous version (84.0.4147.135-lp152.2.17.1.x86_64).


body:
--1599413808.d3A70.20730
Date: Sun, 6 Sep 2020 17:36:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176212
           Summary: sddm can't login in x plasma session
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: werwolf131313-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

after input password sddm blink and restart

sddm version sddm-0.18.1-88.5.x86_64

xorg log:
[    11.767] (EE) Failed to open authorization file
"/run/sddm/{403b7696-a1ff-4dd9-b24a-cf84d015ad70}": No such file or directory

pkgs: xdm xinit

summary: sddm can't login in x plasma session


--1599457934.dF45C50.5631
Date: Mon, 7 Sep 2020 05:52:14 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176215
           Summary: AUDIT-0: systemd: new polkit action org.freedesktop.network1.forcerenew in systemd v246
    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: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello Secteam,

Could you review the following DBUS method so we can upgrade Factory with the
latest version of systemd v246 ?

systemd-network.x86_64: E: polkit-untracked-privilege (Badness: 10000)
org.freedesktop.network1.forcerenew (auth_admin:auth_admin:auth_admin_keep)

You can find the default policies shipped by upstream here:
https://github.com/systemd/systemd/blob/v246/src/network/org.freedesktop.network1.policy

Thanks.


--1599463081.51ee640.11914
Date: Mon, 7 Sep 2020 07:18:01 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176219
           Summary: dd_rescue fails on UnitTests when LTO is enabled
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: qa-bugs-at-suse.de
                CC: afaerber-at-suse.com, dmueller-at-suse.com
          Found By: ---
           Blocker: ---

Created attachment 841425
  --> http://bugzilla.opensuse.org/attachment.cgi?id=841425&action=edit
Build log with LTO enabled

dd_rescue fails on UnitTests when LTO is enabled.
If we disable LTO, it builds properly.


--1599463550.c4C4a00.12523
Date: Mon, 7 Sep 2020 07:25:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176220
           Summary: LLVM10 misses some 'Intrinsics' to build TVM
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

TVM builds properly with llvm9 on Leap, but fails with llvm10 in Tumbleweed.
Errors are on multiple missing ::llvm::Intrinsic::* :

[  356s]
/home/abuild/rpmbuild/BUILD/incubator-tvm-0.6.1/src/codegen/llvm/codegen_arm.cc:
In member function 'tvm::Expr tvm::codegen::CodeGenARM::ARMPopcount(const
tvm::ir::Call*)':
[  356s]
/home/abuild/rpmbuild/BUILD/incubator-tvm-0.6.1/src/codegen/llvm/codegen_arm.cc:61:57:
error: 'arm_neon_vpaddlu' is not a member of 'llvm::Intrinsic'
[  356s]    61 |   ::llvm::Intrinsic::ID vpaddlu_id =
::llvm::Intrinsic::arm_neon_vpaddlu;

[  354s]
/home/abuild/rpmbuild/BUILD/incubator-tvm-0.6.1/src/codegen/llvm/codegen_amdgpu.cc:
In member function 'virtual llvm::Value*
tvm::codegen::CodeGenAMDGPU::GetThreadIndex(const tvm::IterVar&)':
[  354s]
/home/abuild/rpmbuild/BUILD/incubator-tvm-0.6.1/src/codegen/llvm/codegen_amdgpu.cc:135:56:
error: 'amdgcn_workitem_id_x' is not a member of 'llvm::Intrinsic'
[  354s]   135 |     llvm::Intrinsic::ID intrin_id =
::llvm::Intrinsic::amdgcn_workitem_id_x;

[  176s]
/home/abuild/rpmbuild/BUILD/incubator-tvm-0.6.1/src/codegen/llvm/codegen_nvptx.cc:
In member function 'virtual llvm::Value*
tvm::codegen::CodeGenNVPTX::GetThreadIndex(const tvm::IterVar&)':
[  176s]
/home/abuild/rpmbuild/BUILD/incubator-tvm-0.6.1/src/codegen/llvm/codegen_nvptx.cc:111:56:
error: 'nvvm_read_ptx_sreg_tid_x' is not a member of 'llvm::Intrinsic'
[  176s]   111 |     llvm::Intrinsic::ID intrin_id =
::llvm::Intrinsic::nvvm_read_ptx_sreg_tid_x;

[  176s]    88 |           ::llvm::Intrinsic::x86_avx512_mask_vcvtph2ps_512,
16, LLVMType(Float(32, from.lanes())),
[  176s]       |                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[  176s]
/home/abuild/rpmbuild/BUILD/incubator-tvm-0.6.1/src/codegen/llvm/codegen_x86_64.cc:100:30:
error: 'x86_vcvtph2ps_256' is not a member of 'llvm::Intrinsic'
[  176s]   100 |           ::llvm::Intrinsic::x86_vcvtph2ps_256, 8,
LLVMType(Float(32, from.lanes())),
[  176s]       |                              ^~~~~~~~~~~~~~~~~


--1599505020.c1c360.1486
Date: Mon, 7 Sep 2020 18:57:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176244
           Summary: Recent upgrade broke bcache support - dracut does not use /usr/libexec/dracut/modules.d
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: ericvanblokland-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After a recent upgrade, boot dropped me to an emergency shell because the root
filesystem wasn't there.
I traced it down to the bcache device not becoming available. It turns out the
bcache package puts its dracut modules in /usr/libexec/dracut/modules.d instead
of /usr/lib/dracut/modules.d

Manually copying the module from /usr/libexec/dracut/modules.d to
/usr/lib/dracut/modules.d and regenerating the initramfs fixes it.

I guess the bcache package is using this legacy path and needs to be corrected.


--1599579086.DFacda0.18881
Date: Tue, 8 Sep 2020 15:31:26 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176285
           Summary: netconfig: /usr/lib/chrony/helper now in libexec
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: mt-at-suse.com
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

with the libexec move /usr/lib/chrony/helper is now /usr/libexec/chrony/helper


--1599586496.A86EBA00.27958
Date: Tue, 8 Sep 2020 17:34:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176294
           Summary: salt RPM scriptlet contains syntax error
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Salt
          Assignee: salt-maintainers-at-suse.de
          Reporter: ncutler-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When I install "salt-master" using zypper, I get:

Additional rpm output:
/var/tmp/rpm-tmp.7loEN8: line 17: [: 245.7: integer expression expected

which leads me to believe that one of the RPM scriptlets is written in a way
that it ends up containing a syntax error.

Here is the exact command the full output:

    master: ++ zypper --non-interactive install salt-master
    master: Loading repository data...
    master: Reading installed packages...
    master: Resolving package dependencies...
    master: The following 2 NEW packages are going to be installed:
    master:   dmidecode salt-master
    master: 2 new packages to install.
    master: Overall download size: 3.2 MiB. Already cached: 0 B. After the
operation, additional 3.2 MiB will be
 used.
    master: Continue? [y/n/v/...? shows all options] (y):
    master: y
    master: Retrieving package dmidecode-3.2-6.3.x86_64 (1/2),  84.7 KiB (210.8
KiB unpacked)
    master: Retrieving: dmidecode-3.2-6.3.x86_64.rpm [. . . done]
    master: Retrieving package salt-master-3000.3-3.2.x86_64 (2/2),   3.1 MiB (
 3.0 MiB unpacked)
    master: Retrieving: salt-master-3000.3-3.2.x86_64.rpm [. . . done]
    master: Checking for file conflicts: [. . . . done]
    master: (1/2) Installing: dmidecode-3.2-6.3.x86_64 [. . . done]
    master: (2/2) Installing: salt-master-3000.3-3.2.x86_64 [. . . done]
    master: Additional rpm output:
    master: /var/tmp/rpm-tmp.7loEN8: line 17: [: 245.7: integer expression
expected


body:
--1599618422.F4A25.7299
Date: Wed, 9 Sep 2020 02:27:02 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176304
           Summary: GDM showing openSUSE / SUSE logo
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: openSUSE Leap 15.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: gnome-bugs-at-suse.de
          Reporter: vinyanalista-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 841497
  --> http://bugzilla.opensuse.org/attachment.cgi?id=841497&action=edit
GDM with SUSE logo

How to reproduce the bug: download the openSUSE Leap 15.2 live image from
software.opensuse.org, boot it (you can use a VirtualBox VM), give the live
user a password, play with locking the screen and logging out. Sometimes the
SUSE logo appears, sometimes the openSUSE logo appears.

It seems to me that when locking the screen, the SUSE logo appears. Logging
out, the openSUSE logo appears.

I couldn't reproduce it in Tumbleweed. So it seems to be a Leap 15.2 issue
only.

Tested yesterday (Sep 07, 2020):

- openSUSE-Leap-15.2-GNOME-Live-x86_64-Build31.161-Media.iso
- openSUSE-Tumbleweed-GNOME-Live-x86_64-Snapshot20200905-Media.iso

pkgs: gnome-shell gnome-shell-extensions

summary: GDM showing openSUSE / SUSE logo


--1599630667.dC85dd0.5835
Date: Wed, 9 Sep 2020 05:51:07 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176306
           Summary: VUL-0: CVE-2020-6573,CVE-2020-6574,CVE-2020-6575,CVE-2020-657 6,CVE-2020-15959: chromium: Update to 85.0.4183.102
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tchvatal-at-suse.com
          Reporter: atoptsoglou-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

CVE-2020-6573: Use after free in video.
CVE-2020-6574: Insufficient policy enforcement in installer.
CVE-2020-6575: Race in Mojo.
CVE-2020-6576: Use after free in offscreen canvas.
CVE-2020-15959: Insufficient policy enforcement in networking.

Reference

https://chromereleases.googleblog.com/2020/09/stable-channel-update-for-desktop.html


--1599641893.D16E60.10144
Date: Wed, 9 Sep 2020 08:58:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176312
           Summary: pdns and pdns-recursor fail to build with Boost >= 1.73
    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: michael-at-stroeder.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Packages pdns and pdns-recursor fail to build with Boost >= 1.73.

This issue is tracked by upstream here:
https://github.com/PowerDNS/pdns/pull/9070


--1599661941.1BFdC00.12124
Date: Wed, 9 Sep 2020 14:32:21 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176338
           Summary: lightdm: "authentificataion failure" after moving xdm{,-np} PAM files from /etc/pam.d to /usr/etc/pam.d
    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: sndirsch-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I received "authentificataion failure" in lightdm after moving xdm{,-np} PAM
files from /etc/pam.d to /usr/etc/pam.d. It was my understanding
the moving would be possible now with latest pam package in Tumbleweed.

rpm --changelog -q pam
[...]
* Mo Aug 19 2019 kukuk-at-suse.de
- usr-etc-support.patch: Add support for /usr/etc/pam.d

Could it also be an issue in lightdm?


body:
--1599690773.Df2d0.24073
Date: Wed, 9 Sep 2020 22:32:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176374
           Summary: musepack segfault
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: smithjd15-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

running mpcenc:
MPC Encoder 1.30.1 --stable

summary: musepack segfault


--1599721986.56e11.14451
Date: Thu, 10 Sep 2020 07:13:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176384
           Summary: mozilla/thunderbird78: Thunderbird Starts up Blank after Upgrade to 78.2.2
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: 3rd party software
          Assignee: wolfgang-at-rosenauer.org
          Reporter: alessandro.sturniolo-at-gmail.com
        QA Contact: screening-team-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 841563
  --> http://bugzilla.opensuse.org/attachment.cgi?id=841563&action=edit
Thunderbird Window

After today update to Thunderbird 78.2.2, when I open the application, the
window is partially blank.
I get menu bars and the calendar area, but no accounts, no emails and no
folders. Those areas are just white blanks.

Trying to open in Safe mode, gives no results.

Launching the software from command line, gives no output messages.

No extensions or themes installed.

Preferences menu doesn't open at all.

Downloading Thunderbird 78.2.1 from https://give.thunderbird.net/ solved the
issue (so the profile, I think, is not the cause).


--1599727135.8FEA0.4322
Date: Thu, 10 Sep 2020 08:38:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176388
           Summary: OMEMO plugin for Tumbleweed doesn't work
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: opensuse-at-trummer.xyz
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

(from
https://build.opensuse.org/package/show/network/gajim#comment-1305719 )

It seems that Gajim 1.2 doesn't work with the old OMEMO plugin version 2.6.29
anymore. The easiest way would be to just update the plugin to the latest
version for the 1.2 branch - 2.6.80, see
https://dev.gajim.org/gajim/gajim-plugins/-/blob/master/README.md

But the Gajim 1.1 branch that Leap 15.2 and 15.1 have only works with the
plugin until version 2.6.30:
https://dev.gajim.org/gajim/gajim-plugins/-/blob/gajim_1.1/omemo/CHANGELOG


--1599732208.Df7F0aD0.30149
Date: Thu, 10 Sep 2020 10:03:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176401
           Summary: [WSL] missing group nobody which is used by quite some tools
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: WSL
          Assignee: sle-ms-at-suse.de
          Reporter: lubos.kocman-at-suse.com
        QA Contact: qa-c-at-suse.de
          Found By: ---
           Blocker: ---

I was just trying to get openvpn working on my TW WSL image and it failed on
the fact that the group nobody is missing. I've checked and user nobody is
missing as well.

lkocman@DESKTOP-DESO8KI:/etc/openvpn> sudo openvpn --config heroes.conf.UDP
[sudo] password for root:
Thu Sep 10 11:54:38 2020 OpenVPN 2.4.8 aarch64-suse-linux-gnu [SSL (OpenSSL)]
[LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Oct 30 2019
Thu Sep 10 11:54:38 2020 library versions: OpenSSL 1.1.1g  21 Apr 2020, LZO
2.10
Enter Auth Username:lkocman
Enter Auth Password:
Thu Sep 10 11:54:46 2020 NOTE: the current --script-security setting may allow
this configuration to call user-defined scripts
Thu Sep 10 11:54:46 2020 failed to find GID for group nobody
Thu Sep 10 11:54:46 2020 Exiting due to fatal error
lkocman@DESKTOP-DESO8KI:/etc/openvpn> groupadd nobody

I think we should add it to make it more convenient for users so they can get
most of it.

Workaround:
lkocman@DESKTOP-DESO8KI:/etc/openvpn> sudo groupadd -g 65534 nobody
lkocman@DESKTOP-DESO8KI:/etc/openvpn> sudo useradd -s /bin/false -G nobody -u
65534 nobody

This applies to both TW and Leap images.


--1599744229.BDDd4E60.17133
Date: Thu, 10 Sep 2020 13:23:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176414
           Summary: libmysofa is built with profiling enabled
    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: lpechacek-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

ffmpeg, which is a user of libmysofa, spits out the below messages upon
termination. It looks like a result of profiling code being enabled in libsofa
code. I believe the shipping version of the library should be built *without*
profiling.

...
Exiting normally, received signal 2.
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/reader.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hdf/superblock.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hdf/dataobject.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hdf/btree.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hdf/fractalhead.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hdf/gunzip.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hdf/gcol.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/check.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/spherical.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/lookup.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/tools.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/kdtree.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/neighbors.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/interpolate.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/resample.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/loudness.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/minphase.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/easy.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/hrtf/cache.c.gcda:Skip
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1:Cannot create directory
profiling:/home/abuild/rpmbuild/BUILD/libmysofa-1.1/build/src/CMakeFiles/mysofa-shared.dir/resampler/speex_resampler.c.gcda:Skip


--1599746741.3Fd45.22579
Date: Thu, 10 Sep 2020 14:05:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176418
           Summary: gnome-shell[4553]: Failed to load background 'file:///home/adam': Error opening file /home/adam: Is a directory
    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: adam-at-valkor.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Repeated messages in user journal:

Sep 08 18:45:58 think gnome-shell[4553]: Failed to load background
'file:///home/adam': Error opening file /home/adam: Is a directory
Sep 08 18:45:58 think gnome-shell[4553]: Failed to load background
'file:///home/adam': Error opening file /home/adam: Is a directory
Sep 08 18:45:58 think gnome-shell[4553]: Failed to load background
'file:///home/adam': Error opening file /home/adam: Is a directory

Removing this patch removes the error, so it is likely the problem:
gnome-shell-fate324570-Make-GDM-background-image-configurable.patch


--1599835744.6A340.11837
Date: Fri, 11 Sep 2020 14:49:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176450
           Summary: [Build 20200910] chromium fails to load 'start page;
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/1391680/modules/chro
                    mium/steps/14
                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: ---

## Observation

openQA test in scenario opensuse-Tumbleweed-NET-x86_64-xfce@64bit fails in
[chromium](https://openqa.opensuse.org/tests/1391680/modules/chromium/steps/14)

When chromium starts, the page defined as 'start page' does not show up
properly. Subsequent browsing to any web page seems to work just fine, as does
loading the web page in a different tab (or coming back to it after loading any
other page in tab 1)

When chromium is started on the console, there is a repeated log output:

[27296:27296:0911/164713.073522:ERROR:gl_context_egl.cc(233)] eglCreateContext
failed with error EGL_BAD_ATTRIBUTE
[27296:27296:0911/164713.073619:ERROR:gpu_channel_manager.cc(711)]
ContextResult::kFatalFailure: Failed to create shared context for
virtualization.
[27296:27296:0911/164713.073705:ERROR:shared_image_stub.cc(417)]
SharedImageStub: unable to create context
[27296:27296:0911/164713.073805:ERROR:gpu_channel.cc(449)] GpuChannel: Failed
to create SharedImageStub
[27296:27296:0911/164713.074373:ERROR:gl_context_egl.cc(233)] eglCreateContext
failed with error EGL_BAD_ATTRIBUTE
[27296:27296:0911/164713.074445:ERROR:gpu_channel_manager.cc(711)]
ContextResult::kFatalFailure: Failed to create shared context for
virtualization.

## Test suite description

## Reproducible

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

## Expected result

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

## Further details

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


--1600061017.CdDbf0.15820
Date: Mon, 14 Sep 2020 05:23:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176474
           Summary: AUDIT-0: powerdevil5 (suse-dbus-unauthorized-service, polkit-untracked-privilege)
    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: lbeltrame-at-kde.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,

the upcoming version of Plasma 5 (5.20), planned for next month (October 13th)
includes a new KAuth helper to handle new privileged operations, in particular,
getting and setting battery charge thresholds in laptops that support it (like
Lenovo Thinkpads).

This meant that powerdevil5 has now additional helpers to handle this. Two new
polkit privileges are asked:
org.kde.powerdevil.chargethresholdhelper.getthreshold (??:yes:yes) and
org.kde.powerdevil.chargethresholdhelper.setthreshold (??:no:auth_admin_keep).

The two D-Bus service files found by rpmlint are:

-
/usr/share/dbus-1/system-services/org.kde.powerdevil.chargethresholdhelper.service
- /usr/share/dbus-1/system.d/org.kde.powerdevil.chargethresholdhelper.conf

Code used by the helper:

-
https://invent.kde.org/plasma/powerdevil/-/blob/master/daemon/chargethresholdhelper.cpp
-
https://invent.kde.org/plasma/powerdevil/-/blob/master/daemon/chargethresholdhelper.h
-
https://invent.kde.org/plasma/powerdevil/-/blob/master/daemon/chargethreshold_helper_actions.actions

A package including these features is available at
https://build.opensuse.org/package/show/KDE:Unstable:Frameworks/powerdevil5.


--1600103616.822A0.31130
Date: Mon, 14 Sep 2020 17:13:36 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176517
           Summary: The (new) qemu-hw-usb-redirect qemu-hw-display-qxl packages are not pulled on upgrades as intended
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Virtualization:Other
          Assignee: virt-bugs-at-suse.de
          Reporter: mecftu-at-yahoo.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

the qemu-hw-usb-redirect qemu-hw-display-qxl sub packages are not pulled
during the upgrade of the Micro-OS, a derivative of Tumbleweed, with KVM Server
Patterns.

This results in the inability to use QXL video mode (Virtual Hardware Details >
Video > Details tab) and also the use of SPICE USB Redirection during the
creation of new KVM VMs using Virtual Machine Manager.

The quick workaround (on Micro-OS) is the manual installation of the
aforementioned sub packages using the "transactional-update pkg install
qemu-hw-usb-redirect qemu-hw-display-qxl" command


--1600156068.cC8Fb2.2307
Date: Tue, 15 Sep 2020 07:47:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176530
           Summary: [Build 20200914] Pattern Header description: text overlaps icon
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/1394006/modules/sele
                    ct_patterns/steps/17
                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: openQA
           Blocker: ---

## Observation

openQA test in scenario
opensuse-Tumbleweed-DVD-x86_64-create_hdd_gnome-x11@64bit fails in
[select_patterns](https://openqa.opensuse.org/tests/1394006/modules/select_patterns/steps/17)

In the right pane, the Text 'GNOME Desktop; Environment (Wayland)' overlaps the
icon - in the past, this was '[ICON] Text'

Assigning initially to YaST - the snapshot 0914 had an upgrade of Qt 5.15.1

## Test suite description

## Reproducible

Fails since (at least) Build
[20200914](https://openqa.opensuse.org/tests/1394006) (current job)

## Expected result

Last good: [20200911](https://openqa.opensuse.org/tests/1392329) (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=create_hdd_gnome-x11&version=Tumbleweed)


--1600173280.26Ff0.22835
Date: Tue, 15 Sep 2020 12:34:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176557
           Summary: lualatex seem not to be configured correctly
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: gm.venekamp-at-quicknet.nl
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Using TW 20200909 I am getting an error when using lualatex. The sample
document is:
```
\documentclass[a4paper]{article}

\begin{document}

\end{document}
```

When trying to compile I get the following error:
```
> lualatex s.tex
This is LuaHBTeX, Version 1.12.0 (TeX Live 2020/TeX Live for SUSE Linux)
 restricted system commands enabled.

---! lualatex.fmt was written by luatex
(Fatal format file error; I'm stymied)
```

After editing the file:
```
/etc/texmf/web2c/fmtutil.cnf
```

and taking a lucky guess at changing the config it now works for me. The three
commented out lines below are the original lines in the config file and
directly below are the lines that seem to fix my issue. However, I simply took
an educated guess here.

```
# from latex-bin:
latex pdftex language.dat -translate-file=cp227.tcx *latex.ini
pdflatex pdftex language.dat -translate-file=cp227.tcx *pdflatex.ini
#dvilualatex luatex language.dat,language.dat.lua dvilualatex.ini
#lualatex luatex language.dat,language.dat.lua lualatex.ini
#luajitlatex luajittex language.dat,language.dat.lua lualatex.ini
dvilualatex lualatex language.dat,language.dat.lua dvilualatex.ini
lualatex lualatex language.dat,language.dat.lua lualatex.ini
luajitlatex luajitlatex language.dat,language.dat.lua lualatex.ini
```

Regards,
Gerben


--1600197223.4ba4A310.17471
Date: Tue, 15 Sep 2020 19:13:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176571
           Summary: tigervnc: vncserver fails to start plasma session
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: comes-at-naic.edu
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Install opensuse with KDE Plasma
Start a Plasma desktop session.
Open a terminal
Run: vncserver

Depending on the opensuse version the result is the following:
42.3 and earlier - a working vnc session is started.
15.0 and 15.1    - Xvnc is started but the plasma session in it crashes
15.2             - Xvnc is started, the plasma session in it crashes and
                   kwin_x11 of the main desktop session dies.
tumbleweed       - Xvnc is started, the plasma session in it crashes together
                   with the desktop plasma session which kills the Xserver too.

The first time vncserver is executed it creates the script ~/.vnc/xstartup
such script starts the vnc desktop session with the command:
  exec "$client"
replacing such command with:
  exec dbus-launch "$client"
fixes the problem.

The source rpm tigervnc contains the file:
  u_tigervnc_update_default_vncxstartup.patch
The fix should be added in such file. Changing it from:
-       "if [ -x /etc/X11/xinit/xinitrc ]; then\n".
-       "  exec /etc/X11/xinit/xinitrc\n".
+       "\n".
+       "if [ -x \"\$client\" ]; then\n".
+       "  exec \"\$client\"\n".
        "fi\n".
-       "if [ -f /etc/X11/xinit/xinitrc ]; then\n".
-       "  exec sh /etc/X11/xinit/xinitrc\n".
+       "if [ -f \"\$client\" ]; then\n".
+       "  exec sh \"\$client\"\n".

to:
-       "if [ -x /etc/X11/xinit/xinitrc ]; then\n".
-       "  exec /etc/X11/xinit/xinitrc\n".
+       "\n".
+       "if [ -x \"\$client\" ]; then\n".
+       "  exec dbus-launch \"\$client\"\n".
        "fi\n".
-       "if [ -f /etc/X11/xinit/xinitrc ]; then\n".
-       "  exec sh /etc/X11/xinit/xinitrc\n".
+       "if [ -f \"\$client\" ]; then\n".
+       "  exec dbus-launch sh \"\$client\"\n".

fixes the tigervnc package.


--1600257029.fcfe8e51.19394
Date: Wed, 16 Sep 2020 11:50:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176597
           Summary: boost: missing header dependency in serialization library
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: amajer-at-suse.com
          Reporter: amajer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

cat test.cpp
> #include <boost/serialization/set.hpp>

g++ -c test.cpp -I 1.74/include/
> In file included from test.cpp:1:0:
> 1.74/include/boost/serialization/set.hpp: In function ‘void boost::serialization::load_set_collection(Archive&, Container&)’:
> 1.74/include/boost/serialization/set.hpp:41:33: error: ‘library_version_type’ in namespace ‘boost::serialization’ does not name a type
>      const boost::serialization::library_version_type library_version(
>                                  ^~~~~~~~~~~~~~~~~~~~
> 1.74/include/boost/serialization/set.hpp:48:30: error: ‘library_version_type’ is not a member of ‘boost::serialization’
>      if(boost::serialization::library_version_type(3) < library_version){
>                               ^~~~~~~~~~~~~~~~~~~~
> 1.74/include/boost/serialization/set.hpp:48:30: note: suggested alternative: ‘item_version_type’
>      if(boost::serialization::library_version_type(3) < library_version){
>                               ^~~~~~~~~~~~~~~~~~~~
>                               item_version_type
> 1.74/include/boost/serialization/set.hpp:48:56: error: ‘library_version’ was not declared in this scope
>      if(boost::serialization::library_version_type(3) < library_version){
>                                                         ^~~~~~~~~~~~~~~
> 1.74/include/boost/serialization/set.hpp:48:56: note: suggested alternative: ‘item_version’
>      if(boost::serialization::library_version_type(3) < library_version){
>                                                         ^~~~~~~~~~~~~~~
>                                                         item_version

This is a regression since earlier Boost 1.71

Upstream fixed in map.hpp

https://github.com/boostorg/serialization/commit/f4c6d58bb5b61e2e3095f08af9ce4e7c3f08f351#diff-221afe533cf0acfd282372d1600e99c9


--1600288823.Cc35cA0.31697
Date: Wed, 16 Sep 2020 20:40:23 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176644
           Summary: multipath-tools: "BUG: orphaning path sdx that holds hwe of mpatha"
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: martin.wilck-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 841738
  --> https://bugzilla.suse.com/attachment.cgi?id=841738&action=edit
libmultipath-copy-mpp-hwe-from-pp-hwe.patch

Also: "BUG: do_set_from_hwe called with hwe == NULL"

This comes from broken handling of the hardware property entries (hwe) in
libmultipath. A patch has been sent upstream.


--1600331201.6d23Ed70.11204
Date: Thu, 17 Sep 2020 08:26:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176666
           Summary: KDE: akonadi_archivemail_agent (akonadi_archivemail_agent), signal: Segmentation fault
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: x86-64
                OS: openSUSE Leap 15.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: bugrprt21882-at-online.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

KDE PIM KMail repair tracking:

KDE Bug Report 425786 has been resolved and fixed:
<https://bugs.kde.org/show_bug.cgi?id=425786>

Application: akonadi_archivemail_agent (5.14.2 (20.04.2))

Qt Version: 5.12.7
Frameworks Version: 5.71.0
Operating System: Linux 5.3.18-lp152.36-default x86_64
Windowing system: X11
Distribution: openSUSE Leap 15.2

The changed code has been committed in PIM KMail branch 'release/20.08':
<https://invent.kde.org/pim/kmail/commit/0922a95a692f6424773cd28f21a83237a60d226f>

----------------------------------------------------------------------
Reason for the repair:
New, fresh, KMail installation - 1 Akonadi MailDir resource per POP3 Resource -
all the needed e-Mail has been re-imported - no e-Mails without a RID -
periodic pull of POP3 accounts setup - setting up the first periodic Archive -
of the Inbox - pressed "OK" ...
 * Bong!!!!


--1600365445.38f780.16407
Date: Thu, 17 Sep 2020 17:57:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176687
           Summary: VUL-0: CVE-2020-25412: gnuplot: segmentation fault in com_line () at command.c, which may result in context-dependent arbitrary code execution
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
               URL: https://smash.suse.de/issue/267556/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: werner-at-suse.com
          Reporter: wolfgang.frisch-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2020-25412

gnuplot 5.4 is affected by a segmentation fault in com_line () at command.c,
which may result in context-dependent arbitrary code execution.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25412
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25412
https://sourceforge.net/p/gnuplot/bugs/2303/


body:
--1600416414.ca3fbbe20.2247
Date: Fri, 18 Sep 2020 08:06:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176706
           Summary: fpc PIE linking fails in Tumbleweed
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: aloisio-at-gmx.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I'm talking about the peazip package that's built with lazarus
which in turn relies on fpc.

I can build fpc examples in PIE mode without any apparent problem,
but I see this on x86_64/Tumbleweed:

> [  140s] /usr/bin/ld: /usr/lib64/fpc/3.2.0/units/x86_64-linux/rtl/si_c.o: relocation R_X86_64_PC32 against symbol `__libc_start_main@@GLIBC_2.2.5' can not be used when making a PIE object; recompile with -fPIE

fpc 3.2.0 is also used on Leap 15.2 but there is no error.

Is this possibly related to glibc? I'm at my wits' end here.

summary: fpc PIE linking fails in Tumbleweed


--1600462949.ea4aCa3.26136
Date: Fri, 18 Sep 2020 21:02:29 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176733
           Summary: VUL-0: tigervnc: certificate exceptions stored as authorities
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: sndirsch-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: eich-at-suse.com, security-team-at-suse.de,
                    sndirsch-at-suse.com
          Found By: ---
           Blocker: ---

A security issue was discovered in tigernc related how the viewers handle TLS
certificate exceptions. Tigervnc before 1.11.0 stored the certificates as
authorities, meaning that the owner of that certificate could impersonate any
server it wanted after a client had added an exception. Tigervnc 1.11.0 handles
this properly by only storing exceptions for specific hostname/certificate
combinations, as done by HTTP user agents or SSH.

References:
From https://github.com/TigerVNC/tigervnc/releases/tag/v1.11.0
https://github.com/TigerVNC/tigervnc/commit/b30f10c681ec87720cff85d490f67098568a9cba
https://github.com/TigerVNC/tigervnc/commit/20dea801e747318525a5859fe4f37c52b05310cb


body:
--1600513667.4b074bF0.7948
Date: Sat, 19 Sep 2020 11:07:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176737
           Summary: [trackerbug] lxd 4.6 update
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Containers
          Assignee: containers-bugowner-at-suse.de
          Reporter: asarai-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

- Update to LXD 4.6. The full upstream changelog is available from:
  https://discuss.linuxcontainers.org/t/lxd-4-6-has-been-released/8981

  + Networks in projects
  + AppArmor profiles for qemu
  - Removal of custom sqlite fork.

summary: [trackerbug] lxd 4.6 update


--1600550962.c2E70.16718
Date: Sat, 19 Sep 2020 21:29:22 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176742
           Summary: AUDIT-0: plasma5-disks (suse-dbus-unauthorized-service, polkit-untracked-privilege)
    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: fabian@ritter-vogt.de
        QA Contact: qa-bugs-at-suse.de
                CC: opensuse-kde-bugs-at-opensuse.org
          Found By: ---
           Blocker: ---

Hi,

Plasma 5.20 includes a new component which warns the user if SMART values of
disks are critical.
For this it uses a KAuth helper with calls smartctl with the provided device.

The two D-Bus service files found by rpmlint are:

- /usr/share/dbus-1/system-services/org.kde.kded.smart.service
- /usr/share/dbus-1/system.d/org.kde.kded.smart.conf

Code used by the helper:

- https://invent.kde.org/plasma/plasma-disks/-/blob/master/src/helper.cpp
- https://invent.kde.org/plasma/plasma-disks/-/blob/master/src/helper.h
-
https://invent.kde.org/plasma/plasma-disks/-/blob/master/src/org.kde.kded.smart.actions

A package including these features is available at
https://build.opensuse.org/package/show/home:Vogtinator:plasma-disks/plasma5-disks
and once the .spec got reviewed at
https://build.opensuse.org/package/show/KDE:Unstable:Frameworks/plasma5-disks


--1600667573.7BAF8300.1708
Date: Mon, 21 Sep 2020 05:52:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176750
           Summary: Desktop backgrounds in KDE broken with multiple monitors on TW20200917
    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: opensuse-at-trummer.xyz
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since upgrading to TW20200917, desktop backgrounds in KDE are broken when using
multiple screens.

For example, when you have screens with different resolutions, setting a
wallpaper for the smaller screen will make it overflow into the bigger screen
next to it.
The "background area" for the bigger screen will begin offset to the right, as
if the background size was calculated from the wrong screen each time.

Additionally, some of my plasmoids appeared on a wrong screen when starting KDE
Plasma today.

However, the screen layout is still correct in System Settings, and windows
maximize to the correct screen borders. It's just the background and plasmoids
that have gone haywire.

Operating System: openSUSE Tumbleweed 20200917
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.1


--1600694760.1e8FB4e0.7052
Date: Mon, 21 Sep 2020 13:26:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176775
           Summary: Problems after upgrade to openSUSE Leap 15.2
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: tbazant-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After upgrade from 15.1 to 15.2 on my Dell Latitude 5300 2-in-1, the following
happened:

* network link dies after ~ 20 minutes of operations (both ethernet & wi-fi)
* audio problems (microphone did not work)
* `journalctl -f` was fludded with the following message:

"hid-sensor-hub 001F:8087:0AC2.0002: hid_field_extract() called with n (192)"


--1600760749.e54fa7e40.2820
Date: Tue, 22 Sep 2020 07:45:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176791
           Summary: VUL-0: CVE-2020-15960,CVE-2020-15961,CVE-2020-15962,CVE-2020- 15963,CVE-2020-15964,CVE-2020-15965,CVE-2020-15966: chromium: Update to 85.0.4183.121
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: tchvatal-at-suse.com
          Reporter: rfrohl-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The stable channel has been updated to 85.0.4183.121 for Windows, Mac, and
Linux, which will roll out over the coming days/weeks.

A list of all changes is available in the log. Interested in switching release
channels?  Find out how. If you find a new issue, please let us know by filing
a bug. The community help forum is also a great place to reach out for help or
learn about common issues.

Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority
of users are updated with a fix. We will also retain restrictions if the bug
exists in a third party library that other projects similarly depend on, but
haven’t yet fixed.

This update includes 10 security fixes. Below, we highlight fixes that were
contributed by external researchers. Please see the Chrome Security Page for
more information.

High CVE-2020-15960: Out of bounds read in storage. Reported by Anonymous on
2020-06-28

High CVE-2020-15961: Insufficient policy enforcement in extensions. Reported by
David Erceg on 2020-08-10

High CVE-2020-15962: Insufficient policy enforcement in serial. Reported by
Leecraso and Guang Gong of 360 Alpha Lab working with 360 BugCloud on
2020-08-26

High CVE-2020-15963: Insufficient policy enforcement in extensions. Reported by
David Erceg on 2020-08-06

High CVE-2020-15965: Out of bounds write in V8. Reported by Lucas Pinheiro,
Microsoft Browser Vulnerability Research on 2020-09-08

Medium CVE-2020-15966: Insufficient policy enforcement in extensions. Reported
by David Erceg on 2020-08-06

Low CVE-2020-15964: Insufficient data validation in media. Reported by Woojin
Oh(@pwn_expoit) of STEALIEN on 2020-08-25

As usual, our ongoing internal security work was responsible for a wide range
of fixes:

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

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.

Many of our security bugs are detected using AddressSanitizer, MemorySanitizer,
UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.

https://chromereleases.googleblog.com/2020/09/stable-channel-update-for-desktop_21.html


--1600784079.F6cB7e0.4654
Date: Tue, 22 Sep 2020 14:14:39 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176818
           Summary: Wrong public keys in openSUSE-build-key for verifying container image signatures
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: meissner-at-suse.com
          Reporter: rhafer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: sgrunert-at-suse.com
          Found By: ---
           Blocker: ---

The openSUSE-build-keys package contains
/usr/lib/rpm/gnupg/keys/opensuse-container-key.asc and
/usr/lib/rpm/gnupg/keys/suse-container-key.asc which symlink to the "openSUSE
Project Signing Key <opensuse-at-opensuse.org>" and "SuSE Package Signing Key
<build-at-suse.de>" but apparently the images we provide on registry.opensuse.org
are signed by some other key.

When enabling signature verification for "registry.opensuse.org" using the key
"/usr/lib/rpm/gnupg/keys/opensuse-container-key.asc" all images fail to verify
because the images are signed with a different key. Looking into the
signatures, which are fetched from "https://registry.opensuse.org/sigstore/" it
seem the images are signed by a key with the ID "D754694F9AB48CE9".

The key in /usr/lib/rpm/gnupg/keys/opensuse-container-key.asc however AFAICS
is: "B88B2FD43DBDC284".

So something is wrong here.


--1600808818.A1C4de31.5297
Date: Tue, 22 Sep 2020 21:06:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176832
           Summary: [Build 20200921] openQA test fails in inkscape - missing conflict between python-numpy and python3-numpy
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/1401504/modules/inks
                    cape/steps/12
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: stefan.bruens@rwth-aachen.de
        QA Contact: qa-bugs-at-suse.de
          Found By: openQA
           Blocker: ---

## Observation

openQA test in scenario
opensuse-Tumbleweed-DVD-x86_64-upgrade_Leap_42.1_kde@64bit fails in
[inkscape](https://openqa.opensuse.org/tests/1401504/modules/inkscape/steps/12)

## Test suite description

## Reproducible

Fails since (at least) Build
[20200921](https://openqa.opensuse.org/tests/1401504) (current job)

## Expected result

Last good: [20200919](https://openqa.opensuse.org/tests/1401086) (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=upgrade_Leap_42.1_kde&version=Tumbleweed)


--1600893547.aEab0.22763
Date: Wed, 23 Sep 2020 20:39:07 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176888
           Summary: Warning: The code model could not parse an included file, which might lead...
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: marcelo.jimenez-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

This bug has been reported upstream before. We have come to the conclusion that
the problem is downstream. The link to the upstream bug report is this:
https://bugreports.qt.io/browse/QTCREATORBUG-24583

I have a custom toolkit in a separate folder.

I have added the toolkit manually.

QT Creator claims it cannot find the file stddef.h. But even while displaying
the red circle in the left margin, I am able to <CTRL>-click the file and the
editor is able to find it.

If I do:

$
/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/bin/arm-buildroot-linux-gnueabi-cpp
-v
Using built-in specs.
COLLECT_GCC=/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/bin/arm-buildroot-linux-gnueabi-cpp.br_real
Target: arm-buildroot-linux-gnueabi
Configured with: ./configure
-prefix=/home/mroberto/cpti/hg/pig/buildroot/output/host
--sysconfdir=/home/mroberto/cpti/hg/pig/buildroot/output/host/etc
--enable-static --target=arm-buildroot-linux-gnueabi
--with-sysroot=/home/mroberto/cpti/hg/pig/buildroot/output/host/arm-buildroot-linux-gnueabi/sysroot
--enable__cxa_atexit --with-gnu-ld --disable-libssp --disable-multilib
--disable-decimal-float
--with-gmp=/home/mroberto/cpti/hg/pig/buildroot/output/host
--with-mpc=/home/mroberto/cpti/hg/pig/buildroot/output/host
--with-mpfr=/home/mroberto/cpti/hg/pig/buildroot/output/host
--with-pkgversion='Buildroot 2019.11-00018-g90fba2ca74-dirty'
--with-bugurl=http://bugs.buildroot.net/ --disable-libquadmath --enable-tls
--enable-threads --without-isl --without-cloog --with-float=soft
--with-abi=aapcs-linux --with-cpu=arm926ej-s --with-float=soft --with-mode=arm
--enable-languages=c,c++
--with-build-time-tools=/home/mroberto/cpti/hg/pig/buildroot/output/host/arm-buildroot-linux-gnueabi/bin
--enable-shared --disable-libgomp
Thread model: posix
gcc version 9.2.0 (Buildroot 2019.11-00018-g90fba2ca74-dirty)
COLLECT_GCC_OPTIONS='-E' '-v' '-mcpu=arm926ej-s' '-mfloat-abi=soft'
'-mabi=aapcs-linux' '-marm' '-mtls-dialect=gnu' '-march=armv5tej'
/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/bin/../libexec/gcc/arm-buildroot-linux-gnueabi/9.2.0/cc1
-E -quiet -v -iprefix
/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/bin/../lib/gcc/arm-buildroot-linux-gnueabi/9.2.0/
-isysroot
/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/arm-buildroot-linux-gnueabi/sysroot
- -mcpu=arm926ej-s -mfloat-abi=soft -mabi=aapcs-linux -marm -mtls-dialect=gnu
-march=armv5tej
ignoring duplicate directory
"/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/bin/../lib/gcc/../../lib/gcc/arm-buildroot-linux-gnueabi/9.2.0/include"
ignoring nonexistent directory
"/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/arm-buildroot-linux-gnueabi/sysroot/usr/local/include"
ignoring duplicate directory
"/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/bin/../lib/gcc/../../lib/gcc/arm-buildroot-linux-gnueabi/9.2.0/include-fixed"
ignoring duplicate directory
"/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/bin/../lib/gcc/../../lib/gcc/arm-buildroot-linux-gnueabi/9.2.0/../../../../arm-buildroot-linux-gnueabi/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/bin/../lib/gcc/arm-buildroot-linux-gnueabi/9.2.0/include
/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/bin/../lib/gcc/arm-buildroot-linux-gnueabi/9.2.0/include-fixed
/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/bin/../lib/gcc/arm-buildroot-linux-gnueabi/9.2.0/../../../../arm-buildroot-linux-gnueabi/include
/usr/local/toolchains/arm-buildroot-linux-gnueabi_sdk-buildroot-kh_4.9-gcc_9-arm/arm-buildroot-linux-gnueabi/sysroot/usr/include
End of search list.

From this list, I got the four paths that could be giving me trouble. If I add
them to the .includes file the code model works perfectly without warnings.

Not being able to find stddef.h causes lots of error and warning messages on
the code model, rendering it useless. Also, my workaround of including the
paths in a .include file should not be necessary.


--1600925664.00F6a0.5640
Date: Thu, 24 Sep 2020 05:34:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176894
           Summary: [Build 20200922] wine not sure installable
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/1403219/modules/wine
                    /steps/23
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dleuenberger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: openQA
           Blocker: ---

## Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_on_kde@64bit
fails in
[wine](https://openqa.opensuse.org/tests/1403219/modules/wine/steps/23)

Wine requires wine-32bit, that cannot be provided

## Test suite description

## Reproducible

Fails since (at least) Build
[20200922](https://openqa.opensuse.org/tests/1403219) (current job)

## Expected result

Last good: [20200921](https://openqa.opensuse.org/tests/1401531) (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_on_kde&version=Tumbleweed)


body:
--1600945506.2FEE0680.25568
Date: Thu, 24 Sep 2020 11:05:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176907
           Summary: klp tests fail: btrfs related problems
    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: petr.vorel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 841904
  --> https://bugzilla.suse.com/attachment.cgi?id=841904&action=edit
Detailed log

KLP tests fail on Tumbleweed since build 20200824 on btrfs related problems
(5.8.0).
Confirmed running manually on my machine (5.9.0-rc6-2.g289d4e9-default).

Testing on
https://github.com/lpechacek/qa_test_klp.git

kernel: 5.9.0-rc6-2.g289d4e9-default
/ on ext4, /tmp on tmpfs

# ./run.sh (rest is in attached log)
 ✗ Patch under pressure
   (in test file /tmp/tmp.SYdnCZlYmp, line 4)
     `./klp_tc_3.sh' failed
   [12:41:58] Test Case 3: Patch under pressure
   [12:41:58] *** Compiling kernel live patch
   [12:41:58] make: Entering directory
'/usr/src/linux-5.9.0-rc6-2.g289d4e9-obj/x86_64/default'
   [12:41:59]   CC [M]  /tmp/live-patch/tc_3/klp_tc_3_livepatch.o
   [12:41:59]   MODPOST /tmp/live-patch/tc_3/Module.symvers
   [12:42:00]   CC [M]  /tmp/live-patch/tc_3/klp_tc_3_livepatch.mod.o
   [12:42:00]   LD [M]  /tmp/live-patch/tc_3/klp_tc_3_livepatch.ko
   [12:42:00] make: Leaving directory
'/usr/src/linux-5.9.0-rc6-2.g289d4e9-obj/x86_64/default'
   [12:42:00] *** Compiling call_getpid
   [12:42:00] *** Running call_getpid
   [12:42:00] *** Inserting getpid patch
   [12:42:00] *** Wait for completion
   [12:43:03] transitioning patch path:
"/sys/kernel/livepatch/klp_tc_3_livepatch"
   [12:43:03] ksoftirqd/0 (10/10) still in progress:
   [12:43:03] =============
   [12:43:03]
   [12:43:03] rcu_sched (11/11) still in progress:
   [12:43:03] =============
   [12:43:03]
   [12:43:04] btrfs-worker (1140/1140) still in progress:
   [12:43:04] =============
----
Attached a detailed log on my intel machine.

Visible also in openQA on both archs tested:
* intel (5.8.10-1-default)
https://openqa.opensuse.org/tests/1403386/file/serial0.txt
https://openqa.opensuse.org/tests/1403386/file/serial_terminal.txt

* ppc64le (5.8.10-1-default)
https://openqa.opensuse.org/tests/1402900/file/serial0.txt
https://openqa.opensuse.org/tests/1402900/file/serial_terminal.txt

I overlooked this issue because I before I reported to lpechacek over mail
different error (ftrace interface, ppc64le specific).

summary: klp tests fail: btrfs related problems


--1600948022.28f320.23387
Date: Thu, 24 Sep 2020 11:47:02 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176908
           Summary: VUL-1: CVE-2020-25863: wireshark: MIME Multipart dissector crash
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: rfrohl-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

It may be possible to make Wireshark crash by injecting a malformed packet onto
the wire or by convincing someone to read a malformed packet trace file. The
MIME Multipart dissector could crash.

Affected versions: 3.2.0 to 3.2.6, 3.0.0 to 3.0.13, 2.6.0 to 2.6.20
Fixed versions: 3.2.7, 3.0.14, 2.6.20

References:
https://www.wireshark.org/security/wnpa-sec-2020-12
https://gitlab.com/wireshark/wireshark/-/issues/16816


--1600948025.C612DF70.26857
Date: Thu, 24 Sep 2020 11:47:05 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176909
           Summary: VUL-1: CVE-2020-25862: wireshark: TCP dissector crash
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: rfrohl-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

It may be possible to make Wireshark crash by injecting a malformed packet onto
the wire or by convincing someone to read a malformed packet trace file. The
TCP dissector could crash.

Affected versions: 3.2.0 to 3.2.6, 3.0.0 to 3.0.13, 2.6.0 to 2.6.20
Fixed versions: 3.2.7, 3.0.14, 2.6.20

References:
https://www.wireshark.org/security/wnpa-sec-2020-12
https://gitlab.com/wireshark/wireshark/-/issues/16816


--1600948027.3cAbA10.23493
Date: Thu, 24 Sep 2020 11:47:07 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176910
           Summary: VUL-1: CVE-2020-25866: wireshark: BLIP dissector crash
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: rfrohl-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

It may be possible to make Wireshark crash by injecting a malformed packet onto
the wire or by convincing someone to read a malformed packet trace file. The
BLIP dissector could crash.

Affected versions: 3.2.0 to 3.2.6, 3.0.0 to 3.0.13
Fixed versions: 3.2.7, 3.0.14

References:
https://www.wireshark.org/security/wnpa-sec-2020-13
https://gitlab.com/wireshark/wireshark/-/issues/16866


--1600956906.E48e0ecc2.5843
Date: Thu, 24 Sep 2020 14:15:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176927
           Summary: [Staging][Build M.160.1] YaST crashes with latest timezone submission
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/1403079/modules/part
                    itioning_finish/steps/2
                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: openQA
           Blocker: ---

## Observation

openQA test in scenario opensuse-Staging:M-Staging-DVD-x86_64-cryptlvm@64bit
fails in
[partitioning_finish](https://openqa.opensuse.org/tests/1403079/modules/partitioning_finish/steps/2)

yast seems to segfault, as the output on the serial output indicates:
  begin 644 y2start.core.pid_3451.sig_6.time_1600866699

## Test suite description
Maintainers: okurz

Conduct installation with encrypted LVM selected during installation.

## Reproducible

Fails since (at least) Build
[M.160.1](https://openqa.opensuse.org/tests/1403079) (current job)

## Expected result

Last good: [M.157.1](https://openqa.opensuse.org/tests/1402932) (or more
recent)

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=Staging-DVD&machine=64bit&test=cryptlvm&version=Staging%3AM)


--1601041979.7dD2c0.1686
Date: Fri, 25 Sep 2020 13:52:59 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176987
           Summary: VUL-0: CVE-2019-11556: pagure: XSS via the templates/blame.html blame view.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
               URL: https://smash.suse.de/issue/268275/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: ngompa13-at-gmail.com
          Reporter: rfrohl-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2019-11556

Pagure before 5.6 allows XSS via the templates/blame.html blame view.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-11556
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11556
https://docs.pagure.org/pagure/changelog.html
https://pagure.io/pagure/c/31a0d2950ed409550074ca52ba492f9b87ec3318?branch=ab39e95ed4dc8367e5e146e6d9a9fa6925b75618
https://pagure.io/pagure/commits/master


--1601043189.03D87E2.19695
Date: Fri, 25 Sep 2020 14:13:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1176989
           Summary: [Build 20200924] openQA test fails in transactional_update: /etc/shadow lost contents
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/1406389/modules/tran
                    sactional_update/steps/29
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kubic
          Assignee: iforster-at-suse.com
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: dimstar-at-opensuse.org, kubic-bugs-at-opensuse.org
          Found By: openQA
           Blocker: ---

Created attachment 841955
  --> https://bugzilla.suse.com/attachment.cgi?id=841955&action=edit
Serial log of openQA run with manual debugging

## Observation

openQA test in scenario microos-Tumbleweed-MicroOS-Image-x86_64-microos@64bit
fails in
[transactional_update](https://openqa.opensuse.org/tests/1406389/modules/transactional_update/steps/29)

After the update to the new /etc overlay handling, this test fails.

What happens is:
0. First boot inside the initrd. /sysroot is snapshot 1, its etc is the
matching overlay mount
1. Ignition runs, executing usermod to change root's password in
/sysroot/etc/shadow. This ends up in /var/lib/overlay/1/etc/shadow.
2. Combustion runs, executing transactional-update shell (doing nothing of
relevance inside), resulting in snapshot 2
3. Old /sysroot is umounted and snapshot 2 mounted instead and booted into
4. openQA runs transactional-update ptf install, resulting in snapshot 3, and
does a reboot
5. After the reboot, login is not possible as /etc/shadow is incomplete.

/.snapshots/3/snapshot/etc/fstab has this (see end of the attached serial log):
overlay /etc overlay
defaults,upperdir=/sysroot/var/lib/overlay/3/etc,lowerdir=/sysroot/var/lib/overlay/2/etc:/sysroot/etc,workdir=/sysroot/var/lib/overlay/work-etc,...
0 0

/var/lib/overlay/1/etc/shadow, where the password was set, is missing.
AFAICT, it should've been synced into snapshot 3, but that did not happen:

transactional-update 2.25.1 started
Options: --no-selfupdate ptf install
update-test-trivial/update-test-security-5-2.1.x86_64.rpm
Separate /var detected.
/etc on overlayfs detected.
Calling zypper install
Loading repository data...
[...]
New default snapshot is #3 (/.snapshots/3/snapshot).
transactional-update finished

For some reason I fail to reproduce the issue locally...


body:
--1601076325.e260F7Eb0.2955
Date: Fri, 25 Sep 2020 23:25:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1177001
           Summary: Missing python module for carla-control
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: davejplater-at-gmail.com
          Reporter: mrueckert-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

carla-control
LRDF Support not available (LADSPA-RDF will be disabled)
Traceback (most recent call last):
  File "/usr/share/carla/carla-control", line 22, in <module>
    from carla_control import *
  File "/usr/share/carla/carla_control.py", line 34, in <module>
    from liblo import (
ModuleNotFoundError: No module named 'liblo'

pkgs: carla python-pyliblo

summary: Missing python module for carla-control


--1601205916.AF0b7Ce10.30935
Date: Sun, 27 Sep 2020 11:25:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1177016
           Summary: Following TW snapshot 20200925 mkinitrd/dracut segfaults at "*** Including module: kernel-modules ***"
    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: paul.pgp-7-at-gmx.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I've just updated a TW install 20200922 -> 20200925 following which
mkinitrd/dracut consistently segfaults at "*** Including module: kernel-modules
***"

dracut: *** Including module: kernel-modules ***
/usr/lib/dracut/dracut-init.sh: line 252:  9956 Segmentation fault      (core
dumped) $DRACUT_INSTALL ${dracutsysrootdir:+-r "$dracutsysrootdir"}
${initdir:+-D "$initdir"} ${loginstall:+-L "$loginstall"} ${hostonly:+-H}
${check_supported:+--check-supported} ${omit_drivers:+-N "$omit_drivers"}
${srcmods:+--kerneldir "$srcmods"} -m "$@"
dracut: FAILED: /usr/lib/dracut/dracut-install -D
/var/tmp/dracut.d0WfeQ/initramfs -H -N i2o_scsi --kerneldir
/lib/modules/5.8.7-1-default/ -m -o -s
ahci_platform_get_resources|ata_scsi_ioctl|scsi_add_host|blk_cleanup_queue|register_mtd_blktrans|scsi_esp_register|register_virtio_device|usb_stor_disconnect|mmc_add_host|sdhci_add_host|scsi_add_host_with_dma
=drivers
dracut: *** Including module: kernel-modules-extra ***

See also
https://forums.opensuse.org/showthread.php/545119-mkinitrd-dracut-error-after-TW-20200925


--1601252395.2AD50.28609
Date: Mon, 28 Sep 2020 00:19:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1177021
           Summary: Please add support for RTL8761b bluetooth adapter
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: aaronw-at-doofus.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The following page describes a patch that adds support for this Bluetooth 5.0
chip: https://gist.github.com/rometsch/dfd24fb09c85c1ad2f25223dc1481aaa