--1603822253.d42D10.19425
Date: Tue, 27 Oct 2020 18:10:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178203
           Summary: sound is broken at 5.3.18-lp152.44-default with Steinberg UR22C card
    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: matwey.kornilov-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,

I am running openSUSE Leap 15.2 and found that recent update to
kernel-default-5.3.18-lp152.44 introduced the following 100% reproducible issue
with audio for me.

pulseaudio-13.0-lp152.2.3.x86_64

I use external USB sound card Steinber UR22C card with the following
device/vendor IDs:

Bus 004 Device 003: ID 0499:172f Yamaha Corp.

The device is handled by snd_usb_audio kernel module.

Steps to reproduce:

1. Update to kernel-default-5.3.18-lp152.44

2. Run some YouTube video in Firefox MozillaFirefox-78.4.0-lp152.2.24.1.x86_64

3. Start Telegram Desktop from the recent flatpak package during the video
play:
# flatpak run org.telegram.desktop

Actual result:

At this moment, the sound hangs in the Firefox instance, both video and audio
stop and YouTube UI became irresponsible (for instance, I cannot rewind the
video in player). It feels like some sound sink call in FireFox is unexpectedly
blocked for some reason.
There is also no any sound in any other applications. I have not found a way to
recover from this state, except restarting pulseaudio server.

Expected result:

Sound keeps playing during Telegram Desktop startup.

I suppose that the issue may be related to
https://github.com/openSUSE/kernel/commit/7c5b892e0871655fea3294ffac6fa3cc3400b60d


--1603825591.58d71F0.21819
Date: Tue, 27 Oct 2020 19:06:31 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178205
           Summary: VUL-0: redis: potential heap overflow when using a heap allocator other than jemalloc or glibc's malloc
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: mrueckert-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: ---

Redis 6.0.9 fixes a potential heap overflow when using a heap allocator other
than jemalloc or glibc's malloc.

When using a system with no malloc_usable_size(), zmalloc_size() assumed
that the heap allocator always returns blocks that are long-padded.

This may not always be the case, and will result with zmalloc_size()
returning a size that is bigger than allocated. At least in one case
this leads to out of bound write, process crash and a potential security
vulnerability.

Effectively this does not affect the vast majority of users, who use
jemalloc or glibc.

https://raw.githubusercontent.com/redis/redis/6.0/00-RELEASENOTES
https://github.com/redis/redis/pull/7963


--1603840083.1BfEEF0.452
Date: Tue, 27 Oct 2020 23:08:03 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178209
           Summary: Nextcloud desktop cannot open main dialogue due to missing dependencies
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: tux93-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

nextcloud-destktop, starting with 3.0.0, fails to open the new main dialogue on
Xfce due to missing dependencies

> 2020-10-27 23:50:45:659 [ warning default ]:	QQmlApplicationEngine failed to load component
> 2020-10-27 23:50:45:660 [ warning default ]:	qrc:/qml/src/gui/tray/Window.qml:7:1: module "QtGraphicalEffects" is not installed
> 2020-10-27 23:50:45:660 [ warning default ]:	qrc:/qml/src/gui/tray/Window.qml:5:1: module "QtQuick.Controls" is not installed
> 2020-10-27 23:50:45:660 [ warning default ]:	qrc:/qml/src/gui/tray/Window.qml:7:1: module "QtGraphicalEffects" is not installed
> 2020-10-27 23:50:45:660 [ warning default ]:	qrc:/qml/src/gui/tray/Window.qml:5:1: module "QtQuick.Controls" is not installed

After manually installing the missing packages `libqt5-qtgraphicaleffects` and
`libqt5-qtquickcontrols2` the main dialogue can be opened


--1603968957.e7cc583F0.27450
Date: Thu, 29 Oct 2020 10:55:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178257
           Summary: rpm-build-python needs setuptools but cannot require on it
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: code-at-bnavigator.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Some packages can build without python-setuptools and thus do not depend on it.
In this case /usr/lib/rpm/pythondistdeps.py fails in rpm packaging phase:

[   17s] Traceback (most recent call last):
[   17s]   File "/usr/lib/rpm/pythondistdeps.py", line 105, in <module>
[   17s]     from pkg_resources import Distribution, FileMetadata,
PathMetadata, Requirement
[   17s] ModuleNotFoundError: No module named 'pkg_resources'

But rpm-build-python depending on python-setuptools is not possible, because
that would create a dependency loop with setuptools and its build dependencies
(python-ordered-set)


--1604054642.4FE380.15841
Date: Fri, 30 Oct 2020 10:44:02 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178296
           Summary: /usr/etc/skel handling completely broken
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

node128:~ # useradd -r -d /var/lib/test0 test0
chown: cannot access '/home/test0/bin': No such file or directory

node128:~ # ls -alF /home/
total 0
drwxr-xr-x. 1 root root  62 Oct 30 10:39 ./
drwxr-xr-x. 1 root root 142 Oct 30 10:27 ../
drwx------. 1 root root  30 Oct 30 10:19 chrony/
drwx------. 1 root root  30 Oct 30 10:19 messagebus/
drwx------. 1 root root  30 Oct 30 10:19 nobody/
drwx------. 1 root root  30 Oct 30 10:19 sshd/
drwxr-xr-x. 1 root root  38 Oct 30 10:39 test0/

useradd.local creates for every system account a directory below /home, owned
by root, for copying the /usr/etc/skel files.

The current implementation seems to work only for standard users, where the
home directory is below /home, but not for system accounts, not if the
homedirectory is somewhere else, not if the skel directory shouldn't be copied
at all.

I'm afraid we need to patch the shadow suite (useradd) directly instead of
using the useradd.local helper.


--1604072695.777F70Fa0.15207
Date: Fri, 30 Oct 2020 15:44:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178306
           Summary: error: request firmware intel/sof/sof-tgl.ri failed err: -2
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: lmb-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On the Dell XPS 13, looks like the kernel is trying to load a non-existent
audio driver firmware:

[   15.907191] idma64 idma64.1: Found Intel integrated DMA 64-bit
[   15.912927] snd_hda_intel 0000:00:1f.3: DSP detected with PCI
class/subclass/prog-if info 0x040100
[   15.912930] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+
platform, using SOF driver
[   15.988359] i2c_hid i2c-DLL0945:00: supply vdd not found, using dummy
regulator
[   15.988376] i2c_hid i2c-DLL0945:00: supply vddl not found, using dummy
regulator
[   16.011076] input: Dell WMI hotkeys as
/devices/platform/PNP0C14:02/wmi_bus/wmi_bus-PNP0C14:02/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input17
[   16.020321] sof-audio-pci 0000:00:1f.3: DSP detected with PCI
class/subclass/prog-if info 0x040100
[   16.020325] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+
platform, using SOF driver
[   16.020338] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002)
[   16.020661] sof-audio-pci 0000:00:1f.3: DSP detected with PCI
class/subclass/prog-if 0x040100
[   16.020775] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops
i915_audio_component_bind_ops [i915])
[   16.027386] sof-audio-pci 0000:00:1f.3: use msi interrupt mode
[   16.035823] i2c i2c-15: 8/8 memory slots populated (from DMI)
[   16.035824] i2c i2c-15: Systems with more than 4 memory slots not supported
yet, not instantiating SPD
[   16.074627] input: PC Speaker as /devices/platform/pcspkr/input/input18
[   16.074874] pstore: Efi pstore disabled, enforce via pstore.backend=efi
[   16.074874] pstore: On a broken BIOS, this can severely harm your system
[   16.074874] pstore: Only enable efi based pstore when you know what you are
doing
[   16.087833] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5
[   16.087834] sof-audio-pci 0000:00:1f.3: using HDA machine driver
skl_hda_dsp_generic now
[   16.087837] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2
[   16.088661] sof-audio-pci 0000:00:1f.3: Direct firmware load for
intel/sof/sof-tgl.ri failed with error -2
[   16.088663] sof-audio-pci 0000:00:1f.3: error: request firmware
intel/sof/sof-tgl.ri failed err: -2
[   16.088666] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware
-2
[   16.088978] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2


--1604088752.c2EE50260.24003
Date: Fri, 30 Oct 2020 20:12:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178312
           Summary: Updated perl-WebService-MusicBrainz breaks abcde in Tumbleweed 20201028
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: David@WalkerStreet.info
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Upgrading to Tumbleweeed 20201028 resulted in:

  Problem: abcde-2.9.3-4.3.noarch requires perl(WebService::MusicBrainz) =
1.0.4, but this requirement cannot be provided
    deleted providers: perl-WebService-MusicBrainz-1.0.4-1.6.noarch
   Solution 1: deinstallation of abcde-2.9.3-4.3.noarch
   Solution 2: keep obsolete perl-WebService-MusicBrainz-1.0.4-1.6.noarch
   Solution 3: break abcde-2.9.3-4.3.noarch by ignoring some of its
dependencies


--1604143335.670c3AD0.30423
Date: Sat, 31 Oct 2020 11:22:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178321
           Summary: AUDIT-0: udisks2: 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: milsav92-at-outlook.com
        QA Contact: security-team-at-suse.de
          Found By: ---
           Blocker: ---

libudisks2-0_lsm.x86_64: E: polkit-untracked-privilege (Badness: 10)
org.freedesktop.udisks2.lsm.manage-led (auth_admin:auth_admin:auth_admin_keep)
The privilege is not listed in /etc/polkit-default-privs.*         which makes
it harder for admins to find. Furthermore polkit         authorization checks
can easily introduce security issues. If the         package is intended for
inclusion in any SUSE product please open         a bug report to request
review of the package by the security team.         Please refer to
https://en.opensuse.org/openSUSE:Package_security_guidelines#audit_bugs for
more information.

It seems it was renamed from:
org.freedesktop.udisks2.manage-led
to:
org.freedesktop.udisks2.lsm.manage-led
in commit 6cef50624596e3f128698adb1402b389bad4792c

https://github.com/storaged-project/udisks/commit/6cef50624596e3f128698adb1402b389bad4792c#diff-dd9c6b44381920d6c381940478c9503ed164f828932d790865650fd6b40d32ae

which was released as part of usidsk2-2.9.0

PS. Is seems that when I branched Base:System/udisks2 I didn't pay attention to
the fact that Base:System has:
Support: !rpmlint-Factory
set as a project configuration which propagated to the branched project.


--1604253184.E40540.27855
Date: Sun, 1 Nov 2020 17:53:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178330
           Summary: Customer kernel module build leaves null.000i.ipa-clones after "make clean"
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: snguyen-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hi

When I am cleaning up a directory that contains customer modules (make clean),
I am always left with a file called null.000i.ipa-clones.

Here is an example:
-rw-r--r


--1604305030.7ff8EEa0.20066
Date: Mon, 2 Nov 2020 08:17:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178341
           Summary: python-paramiko requires newer pythin-cryptography
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mark-at-overmeer.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

(not the same as 1020340)
python3-paramiko 2.4.2 is broken by python3-cryptography 2.8, which has changed
its interface.  This, in its turn, breaks duplicity.

Manually installing the newest paramiko (3.7.2) solves the problem.

/usr/lib/python3.6/site-packages/paramiko/kex_ecdh_nist.py:111:
CryptographyDeprecationWarning: encode_point has been deprecated on
EllipticCurvePublicNumbers and will be removed in a future version. Please use
EllipticCurvePublicKey.public_bytes to obtain both compressed and uncompressed
point encoding.
  hm.add_string(self.Q_C.public_numbers().encode_point())
BackendException: ssh connection to backups@mars:22 failed: private_value must
be an integer type.


--1604416888.84DC0A0.9780
Date: Tue, 3 Nov 2020 15:21:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178401
           Summary: errors in OBS builds from kernel+initrd, e.g. "dracut-pre-udev[231]: modprobe: FATAL: Module ext2 not found in directory /lib/modules/5.8.15-1-default"
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: okurz-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

## Observation

Originally reported in
https://github.com/openSUSE/open-build-service/issues/10341#issue-728442525 the
OBS build logs are full of errors and warnings which the OBS maintainers
designated as issues coming from kernel and/or coming from initrd, e.g.:

```
[   22s] Booting from ROM..c[?7l[2J[    2.619073] dracut-pre-udev[229]:
modprobe: FATAL: Module kqemu not found in directory
/lib/modules/5.8.15-1-default
[   22s] [    2.632643] dracut-pre-udev[231]: modprobe: FATAL: Module ext2 not
found in directory /lib/modules/5.8.15-1-default
[   22s] [    2.636965] dracut-pre-udev[232]: modprobe: FATAL: Module ext3 not
found in directory /lib/modules/5.8.15-1-default
[   23s] [    3.394114] dracut-pre-udev[245]: modprobe: FATAL: Module
nf_conntrack_ipv6 not found in directory /lib/modules/5.8.15-1-default
[   23s] [    3.492219] dracut-pre-udev[256]: modprobe: FATAL: Module ibmvscsi
not found in directory /lib/modules/5.8.15-1-default
[   23s] [    3.525927] dracut-pre-udev[259]: modprobe: FATAL: Module ibmveth
not found in directory /lib/modules/5.8.15-1-default
…

[   30s] /sbin/unix2_chkpwd: setting to root:shadow 4755 (wrong owner/group
root:root)
[   30s] /sbin/unix_chkpwd: setting to root:shadow 4755 (wrong owner/group
root:root)
[   30s] /usr/bin/mount: setting to root:root 4755 (wrong permissions 0755)
[   30s] /usr/bin/su: setting to root:root 4755 (wrong permissions 0755)
[   30s] /usr/bin/umount: setting to root:root 4755 (wrong permissions 0755)
…
[   34s] /usr/bin/mount: setting to root:root 4755 (wrong permissions 0755)
[   34s] /usr/bin/umount: setting to root:root 4755 (wrong permissions 0755)
[   34s] /usr/bin/wall: setting to root:tty 2755 (wrong permissions 0755)
[   34s] /usr/bin/write: setting to root:tty 2755 (wrong permissions 0755)
[   34s] /usr/bin/su: setting to root:root 4755 (wrong permissions 0755)
[   34s] grep: /etc/default/su: No such file or directory
…
[   34s] /usr/bin/udevadm: error while loading shared libraries:
libsystemd-shared-246.so: cannot open shared object file: No such file or
directory
…
[   34s] /var/tmp/rpm-tmp.FNx2gQ: line 19: pam-config: command not found
…
[   34s] /usr/lib/tmpfiles.d/journal-nocow.conf:26: Failed to resolve
specifier: uninitialized /etc detected, skipping
…
[   34s] chown: cannot access '/home/dockremap/.config': No such file or
directory
…
[   53s] RTNETLINK answers: File exists
[   53s] RTNETLINK answers: File exists
```

## Steps to reproduce
Seemingly reproducible in any build of packages, e.g.
https://build.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/curl/_log
shows the same

## Expected result

Only errors in the log that I as package/project maintainer can fix


--1604563764.Cadba0.4909
Date: Thu, 5 Nov 2020 08:09:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178453
           Summary: [Build 20201103] gnuhealth_client crashes on start
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/1460183/modules/gnuh
                    ealth_client_first_time/steps/2
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: openQA
           Blocker: Yes

## Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-gnuhealth@64bit fails in
[gnuhealth_client_first_time](https://openqa.opensuse.org/tests/1460183/modules/gnuhealth_client_first_time/steps/2)

## Test suite description
Maintainer: okurz-at-suse.de
Test scenario for gnuhealth software stack

## Reproducible

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

## Expected result

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


body:
--1604583237.883BF5CB0.12616
Date: Thu, 5 Nov 2020 13:33:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178475
           Summary: permissions: does not use %optflags
    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: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

the permissions package is compiled without honoring %optflags

We even used to have check that makes sure all binaries do. Seems to be gone!?

summary: permissions: does not use %optflags


--1604583624.213E03d50.13293
Date: Thu, 5 Nov 2020 13:40:23 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178476
           Summary: permissions: missing large file support and not erroring out on stat fail
    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: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The chkstat program is built without large file support (-D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64) which can make it silently fail if it runs in a 32bit
userspace on filesystem of a 64bit host.
The code just silently fails:
https://github.com/openSUSE/permissions/blob/ece8520ae271152d88ad24968c3831417ce4732c/src/chkstat.cpp#L950

I ran into the issue when building i586 packages on x86_64 when /var/tmp ended
up with values that stat couldn't digest so was silently skipped and left with
wrong mode. As you can imagine that leads to mind boggling build fails :-)
Please compile with LFS.


body:
--1604585935.a8fF601.7732
Date: Thu, 5 Nov 2020 14:18:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178478
           Summary: [rpm4.16] apache2 fails to build
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Apache
          Assignee: bnc-team-apache-at-forge.provo.novell.com
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Tumbleweed is currently preparing to upgrade to RPM 4.16.

Apache2 is one of the packages failing this:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:A/apache2/standard/x86_64

>[  202s] Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.7LI2vq
>[  202s] + umask 022
>[  202s] + cd /home/abuild/rpmbuild/BUILD
>[  202s] + /usr/bin/rm -rf /home/abuild/rpmbuild/BUILDROOT/apache2-2.4.46-9.2.x86_64
>[  202s] + /usr/bin/mkdir -p /home/abuild/rpmbuild/BUILDROOT
>[  202s] + /usr/bin/mkdir /home/abuild/rpmbuild/BUILDROOT/apache2-2.4.46-9.2.x86_64
>[  202s] + cd httpd-2.4.46
>[  202s] + cat
>[  202s] /var/tmp/rpm-tmp.7LI2vq: line 36: /home/abuild/rpmbuild/BUILDROOT/apache2-2.4.46-9.2.x86_64//usr/lib64/apache2_MMN: No such file or directory
>[  202s] error: Bad exit status from /var/tmp/rpm-tmp.7LI2vq (%install)

The reson for this lies in the changed behavior of RPM 4.16, which forcibly
empties DESTDIR at the beginning of %install and apache2.spec abusivly
installing files already during the %build phase.

I actually recommend to changethis package to a _multibuild and build each
flavor sepearately (see for example how I converted bogofilter -
https://build.opensuse.org/request/show/846028 )

summary: [rpm4.16] apache2 fails to build


body:
--1604633053.e5CF20.11941
Date: Fri, 6 Nov 2020 03:24:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178496
           Summary: Please upgrade KiCad to 5.1.8.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: aaronw-at-doofus.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

KiCad 5.1.8 has been released, please upgrade from 5.1.7 to 5.1.8.

https://kicad.org/blog/2020/11/KiCad-5.1.8-Release/

summary: Please upgrade KiCad to 5.1.8.


--1604668416.AC487810.14735
Date: Fri, 6 Nov 2020 13:13:36 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178511
           Summary: QT applications don't use the correct mouse cursor
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Xfce
          Assignee: bnc-team-xfce-at-forge.provo.novell.com
          Reporter: maurizio.galli-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When using a qt application, the mouse cursor theme is not applied but falls
back to legacy X cursors instead.

A fix is to create /usr/share/icons/default/index.theme with content
[Icon Theme]
Inherits=Adwaita

This could be added and installed by the xfce branding package.


--1604677329.ef57f500.22007
Date: Fri, 6 Nov 2020 15:42:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178513
           Summary: LLVMConfig.cmake detection is broken with llvm11
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: martin.liska-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

llvm11 got accepted to Factory and I see the following failure for cvise (where
I build require clang10-devel and llvm10-devel):

https://build.opensuse.org/package/live_build_log/openSUSE:Factory/cvise/standard/x86_64

with:

[   23s]


--1604701944.D72d60.20831
Date: Fri, 6 Nov 2020 22:32:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178527
           Summary: [Build 20201105] aa-autodep tries to load inexisting files
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/1461543/modules/aa_a
                    utodep/steps/12
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: openQA
           Blocker: Yes

## Observation

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

/tmp/apparmor.d is being setup with just asbtractions and tunables, then
aa-autodep -d /tmp/apparmor.d nscd being started;

This results in aa-autodep complaingin:

ERROR: includefile /tmp/apparmor.d/apache2.d not found

## Test suite description
Maintainer: wnereiz.

Test AppArmor tool with an existing disk image.

## Reproducible

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

## Expected result

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


--1604728187.0ad4a510.29894
Date: Sat, 7 Nov 2020 05:49:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178530
           Summary: system-user-libvirt-dbus-1.4.0-2.1.x86_64 fails to install on new system
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: nate_opensuse-at-slow.moda
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Something is wrong with the pre-install script in the RPM.  It is failing to
create a user using the /usr/sbin/sysusers2shadow script.

Example:

Checking for file conflicts:
........................................................................................................................................................................................................................................................................................[done]
(1/1) Installing: system-user-libvirt-dbus-1.4.0-2.1.x86_64
........................................................................................................................................................................................................................................................[error]
Installation of system-user-libvirt-dbus-1.4.0-2.1.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: /usr/sbin/sysusers2shadow: line
59: $3: unbound variable
error: %prein(system-user-libvirt-dbus-1.4.0-2.1.x86_64) scriptlet failed, exit
status 1
error: system-user-libvirt-dbus-1.4.0-2.1.x86_64: install failed

The actual script is pretty simple:

❯ rpm -qp --scripts system-user-libvirt-dbus-1.4.0-2.1.x86_64.rpm
preinstall scriptlet (using /bin/sh):
#!/bin/sh
cat <<"EOF" |
u libvirtdbus "Libvirt D-Bus bridge"
g libvirtdbus
EOF
/usr/sbin/sysusers2shadow || [ -f /.buildenv ]

it looks ok, but I couldn't really figure out what sysusers2shadow was actually
expecting in terms of input.

This only fails on a fresh install.  If you had the package installed
previously and libvirtdbus user is already setup then it skips this part.

As a work around I manually added the libvirtdbus user to passwd, shadow, and
groups.  After that zypper was able to install the package.


--1604753706.53bF40.28877
Date: Sat, 7 Nov 2020 12:55:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178533
           Summary: Stunnel cannot create pid file /var/run/stunnel.pid
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: i586
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: toganm-at-dinamizm.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On a fresh clean install of TW stunnel doesn't start. It had two issues first

stunnel.service: Start request repeated too quickly.
Nov 05 11:20:09 dinasor systemd[1]: stunnel.service: Failed with result
'exit-code'.

This I changed by changing the systemd unit to RestartSec=5s

#Restart=always
RestartSec=5s

The second issue unfortunately is still there causing stunnel not to start

2020.11.07 13:39:39 LOG3[main]: Cannot create pid file /var/run/stunnel.pid
2020.11.07 13:39:39 LOG3[main]: create: Permission denied (13)

NAME="openSUSE Tumbleweed"
# VERSION="20201030"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20201030"

If you need any more info let me know


--1604918107.e442C11.17576
Date: Mon, 9 Nov 2020 10:35:07 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178564
           Summary: Bazel 3.4 not built for armv7 due to a missing include path
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: armv7
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Java
          Assignee: java-maintainers-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: ---

Bazel 3.4 is not built for armv7 due to a missing include path.
It complains about 'jni_md.h' being not found:
In file included from
src/main/java/com/google/devtools/build/lib/syntax/cpu_profiler_posix.cc:20:
[  798s]
bazel-out/arm-opt/bin/external/bazel_tools/tools/jdk/include/jni.h:45:10: fatal
error: jni_md.h: No such file or directory
[  798s]    45 | #include "jni_md.h"
[  798s]       |          ^~~~~~~~~~
[  798s] compilation terminated.

But it is available at
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0/include/linux/jni_md.h

x86_64 and aarch64 are not affected.

Not sure how to add /usr/lib/jvm/java-1.8.0-openjdk-1.8.0/include/linux/ to the
list of include path for bazel. Or is it a fix for openjdk?

Latest build log:
https://build.opensuse.org/package/live_build_log/devel:tools:building/bazel3.4/openSUSE_Factory_ARM/armv7l


body:
--1604933878.dBFca0.2730
Date: Mon, 9 Nov 2020 14:57:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178582
           Summary: ibus-rime should require brise
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: liusen-at-disroot.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On Leap 15.2, ibus-rime fails to work, because of missing brise.

Brise provides an input schemas collection which required by ibus-rime.

It should be added to ibus-rime's Require.

summary: ibus-rime should require brise


--1604949976.76f3Eda70.19160
Date: Mon, 9 Nov 2020 19:26:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178601
           Summary: Xvnc service tries to run with-vnc-key.sh from /usr/lib/vnc/ instead of /usr/libexec/vnc/
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: jarek-at-stormdust.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

There is a mismatch between /usr/lib and /usr/libexec in the xorg-x11-Xvnc
package.

Looking at the contents of xorg-x11-Xvnc-1.10.1-6.1, I see that it:
- installs "with-vnc-key.sh" in /usr/libexec/vnc
- in "xvnc@.service" it tries to run /usr/lib/vnc/with-vnc-key.sh

As the result it fails with the following error logged:

xvnc@0-fd06:...36b:46584.service: Failed at step EXEC spawning
/usr/lib/vnc/with-vnc-key.sh: No such file or directory


--1604958398.1aC6bB00.5646
Date: Mon, 9 Nov 2020 21:46:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178604
           Summary: cups cannot print to remote cups: Could not start IPP Backend (/usr/lib/cups/backend/ipp): 13 Permission denied
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Printing
          Assignee: jsmeix-at-suse.com
          Reporter: luizluca@tre-sc.jus.br
        QA Contact: jsmeix-at-suse.com
          Found By: ---
           Blocker: ---

Hello,

For some time with Tumbleweed and now also with Leap 15.2, I cannot print to a
remote cups server directly polled with:

  cupsd-browsed.conf:
  BrowsePoll remote.cups.server.addr
  LocalQueueNamingRemoteCUPS RemoteName

All remote cups printers are network printers. If I add that remote printer as
a local printer (with remote uri), it works as expected.

I can list all remote printers correctly and I can print manually from my
machine using:

  lp -h remote.cups.server.addr -d printername -t testjob a.txt

While this fails:

  lp -d printername -t testjob a.txt

with:

  Could not start IPP Backend (/usr/lib/cups/backend/ipp): 13 Permission denied

I used strace to follow the calls from cups until ipp and saw this:

[pid 29201] execve("/usr/lib/cups/daemon/cups-exec",
["/usr/lib/cups/daemon/cups-exec", "-g", "7", "-n", "0", "-u", "4", "none",
"/usr/lib/cups/filter/texttopdf", ..., "/var/spool/cups/d00109-001"])
[pid 29201] execve("/usr/lib/cups/filter/texttopdf", [...,
"/var/spool/cups/d00109-001"])
[pid 29202] execve("/usr/lib/cups/daemon/cups-exec",
["/usr/lib/cups/daemon/cups-exec", "-g", "7", "-n", "0", "-u", "4", "none",
"/usr/lib/cups/backend/implicitclass", "implicitclass://printername/", ...])
[pid 29202] execve("/usr/lib/cups/backend/implicitclass",
["implicitclass://printername/", ...])
[pid 29203] execve("/usr/lib/cups/filter/gziptoany",
["ipp://remote.cups.server.addr:631/printers/printername", ...,
"/var/spool/cups/tmp/072125faaaeab"])
[pid 29204] execve("/usr/lib/cups/backend/ipp",
["ipp://remote.cups.server.addr:631/printers/printername",
"/var/spool/cups/tmp/072125fab6733"])

So cups switch to user 4(lp) group 7(lp), calls implicitclass, which calls
gziptoany and ipp. However, ipp cannot be used by lp:

-rwxr-xr-x 1 root root 23096 ago 25 16:42 /usr/lib/cups/backend/implicitclass
-rwx----


body:
--1605001690.2BFA00.17309
Date: Tue, 10 Nov 2020 09:48:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178614
           Summary: Incorrect line info for try/catch
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: tdevries-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On Leap 15.2 we have gcc 7.5.0, which has debug info PR97774 - "Incorrect line
info for try/catch" ( https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97774 ).

Can we backport the fix to 7.5.0?

FWIW, The patch applies cleanly to gcc-7-branch.

summary: Incorrect line info for try/catch


--1605005325.ebd8ba0.21382
Date: Tue, 10 Nov 2020 10:48:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178617
           Summary: Seccheck is broken due to wrong exec location
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: toganm-at-dinamizm.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The current shippped seccheck is broken as with the move to /usr/libexec
seccheck
is not able to work. hence all the service files are also broken

For the patches to correct this issue see the pull request in github

https://github.com/openSUSE/seccheck/pull/1/commits/ba7b4d6678d60d6c8cbd8ae02382706bc677ca7b

Thanks

Togan


--1605017066.D1B0b10.29131
Date: Tue, 10 Nov 2020 14:04:26 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1178624
           Summary: On AArch64 memcpy expansion cannot handle length > 32-bit signed int max
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: aarch64
                OS: Linux
            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
          Found By: ---
           Blocker: ---

On AArch64 memcpy expansion cannot handle length > 32-bit signed int max.
It is being fixed in gcc 11 and backports are working their way into gcc 8, 9
and 10.
But we would need to backport to gcc7 in Leap/SLE, as gcc7 is unsupported
upstream, anymore.

Upstream bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97535

Upstream fix:
https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=0f801e0b6cc9f67c9a8983127e23161f6025c5b6


--===============4969366891015347703==
Content-Type: multipart/alternative; boundary="1606673320.3aA7a70.11506";
 charset="UTF-8"

--1606673320.3aA7a70.11506
Date: Sun, 29 Nov 2020 18:08:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179382
           Summary: mozilla-nss 3.58-1.1 breaks SSL connections in pidgin
    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: FSchreiner-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After updating mozilla-nss to 3.58-1.1 at 2020-11-25, I could not connect to
xmpp/irc servers via SSL/TLS encrypted connections with the following error in
the debug logs:

nss: Handshake failed  (-12251)

According to

https://bugzilla.mozilla.org/show_bug.cgi?id=1672855
https://www.mail-archive.com/debian-bugs-dist-at-lists.debian.org/msg1770018.html
https://bugs.archlinux.org/task/68357

it seems to be a upstream problem with mozilla-nss 3.58

After updating the sources to nss-3.59 and rebuilding/installing the package,
the problem was gone.


--===============0161025244922153493==
Content-Type: multipart/alternative; boundary="1606815532.CdFd80.32356";
 charset="UTF-8"

--1606815532.CdFd80.32356
Date: Tue, 1 Dec 2020 09:38:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179447
           Summary: VUL-0: CVE-2020-28926: minidlna: before versions 1.3.0 allows remote code execution
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
               URL: https://smash.suse.de/issue/272482/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: ro-at-suse.de
          Reporter: rfrohl-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2020-28926

ReadyMedia (aka MiniDLNA) before versions 1.3.0 allows remote code execution.
Sending a malicious UPnP HTTP request to the miniDLNA service using HTTP
chunked
encoding can lead to a signedness bug resulting in a buffer overflow in calls
to
memcpy/memmove.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-28926
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28926
https://sourceforge.net/projects/minidlna/
https://www.rootshellsecurity.net/remote-heap-corruption-bug-discovery-minidlna/


body:
--===============5827938461027325449==
Content-Type: multipart/alternative; boundary="1606815806.ee7ec28F0.32696";
 charset="UTF-8"

--1606815806.ee7ec28F0.32696
Date: Tue, 1 Dec 2020 09:43:26 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179449
           Summary: VUL-1: CVE-2020-11867: audacity: saves temporary files to /var/tmp/audacity-$USER by default, which permissions are set to 755.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
               URL: https://smash.suse.de/issue/272474/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: mseben-at-gmail.com
          Reporter: rfrohl-at-suse.com
        QA Contact: security-team-at-suse.de
                CC: davejplater-at-gmail.com
          Found By: Security Response Team
           Blocker: ---

CVE-2020-11867

Audacity through 2.3.3 saves temporary files to /var/tmp/audacity-$USER by
default. After Audacity creates the temporary directory, it sets its
permissions
to 755. Any user on the system can read and play the temporary audio .au files
located there.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11867
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11867
https://github.com/audacity/audacity/releases
https://salvatoresecurity.com/the-many-perils-of-tmp/

pkgs: lilv lv2 serd sord sratom suil


body:
--===============6526497768260357637==
Content-Type: multipart/alternative; boundary="1606816184.AD5d0.23634";
 charset="UTF-8"

--1606816184.AD5d0.23634
Date: Tue, 1 Dec 2020 09:49:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179450
           Summary: rpm %post failures with PAC/BTI enabled
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          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
          Found By: ---
           Blocker: ---

Created attachment 844010
  --> http://bugzilla.opensuse.org/attachment.cgi?id=844010&action=edit
salt-journal.log

Recently, Pointer Authentication and Branch Target Identification (PAC/BTI)
have been enabled in Factory:ARM.
Now, in openQA when qemu is run with PAC/BTI enabled, we have %post failures in
zypper.

Some occurrences:
* https://openqa.opensuse.org/tests/1489881/file/kiwi_templates-journal.log
* https://openqa.opensuse.org/tests/1489881/file/salt-journal.log

The failure is always in scriptlet %post which calls ldconfig, such as:
  Nov 30 23:01:06.242415 ip-10-0-2-15 [RPM][4546]: scriptlet
%post(libbrotlienc1-1.0.9-1.2.aarch64) failure: 2

summary: rpm %post failures with PAC/BTI enabled


--===============3416941120656258564==
Content-Type: multipart/alternative; boundary="1606828086.A3afA10.7623";
 charset="UTF-8"

--1606828086.A3afA10.7623
Date: Tue, 1 Dec 2020 13:08:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179461
           Summary: mutt no longer finds/displays plaintext in mbox format
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: openSUSE Leap 15.1
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: danielm-at-ecoscentric.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

CVE update somehow breaks mail display and search. The number of matched items
is way less than previous version, and when I open any of the found emails only
the header is shown and message body is empty. The mailbox is stored locally in
mbox format.

to reproduce, after starting mutt:

c =clients/CONFIDENTIAL
l
~b CONFIDENTIAL_STRING

mutt-1.10.1-lp151.2.6.1 shows "Msgs:17/212" matched, 2.3.1 shows "46/212". On
the 2.6.1 system the body of the messages isn't shown, but I can show the
header (h) and see on both systems and see the headers as far as (on the last
matched message [29] for both):

"Content-Type: text/plain; charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 MIME-Version: 1.0
 Status: RO
 X-Status: A
 Content-Length: 5456
 Lines: 128

"

Two systems side by side are running Leap 15.1, all updates applied to about
0845am GMT today. One has mutt, mutt-doc & mutt-lang packages forced back to
2.3.1. Mailboxes are the same and were rsync'd about 0835, as were .muttrc
config files. Forcibly reverting back to lp151.2.3.1 packages resolved the
issue as a quick workaround.

Other searches, such as by Subject also yield the same result on 2.6.1.


--===============0887234265723655425==
Content-Type: multipart/alternative; boundary="1606915078.DdEF0.19594";
 charset="UTF-8"

--1606915078.DdEF0.19594
Date: Wed, 2 Dec 2020 13:17:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179528
           Summary: VUL-0: CVE-2020-27818: pngcheck: global buffer overflow was discovered in check_chunk_name function via crafted pngfile
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
               URL: https://smash.suse.de/issue/272507/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: atoptsoglou-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2020-27818

A global buffer overflow was discovered in check_chunk_name function in
pngcheck-2.4.0 via a crafted png file.

Reference:

https://bugzilla.redhat.com/show_bug.cgi?id=1897485

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


body:
--===============1474897218154182071==
Content-Type: multipart/alternative; boundary="1607014104.DA6b2e0.32544";
 charset="UTF-8"

--1607014104.DA6b2e0.32544
Date: Thu, 3 Dec 2020 16:48:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179574
           Summary: move /var/spool/mail/ to separate package
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: lnussel-at-suse.com
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1165830
          Found By: ---
           Blocker: ---

/var/spool/mail/ is like /tmp 1777 so yet another location where users can
write any file. It's only used by MUAs that are not installed by default
anymore nowadays, so should be moved to separate package and required by MUAs.
Also, the default of the  CREATE_MAIL_SPOOL variable should be set to "no".

pkgs: exim rpmlint sendmail


body:
--===============0217031131874319454==
Content-Type: multipart/alternative; boundary="1607024427.88B0F0.13353";
 charset="UTF-8"

--1607024427.88B0F0.13353
Date: Thu, 3 Dec 2020 19:40:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179576
           Summary: VUL-0: chromium: Update to 87.0.4280.88
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: gmbr3-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
                CC: atoptsoglou-at-suse.com, meissner-at-suse.com
        Depends on: 1178923
          Found By: ---
           Blocker: ---

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

tracker for chromium 87.0.4280.88

summary: VUL-0: chromium: Update to 87.0.4280.88


body:
--===============7503633286922771757==
Content-Type: multipart/alternative; boundary="1607076250.aC181.22221";
 charset="UTF-8"

--1607076250.aC181.22221
Date: Fri, 4 Dec 2020 10:04:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179592
           Summary: tigervnc-x11vnc requires python2
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: gfx-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: gfx-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The package tigervnc produces a subpackage called tigervnc-x11vnc, which has an
explicit Requires: python (aka python2)

Can this package be converted to python3? python 2 is EOL in we should try to
eliminate it.

As it is now, the dep is correct, as /usr/bin/x11vnc contains:
#!/usr/bin/env python
(which by the way triggers a rpmlint warning - usr/bin/env is not suitable for
packages)

Converting that script to py3 appears (on first sight_ rather straight forward,
there seem only like 2 print statements that need to be put in parenthesis

summary: tigervnc-x11vnc requires python2


body:
--===============0033406446833063537==
Content-Type: multipart/alternative; boundary="1607088180.fBE7adC30.8383";
 charset="UTF-8"

--1607088180.fBE7adC30.8383
Date: Fri, 4 Dec 2020 13:23:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179607
           Summary: xdm does not install
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: screening-team-bugs-at-suse.de
          Reporter: Sauerlandlinux-at-gmx.de
        QA Contact: screening-team-bugs-at-suse.de
          Found By: ---
           Blocker: ---

package xdm from Repo X11:Xorg does not install in Leap 15.2 because of:

Problem: nothing provides /usr/bin/pidof needed by
xdm-1.1.12-lp152.319.1.x86_64

I think this is the Problem:
Requires:       %{_bindir}/pidof

In Leap/Tumbleweed you have :
Requires:       /sbin/pidof

Another directory.

See:
https://forums.opensuse.org/showthread.php/547744-Cannot-update-xdm-and-Mesa-3D-from-Experimental-repo-quot-nothing-provides-usr-bin-pidof-quot

summary: xdm does not install


body:
--===============5424703839063691793==
Content-Type: multipart/alternative; boundary="1607093068.3D4D46FB0.9615";
 charset="UTF-8"

--1607093068.3D4D46FB0.9615
Date: Fri, 4 Dec 2020 14:44:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179613
           Summary: Remove KDE4 and related qt4 libraries
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: lubos.kocman-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

This is a tracker for removal of KDE4 and related qt4 libraries that are no
longer needed. Both were already unsupported in 15.2, and we'd like to remove
them as we're now facing a lot of build issues in openSUSE Backports 15.3

pkgs: breeze fcitx fcitx-qt5 ffado gcin hydrogen lightdm nulloy qwt qwt6 qwtplot3d release-notes-openSUSE scim wt yate

summary: Remove KDE4 and related qt4 libraries


body:
--===============5469857238601166964==
Content-Type: multipart/alternative; boundary="1607101764.f58105E0.19765";
 charset="UTF-8"

--1607101764.f58105E0.19765
Date: Fri, 4 Dec 2020 17:09:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179619
           Summary: Helm v3 version is  outdated
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dmueller-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

SUSE Private Registry Powered By Harbor v2.1 needs a helm client that is 3.3 or
newer.

since it is backward compatible, we should just update to something that
upstreams considers maintained.

summary: Helm v3 version is  outdated


--===============2855186227055742729==
Content-Type: multipart/alternative; boundary="1607260206.3a4b10.11116";
 charset="UTF-8"

--1607260206.3a4b10.11116
Date: Sun, 6 Dec 2020 13:10:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179635
           Summary: tlp does not restore disk APM settings after resume
    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: biblbroks-at-hotmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Using tlp-1.3.1-2.1.noarch and the following settings in /etc/tlp.conf

[...]
DISK_DEVICES="sda sdb"
DISK_APM_LEVEL_ON_AC="254 254"
DISK_APM_LEVEL_ON_BAT="254 254"
[...]

disk APM level is correctly set on boot, but reverts to 128 (disk default)
after sleep/resume cycle. This used to work, but broke a few months ago with
package updates.

Root cause of the issue is that systemd sleep hook for tlp is installed in the
wrong place, under

/usr/lib/systemd/system/system-sleep/

whereas systemd-path claims the correct path is

/usr/lib/systemd/system-sleep/

so the hook never gets triggered.

If I manually copy /usr/lib/systemd/system/system-sleep/tlp to
/usr/lib/systemd/system-sleep/, the problem goes away and APM gets correctly
restored after resume.


body:
--===============6098607929233303760==
Content-Type: multipart/alternative; boundary="1607372955.D85EdA00.13373";
 charset="UTF-8"

--1607372955.D85EdA00.13373
Date: Mon, 7 Dec 2020 20:29:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179734
           Summary: Emulators/wine: Bug /usr/lib*/libwine.so are missing in devel package wine-6.0-rc1
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: meissner-at-suse.com
          Reporter: munix9-at-googlemail.com
        QA Contact: screening-team-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The devel lib links
/usr/lib/libwine.so -> libwine.so.1.0
/usr/lib64/libwine.so -> libwine.so.1.0
are missing in the devel packages of wine-6.0-rc1
(Factory/Tumbleweed 32/64).

This leads to errors in the detection of the devel package e.g. with cmake
"find_library".
See for example https://build.opensuse.org/package/show/multimedia:apps/lmms

If I manually set the missing links in a local build, the detection works
again.

pkgs: carla lmms


body:
--===============9002203010528960682==
Content-Type: multipart/alternative; boundary="1607416918.71fe0a3.17432";
 charset="UTF-8"

--1607416918.71fe0a3.17432
Date: Tue, 8 Dec 2020 08:41:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179751
           Summary: gmp 6.2.1 fails in test in OBS
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          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,
                    rguenther-at-suse.com
          Found By: ---
           Blocker: ---

Since the update from 6.2.0 to 6.2.1, gmp fails in 't-constants' test for
aarch64. The tests/test-suite.log file is not very verbose:

[  141s] ========================================
[  141s]    GNU MP 6.2.1: tests/test-suite.log
[  141s] ========================================
[  141s]
[  141s] # TOTAL: 8
[  141s] # PASS:  7
[  141s] # SKIP:  0
[  141s] # XFAIL: 0
[  141s] # FAIL:  1
[  141s] # XPASS: 0
[  141s] # ERROR: 0
[  141s]
[  141s] .. contents:: :depth: 2
[  141s]
[  141s] FAIL: t-constants
[  141s] =================
[  141s]
[  141s] FAIL t-constants (exit status: 134)

summary: gmp 6.2.1 fails in test in OBS


--===============7177531831481688774==
Content-Type: multipart/alternative; boundary="1607423560.AA76B3CC0.1123";
 charset="UTF-8"

--1607423560.AA76B3CC0.1123
Date: Tue, 8 Dec 2020 10:32:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179756
           Summary: python3-base: Inconsistent file versions for ensurepip / setuptools / pip
    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: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: frank.kuehndel@embedded-brains.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

In package python3-base-3.6.12-lp152.4.9.1.x86_64.rpm:

The file /usr/lib64/python3.6/ensurepip/__init__.py contains these version
numbers:

    _SETUPTOOLS_VERSION = "40.6.2"

    _PIP_VERSION = "18.1"

Yet, the directory /usr/lib64/python3.6/ensurepip/_bundled/ contains files with
different version numbers:

    pip-20.2.3-py2.py3-none-any.whl
    setuptools-44.1.1-py2.py3-none-any.whl

How to reproduce:

$ python3.6 -m ensurepip --default-pip
Traceback (most recent call last):
  File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/lib64/python3.6/ensurepip/__main__.py", line 5, in <module>
    sys.exit(ensurepip._main())
  File "/usr/lib64/python3.6/ensurepip/__init__.py", line 204, in _main
    default_pip=args.default_pip,
  File "/usr/lib64/python3.6/ensurepip/__init__.py", line 99, in _bootstrap
    "_bundled/{}".format(wheel_name),
  File "/usr/lib64/python3.6/pkgutil.py", line 634, in get_data
    return loader.get_data(resource_name)
  File "<frozen importlib._bootstrap_external>", line 832, in get_data
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/lib64/python3.6/ensurepip/_bundled/setuptools-40.6.2-py2.py3-none-any.whl'

(In my case, the above is needed to use a Python Virtual Environment. The above
simplified command results from a call `python3 -m venv env`.)

The following is a workaround which reduces the error to a warning. It works in
my case but it may not work for you because it finds other working versions of
pip and setuptools on my machine:

root # cd /usr/lib64/python3.6/ensurepip/_bundled
root # ln -s pip-20.2.3-py2.py3-none-any.whl pip-18.1-py2.py3-none-any.whl
root # ln -s setuptools-44.1.1-py2.py3-none-any.whl
setuptools-40.6.2-py2.py3-none-any.whl


--===============1215322250325712455==
Content-Type: multipart/alternative; boundary="1607432767.C4f72000.10746";
 charset="UTF-8"

--1607432767.C4f72000.10746
Date: Tue, 8 Dec 2020 13:06:07 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179763
           Summary: Patch openSUSE-2020-2161 - EDAC amd64: Error: F1 not found with AMD A10-5750M APU
    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: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: bugrprt21882-at-online.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since the Kernel patch openSUSE-2020-2161 the systemd Journal has the following
errors:
kernel: EDAC amd64: F15h detected (node 0).
kernel: EDAC amd64: Error: F1 not found: device 0x1601 (broken BIOS?)

The machine's CPU is:
 # inxi --admin -C
CPU:       Topology: Quad Core model: AMD A10-5750M APU with Radeon HD Graphics
bits: 64 type: MCP arch: Piledriver
           family: 15 (21) model-id: 13 (19) stepping: 1 microcode: 6001119 L1
cache: 192 KiB L2 cache: 2048 KiB
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 19962
           Speed: 1251 MHz min/max: 1400/2500 MHz boost: enabled Core speeds
(MHz): 1: 1258 2: 1211 3: 1231 4: 1350
           Vulnerabilities: Type: itlb_multihit status: Not affected
           Type: l1tf status: Not affected
           Type: mds status: Not affected
           Type: meltdown status: Not affected
           Type: spec_store_bypass mitigation: Speculative Store Bypass
disabled via prctl and seccomp
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user
pointer sanitization
           Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled,
RSB filling
           Type: srbds status: Not affected
           Type: tsx_async_abort status: Not affected
 #


--===============5137385693634260558==
Content-Type: multipart/alternative; boundary="1607433754.17881dfF0.13035";
 charset="UTF-8"

--1607433754.17881dfF0.13035
Date: Tue, 8 Dec 2020 13:22:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179765
           Summary: [rpm4.16]ostgresql fails with fixed brp-check-suse
    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: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

openSUSE:Factory:Staging:A is preparing the upgrade of RPM to version 4.16. AS
part of this upgrade, there is also a fixed brp-check-suse in the staging (it
had problem detecting some invalid symlinks, mainly when they pointed to the
same directory)

Currently the various postgresql versions fail in Staging:A, with errors like:

[  580s] ERROR: link target doesn't exist (neither in build root nor in
installed system):
[  580s]   /usr/lib64/libecpg.so -> libecpg.so.6
[  580s] Add the package providing the target to BuildRequires and Requires
[  580s] ERROR: link target doesn't exist (neither in build root nor in
installed system):
[  580s]   /usr/lib64/libecpg_compat.so -> libecpg_compat.so.3
[  580s] Add the package providing the target to BuildRequires and Requires
[  580s] ERROR: link target doesn't exist (neither in build root nor in
installed system):
[  580s]   /usr/lib64/libpgtypes.so -> libpgtypes.so.3
[  580s] Add the package providing the target to BuildRequires and Requires
[  580s] ERROR: link target doesn't exist (neither in build root nor in
installed system):
[  580s]   /usr/lib64/libpq.so -> libpq.so.5

(from postgresql12)


body:
--===============2930841772028778406==
Content-Type: multipart/alternative; boundary="1607460121.80600.7435";
 charset="UTF-8"

--1607460121.80600.7435
Date: Tue, 8 Dec 2020 20:42:01 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179790
           Summary: fwupd package has not been validated
    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: fkrueger-at-mailbox.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

With the recent update to fwupd 1.5.2 (TW20201205) and using, e.g., 'fwupdmgr
update' I am getting "WARNING: This package has not been validated, it may not
work properly."

> tree /boot/efi/
/boot/efi/
????????? EFI
    ????????? boot
    ??????? ????????? bootx64.efi
    ??????? ????????? fallback.efi
    ??????? ????????? MokManager.efi
    ????????? opensuse
        ????????? boot.csv
        ????????? fw
        ??????? ????????? fwupd-3b8c8162-188c-46a4-aec9-be43f1d65697.cap
        ??????? ????????? fwupd-9bfd8b34-080b-40a1-47b3-ca1efa289e6d.cap
        ????????? fwupdx64.efi
        ????????? grub.cfg
        ????????? grub.efi
        ????????? grubx64.efi
        ????????? MokManager.efi
        ????????? shim.efi

summary: fwupd package has not been validated


--===============1125886533951962695==
Content-Type: multipart/alternative; boundary="1607506941.5465e64c1.13499";
 charset="UTF-8"

--1607506941.5465e64c1.13499
Date: Wed, 9 Dec 2020 09:42:21 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179817
           Summary: taglib corrupts ogg files under some circumstances
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: alarrosa-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

According to https://github.com/taglib/taglib/issues/864, under some
circumstances, saving certain ogg files with taglib 1.11.1 can result in
corrupted files.

The fix is provided by upstream at
https://github.com/taglib/taglib/commit/9336c82da3a04552168f208cd7a5fa4646701ea4


--===============0814587920097281796==
Content-Type: multipart/alternative; boundary="1607622181.Df22E0.10504";
 charset="UTF-8"

--1607622181.Df22E0.10504
Date: Thu, 10 Dec 2020 17:43:01 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179914
           Summary: VUL-0: CVE-2020-29367: blosc: heap-based buffer overflow when there is a lack of space to write compressed data
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
               URL: https://smash.suse.de/issue/272427/
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: wolfgang.frisch-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2020-29367

blosc2.c in Blosc C-Blosc2 through 2.0.0.beta.5 has a heap-based buffer
overflow when there is a lack of space to write compressed data.

References:
https://github.com/Blosc/c-blosc2/commit/c4c6470e88210afc95262c8b9fcc27e30ca043ee
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26442
https://bugzilla.redhat.com/show_bug.cgi?id=1903232
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29367
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29367


body:
--===============3721063484365206581==
Content-Type: multipart/alternative; boundary="1607682740.f7FCfFa80.32198";
 charset="UTF-8"

--1607682740.f7FCfFa80.32198
Date: Fri, 11 Dec 2020 10:32:20 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179945
           Summary: [icu68] postgresql fails to build
    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: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

in Staging:I, icu is being updated to ICU 68.1 (from 67.x)

PostgreSQL is amongst the few packages failing to build.

From pgsql12 build log:

[  100s] collationcmds.c:466:51: error: 'TRUE' undeclared (first use in this
function); did you mean 'IS_TRUE'?

The point being that icu stopped defining the macros for TRUE/FALSE in order to
avoid issues with C++20

other consumers, like chromium, did:

s/TRUE/true/ and s/FALSE/false/

summary: [icu68] postgresql fails to build


body:
--===============4357486983066432164==
Content-Type: multipart/alternative; boundary="1607754951.27D37ec0.7923";
 charset="UTF-8"

--1607754951.27D37ec0.7923
Date: Sat, 12 Dec 2020 06:35:51 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1179972
           Summary: [trackerbug] lxd 4.9 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.9. The full upstream changelog is available from:
  https://discuss.linuxcontainers.org/t/lxd-4-9-has-been-released/9673

  + Mediated GPU devices for Virtual Machines
  + IOMMU groups for PCI devices
  + QEMU version in server environment information
  * Improved lifecycle events
  + "user." keys allowed on all objects
  + usb_address and pci_address properties in USB/network resources
  + ipv4.dhcp and ipv6.dhcp on OVN networks
  + ovn.ingress_mode on physical networks
  + ipv4.routes.anycast and ipv6.routes.anycast on physical networks
  + limits.instances project option
  + zstd compression for images and backups

summary: [trackerbug] lxd 4.9 update


--===============0326760235629209293==
Content-Type: multipart/alternative; boundary="1608027699.eCad41fe0.30502";
 charset="UTF-8"

--1608027699.eCad41fe0.30502
Date: Tue, 15 Dec 2020 10:21:39 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1180049
           Summary: libvirtd deletes snapshot from qcow2, but keeps them internally
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: felix.niederwanger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

virsh snapshot-delete and the same in virt-manager delete a snapshot from the
qcow2 image, but the snapshot still shows up in virsh and virt-manager.
After deleting, the snapshot does not show up in `qemu-img snapshot -l`, which
is expected.
When trying to delete the snapshot again in virsh or virt-manager, libvirtd
complains in journal that the snapshot does not exists.

## Observation

    # List snapshots. There should the 3 "updated-*" snapshots, as old ones are
deleted automatically
    phoenix@racetrack-7290:~> virsh snapshot-list tumbleweed
     Name                 Creation Time               State
    -----------------------------------------------------------
     updated-2020-11-20   2020-11-20 09:15:09 +0100   shutoff
     updated-2020-11-23   2020-11-23 16:21:29 +0100   shutoff
     updated-2020-11-30   2020-11-30 13:29:55 +0100   shutoff
     updated-2020-12-07   2020-12-07 14:00:15 +0100   shutoff
     updated-2020-12-08   2020-12-07 15:31:57 +0100   shutoff
     updated-2020-12-09   2020-12-09 12:27:17 +0100   shutoff
     updated-2020-12-10   2020-12-10 12:25:40 +0100   shutoff
     updated-2020-12-11   2020-12-11 12:28:50 +0100   shutoff
     updated-2020-12-14   2020-12-14 12:29:13 +0100   shutoff

    # Delete oldest snapshot
    phoenix@racetrack-7290:~> virsh snapshot-delete --domain tumbleweed
updated-2020-11-20
    Domain snapshot updated-2020-11-20 deleted

    # Snapshot still shows up in virsh
    phoenix@racetrack-7290:~> virsh snapshot-list tumbleweed
     Name                 Creation Time               State
    -----------------------------------------------------------
     updated-2020-11-20   2020-11-20 09:15:09 +0100   shutoff
     updated-2020-11-23   2020-11-23 16:21:29 +0100   shutoff
     updated-2020-11-30   2020-11-30 13:29:55 +0100   shutoff
     updated-2020-12-07   2020-12-07 14:00:15 +0100   shutoff
     updated-2020-12-08   2020-12-07 15:31:57 +0100   shutoff
     updated-2020-12-09   2020-12-09 12:27:17 +0100   shutoff
     updated-2020-12-10   2020-12-10 12:25:40 +0100   shutoff
     updated-2020-12-11   2020-12-11 12:28:50 +0100   shutoff
     updated-2020-12-14   2020-12-14 12:29:13 +0100   shutoff

    # But old snapshots do not show up in qemu-img. This is the expected state
    phoenix@racetrack-7290:~> sudo qemu-img snapshot -l
/srv/libvirt/virtualmachines/tumbleweed.qcow2
    Snapshot list:
    ID        TAG               VM SIZE                DATE     VM CLOCK
ICOUNT
    32        updated-2020-12-10     0 B 2020-12-10 12:25:40 00:00:00.000
    33        updated-2020-12-11     0 B 2020-12-11 12:28:50 00:00:00.000
    34        updated-2020-12-14     0 B 2020-12-14 12:29:13 00:00:00.000
   0

## Journal log

When trying to delete those "nonexisting" snapshots, I find the following lines
in the journal

    Dec 15 10:51:57 racetrack-7290 libvirtd[7015]: internal error: Child
process (/usr/bin/qemu-img snapshot -d updated-2020-11-20
/srv/libvirt/virtualmachines/tumbleweed.qcow2) unexpected exit status 1:
qemu-img: Could not delete snapshot 'updated-2020-11-20': snapshot not found
    Dec 15 10:51:57 racetrack-7290 libvirtd[7015]: skipping snapshot action on
vda
    Dec 15 10:52:04 racetrack-7290 libvirtd[7015]: internal error: Child
process (/usr/bin/qemu-img snapshot -d updated-2020-11-20
/srv/libvirt/virtualmachines/tumbleweed.qcow2) unexpected exit status 1:
qemu-img: Could not delete snapshot 'updated-2020-11-20': snapshot not found
    Dec 15 10:52:04 racetrack-7290 libvirtd[7015]: skipping snapshot action on
vda


--===============6887477834752328393==
Content-Type: multipart/alternative; boundary="1608039883.AfAdcAe1.12951";
 charset="UTF-8"

--1608039883.AfAdcAe1.12951
Date: Tue, 15 Dec 2020 13:44:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1180058
           Summary: Please don't create /boot/do_purge_kernels on initial install
    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: dcermak-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Currently the %post scriptlet of the kernel creates /boot/do_purge_kernels to
trigger zypper's kernel purging.

Could this be modified so that it only creates this file on upgrades and *not*
on fresh installations? Currently this will cause zypper to try to purge old
kernels on fresh installations. While that is short, it can cause noticeable
delays until zypper can be used again, especially in resource constrained
systems.

Could the creation of this file be adjusted so that it is only created on
upgrades and not on new installations?


--===============4815123867446431174==
Content-Type: multipart/alternative; boundary="1608060892.2BD435E2.4976";
 charset="UTF-8"

--1608060892.2BD435E2.4976
Date: Tue, 15 Dec 2020 19:34:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1180068
           Summary: games:tools/mumble: Old category on .desktop file, shown as lost+found
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: x86-64
                OS: openSUSE Leap 15.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: i-at-marguerite.su
          Reporter: nahkaz-at-gmail.com
        QA Contact: screening-team-bugs-at-suse.de
                CC: matthias-at-mailaender.name, opensuse-at-dstoecker.de
          Found By: ---
           Blocker: ---

Created attachment 844491
  --> http://bugzilla.opensuse.org/attachment.cgi?id=844491&action=edit
Screenshot of problem

This applies to same package on other repositories also.

Currenty mumble package is creating .desktop file with X-SuSE-Core-Game
-category.
Using this category results in lost+found -category being shown in KDE Plasma
5.18.6.


--===============5613792603681456583==
Content-Type: multipart/alternative; boundary="1608130309.DBfbccc60.30584";
 charset="UTF-8"

--1608130309.DBfbccc60.30584
Date: Wed, 16 Dec 2020 14:51:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1180117
           Summary: Regression in uvcvideo: Webcam (1f3a:100e) stopped working as of 5.3.18-lp152.50-default
    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: doerges@pre-sense.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The webcam in question is
  Renkforce RF AC4K 300 Action Cam 4K

https://www.conrad.de/de/p/action-cam-renkforce-rf-ac-4k-webcam-4k-wlan-wasserfest-staubgeschuetzt-1577043.html

It identifies as:
  [34367.545510] uvcvideo: Found UVC 1.00 device Android (1f3a:100e)

Everything was working fine with openSUSE Leap 15.2 and Kernel
5.3.18-lp152.47-default (RPM kernel-default-5.3.18-lp152.47.2.x86_64) and
earlier versions.

After updating to kernel-default-5.3.18-lp152.50.1.x86_64 the webcam stopped
working. This is also true for later Kernel versions.

With Kernel 5.3.18-lp152.47-default I can capture the videostream, e.g. via:

-


--===============8164287088773571971==
Content-Type: multipart/alternative; boundary="1608148077.257B1.17098";
 charset="UTF-8"

--1608148077.257B1.17098
Date: Wed, 16 Dec 2020 19:47:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1180132
           Summary: roundcubemail should recommend httpd, not require lighttpd
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Apache
          Assignee: bnc-team-apache-at-forge.provo.novell.com
          Reporter: jimc-at-jfcarter.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Versions:
roundcubemail-1.4.9-2.1.noarch (updated 2020-12-15, yesterday)
lighttpd-1.4.55-4.1.x86_64
apache2-2.4.46-9.1.x86_64

roundcubemail newly requires lighttpd by name.  On my webserver,
Apache is the HTTP infrastructure that sends out RoundCube.
I hit some snarl-ups with both lighttpd and apache2 installed
together (my hacks, not your fault).  I wanted to just de-install
lighttpd, but roundcubemail has a hard requirement for it.  So
instead I'm fixing the snarl-up and letting lighttpd sit unused,
until it's no longer required.

Lighttpd is a nice package and I used it on a project where a
lightweight webserver was needed, but in this case roundcubemail
needs to defer to the sysop's choice of webserver.  Could you
please refer to "httpd" as the facility needed by roundcubemail
rather than picking a specific one of the various available
webservers?  Both apache2 and lighttpd provide this generic
facility, and I assume that nginx does also.

Also, it's a little bizarre and inefficient to install
roundcubemail on a different host from the webserver and then
make it available to the webserver on a SAN-like kludge like NFS,
but that kind of baroque storage architecture seems to be the name
of the game in the enterprise today.  I'd also like you to change
"require" to "recommend" to accommodate situations like that.

I'm surprised not to see any hits in a bug search for
"roundcubemail lighttpd" that I could add a "mee too" comment to.


--===============6849129781337445792==
Content-Type: multipart/alternative; boundary="1608195721.8CFa5.25046";
 charset="UTF-8"

--1608195721.8CFa5.25046
Date: Thu, 17 Dec 2020 09:02:01 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1180150
           Summary: PackageKit (zypp backend) does not always list all available updates
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: x86-64
                OS: openSUSE Leap 15.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: gnome-bugs-at-suse.de
          Reporter: jdelvare-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I have a wine-staging update available for my system (from OBS project
Emulators:Wine). "zypper up" does list it always. The PackageKit front-end,
however, sometimes lists it, and sometimes not. Today it doesn't, but yesterday
it did (but I did not install it, in order to keep the bug reproducer).

I suspect this has something to do with the version string. The update has a ~
in its version string. Installed package:

wine-staging-5.22-lp151.1222.1

Available update:

wine-staging-6.0~rc1-lp151.1230.3

Let me know if I can provide additional data to help investigate the issue.


body:
--===============0550131564900012992==
Content-Type: multipart/alternative; boundary="1608309225.47Cc6E75.27606";
 charset="UTF-8"

--1608309225.47Cc6E75.27606
Date: Fri, 18 Dec 2020 16:33:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1180228
           Summary: Geeqie fails to start
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: gnome-bugs-at-suse.de
          Reporter: dutchkind-at-txoriaskea.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since a few days Geeqie fails to open. I think it was after some update to the
latest version. When I try to start from terminal I get the following output:

Xlib: sequence lost (0x100ac > 0xae) in reply type 0x0!

(geeqie:12159): Gdk-ERROR **: 17:22:56.198: The program 'geeqie' received an X
Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 186 error_code 2 request_code 152 (GLX) minor_code 24)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Would be very nice to get this fixed

summary: Geeqie fails to start


--===============5327706135758823305==
Content-Type: multipart/alternative; boundary="1608320403.EBF208cA5.24158";
 charset="UTF-8"

--1608320403.EBF208cA5.24158
Date: Fri, 18 Dec 2020 19:40:03 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1180230
           Summary: Connecting to network via NetworkManager in Gnome Shell requires root password
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: gnome-bugs-at-suse.de
          Reporter: dlrobin874-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Setting up a new wireless connection (i.e., for my home wifi after a fresh
install) through the menu in Gnome Shell asks for a root password to edit
connections for all users.

Don't know if the correct solution is getting Gnome Shell to just modify the
connection for the local user similarly to how Plasma works, or if it's to
modify PackageKit upstream, but connecting to a network shouldn't require root
password.


--===============7678601067888598449==
Content-Type: multipart/alternative; boundary="1608380186.ED4BBB360.4879";
 charset="UTF-8"

--1608380186.ED4BBB360.4879
Date: Sat, 19 Dec 2020 12:16:26 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1180234
           Summary: no DNS in resolv.conf with NetworkManager
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: seife-at-novell.slipkontur.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Summary: NETCONFIG_DNS_POLICY="auto" does not work with NetworkManager, it
needs to be changed manually to NETCONFIG_DNS_POLICY="STATIC * NetworkManager"

After installing a JeOS-X11 system on an ARM board (which has NetworkManager
installed and enabled by default) and using nmtui-connect to connect to a
wireless network, I found an empty resolv.conf with no name servers from DHCP.

bananapim2zero:~ # netconfig update -f -v
<13>Dec 19 12:14:46 netconfig: Executing 'update -f -v' for pid 8743
debug: lockfile created (/var/run/netconfig.pid) for PID 9612
debug: lockfile created
debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime
debug: dns-resolver module called
debug: Resolved dns-policy 'auto' for service 'network' to 'STATIC *'
debug: Keep Static
debug: Other: *
debug: write_resolv_conf: '   ' '   '
debug: dns settings written to /var/run/netconfig/resolv.conf
debug: /etc/resolv.conf is already a link to /var/run/netconfig/resolv.conf
debug: dns-bind Module called
debug: dns-dnsmasq Module called
debug: nis Module called
debug: Resolved nis-policy 'auto' for service 'network' to 'STATIC *'
debug: Keep Static
debug: format_static[-1] called
debug: Other: *
debug: write_yp_conf
debug: nis settings written to /var/run/netconfig/yp.conf
debug: /etc/yp.conf is already a link to /var/run/netconfig/yp.conf
debug: nis domainname '' is up to date
debug: ntp-runtime Module called
debug: Resolved ntp-policy 'auto' for service 'network' to 'STATIC *'
debug: Keep Static
debug: Other: *
debug: write_chrony_servers:
debug: ntp servers written to /var/run/netconfig/chrony.servers
bananapim2zero:~ # ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 26 Dez 17 14:29 /etc/resolv.conf ->
/run/netconfig/resolv.conf
bananapim2zero:~ # tail -5 /etc/resolv.conf
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
bananapim2zero:~ #

Setting the NETCONFIG_DNS_POLICY="STATIC * NetworkManager" makes it work.


body:
--===============4746088336353662520==
Content-Type: multipart/alternative; boundary="1608533696.Ba3fdbC0.19681";
 charset="UTF-8"

--1608533696.Ba3fdbC0.19681
Date: Mon, 21 Dec 2020 06:54:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1180243
           Summary: [trackerbug] Docker 19.03.14 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 Docker 19.03.13-ce. See upstream changelog in the packaged
  /usr/share/doc/packages/docker/CHANGELOG.md. CVE-2020-15257

https://github.com/docker/docker-ce/releases/tag/v19.03.14

pkgs: containerd docker

summary: [trackerbug] Docker 19.03.14 update


--===============3986657945605907541==
Content-Type: multipart/alternative; boundary="1608538488.8f8AEcae0.10225";
 charset="UTF-8"

--1608538488.8f8AEcae0.10225
Date: Mon, 21 Dec 2020 08:14:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1180251
           Summary: VUL-0: CVE-2020-35573: postsrsd: DoS via a long timestamp tag in an SRS address
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
               URL: https://smash.suse.de/issue/273807/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: abergmann-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2020-35573

srs2.c in PostSRSd before 1.10 allows remote attackers to cause a denial of
service (CPU consumption) via a long timestamp tag in an SRS address.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35573
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35573
https://github.com/roehling/postsrsd/commit/4733fb11f6bec6524bb8518c5e1a699288c26bac
https://lists.debian.org/debian-lts-announce/2020/12/msg00031.html