--1622008733.1BFB0.6618
Date: Wed, 26 May 2021 05:58:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

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

Fixed in chromium 91.0.4472.77

* CVE-2021-30521: Heap buffer overflow in Autofill
* CVE-2021-30522: Use after free in WebAudio
* CVE-2021-30523: Use after free in WebRTC
* CVE-2021-30524: Use after free in TabStrip
* CVE-2021-30525: Use after free in TabGroups
* CVE-2021-30526: Out of bounds write in TabStrip
* CVE-2021-30527: Use after free in WebUI
* CVE-2021-30528: Use after free in WebAuthentication
* CVE-2021-30529: Use after free in Bookmarks
* CVE-2021-30530: Out of bounds memory access in WebAudio
* CVE-2021-30531: Insufficient policy enforcement in Content Security Policy
* CVE-2021-30532: Insufficient policy enforcement in Content Security Policy
* CVE-2021-30533: Insufficient policy enforcement in PopupBlocker
* CVE-2021-30534: Insufficient policy enforcement in iFrameSandbox
* CVE-2021-30535: Double free in ICU
* CVE-2021-21212: Insufficient data validation in networking
* CVE-2021-30536: Out of bounds read in V8
* CVE-2021-30537: Insufficient policy enforcement in cookies
* CVE-2021-30538: Insufficient policy enforcement in content security policy
* CVE-2021-30539: Insufficient policy enforcement in content security policy
* CVE-2021-30540: Incorrect security UI in payments
* Various fixes from internal audits, fuzzing and other initiatives

References:
https://chromereleases.googleblog.com/2021/05/stable-channel-update-for-desktop_25.html


--1622130714.f2F01E21.10723
Date: Thu, 27 May 2021 15:51:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186561
           Summary: pipewire user services presets are not set on a new installation
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: alarrosa-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

In a new TW (or SLE15-SP3/Leap 15.3) installation, pipewire is installed before
systemd which makes the %systemd_user_* macros not do anything and so the user
services (mainly pipewire.socket and pipewire-media-session.service but also ,
pipewire-pulse.socket if the user installs the pipewire-pulseaudio package
during installation) are not enabled as they should.

After the installation is done executing the following command gives:

> grep -e "install|pipewire|0.3.27" -e "install|systemd|246" /var/log/zypp/history
2021-05-24
09:42:57|install|pipewire|0.3.27-2.1|x86_64||openSUSE-20210522-0|b811f374ec767b8f176864ae37e24be5218e6230741e3707bda934c01486e6c1|
2021-05-24
09:43:42|install|systemd|246.13-1.2|x86_64||openSUSE-20210522-0|06a9eb6641d7a28d2a1d2b100828800db9d11bc1bf196c5a04cca1ced1680339|

Note that that version of the pipewire package uses %systemd_ordering, but it
seems zypper is not honoring it.


--1622161755.FC31Ad8b0.456
Date: Fri, 28 May 2021 00:29:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186572
           Summary: PipeWire on Plasma can't control the volume
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: andresbs2000-at-protonmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 849767
  --> http://bugzilla.opensuse.org/attachment.cgi?id=849767&action=edit
System logs and information

I can't raise the volume for my wired headphones in Plasma (X11 session).
Currently I am using pipewire-pulseaudio and the following services are
enabled:
* pipewire-media-session
* pipewire
* pipewire-pulse

Checking the user journal entries for all of those services revealed nothing
useful, just some Zoom errors, as usual.

My laptop has jack combo (a.k.a. Analog Stereo Duplex).

So here is what I picked up so far:
- If I unplug my headphone, the loudspeaker and the built-in subwoofer work
fine, I can control the volume with no issues.
- Connecting the headphone does not affect anything as PipeWire doesn't switch
to the headphone by default.
- If I keep the audio output as "Speaker" and switch from "Internal Microphone"
to "Headset Microphone", the sound starts coming out from my headset and I can
control the volume. Odd.
- After trying the previous combination, if I change the output from internal
to headset, the sound gets low again and the volume control doesn't work.
Unplugging and plugging back in the headset, and trying Speaker + headset mic
again makes the sound come out of the headset with volume control working.
- Plasma is set to use the jack in "Analog Stereo Duplex" mode, which is the
default one.
- This issue started happening in the 20210524 Tumbleweed snapshot.
- Neither alsa or pulseaudio are installed and both are locked from zypper.
- My bluetooth headphones don't suffer this issue neither, it happens
specifically with the wired headphones.

I can't tell if the issue is something in Plasma/Qt or it has to do with the
new PipeWire update (version 0.3.28-1.1).
I attached the output of save_y2logs to ease the analysis, if that helps.


--1622185353.2bEc5Ea1.25898
Date: Fri, 28 May 2021 07:02:33 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186575
           Summary: VUL-1: CVE-2021-33038:  python-HyperKitty: information disclosure when importing a private mailing list
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
               URL: https://smash.suse.de/issue/300830/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: pgajdos-at-suse.com
          Reporter: rfrohl-at-suse.com
        QA Contact: security-team-at-suse.de
                CC: mmachova-at-suse.com
          Found By: Security Response Team
           Blocker: ---

CVE-2021-33038

An issue was discovered in management/commands/hyperkitty_import.py in
HyperKitty through 1.3.4. When importing a private mailing list's archives,
these archives are publicly visible for the duration of the import. For
example,
sensitive information might be available on the web for an hour during a large
migration from Mailman 2 to Mailman 3.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-33038
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33038
https://gitlab.com/mailman/hyperkitty/-/issues/380
https://gitlab.com/mailman/hyperkitty/-/commit/9025324597d60b2dff740e49b70b15589d6804fa


--1622203596.3ca60.15691
Date: Fri, 28 May 2021 12:06:36 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186592
           Summary: sendmail: inconsistencies in entries in /etc/permissions.d/sendmail*
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: werner-at-suse.com
          Reporter: matthias.gerstner-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: ---
           Blocker: ---

Integrity checks for our permissions profiles show a number of problems with
entries in the files /etc/permissions.d/sendmail* installed by the sendmail
package. The inconsistencies are as follows:

1) with the move to /usr/libexec, the following paths are no longer correct:

- /usr/lib/sendmail.d/bin
        ??? was last seen in sle15-x86_64 in package sendmail.rpm
- /usr/lib/sendmail.d/bin/smrsh
        ??? was last seen in sle15-x86_64 in package sendmail.rpm
- /usr/lib/sendmail.d/bin/mail.local
        ??? was last seen in sle15-x86_64 in package sendmail.rpm

2) /var/run should be /run, since /var/run is only a symlink any more

- /var/run/sendmail
        ??? was last seen in sle11-x86_64 in package sendmail.rpm

3) /var/spool/mail is conflicting with systemd-tmpfiles

the filesystem package installs a systemd-tmpfiles configuration that
conflicts with the permissions entry:

E: [permissions-tmpfiles-conflict] Conflict between permissions and
systemd-tmpfiles for /var/spool/mail

systemd-tmpfiles entries:

    filesystem-15.5-40.2.i586.rpm: /usr/lib/tmpfiles.d/fs-var.conf:
    d /var/spool/mail 1777 root root - -

permission profile entries:

    permissions.sendmail:7:          /var/spool/mail root:root 0o1777
    permissions.sendmail.paranoid:7: /var/spool/mail root:root 0o1755

It would be best to drop /var/spool/mail completely from permissions, since
the systemd-tmpfiles entry usually wins anyway (at least after the first
reboot after installing the sendmail package).


--1622203718.E0aff0.14061
Date: Fri, 28 May 2021 12:08:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186593
           Summary: Leap 15.3 is missing Backports update and SLE Update repo definitions
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Patterns
          Assignee: lubos.kocman-at-suse.com
          Reporter: lubos.kocman-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

lkocman@localhost:/etc/openvpn> sudo zypper lr -d
#  | Alias                     | Name
| Enabled | GPG Check | Refresh | Priority | Type   | URI
                                                           | Service
---+---------------------------+-----------------------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------------------+--------
 1 | Kernel_SLE15-SP3          | Kernel builds for branch SLE15-SP3 (standard)
| Yes     | (r ) Yes  | No      |    1     | rpm-md |
https://download.opensuse.org/repositories/Kernel:/SLE15-SP3/standard/
     |
 2 | SuSE                      | VideoLAN repo (SLEap_15.3)
| Yes     | (r ) Yes  | No      |   99     | rpm-md |
http://download.videolan.org/SuSE/SLEap_15.3/
     |
 3 | YaST_Head                 | The Latest YaST Packages (openSUSE_Leap_15.3)
| Yes     | (r ) Yes  | No      |   99     | rpm-md |
https://download.opensuse.org/repositories/YaST:/Head/openSUSE_Leap_15.3/
     |
 4 | microsoft-edge-dev        | microsoft-edge-dev
| Yes     | (r ) Yes  | Yes     |   99     | rpm-md |
https://packages.microsoft.com/yumrepos/edge/
     |
 5 | obs-studio                | obs-studio
| No      | --


--1622204314.34e561b1.16271
Date: Fri, 28 May 2021 12:18:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186595
           Summary: systemd: /usr/lib/systemd/systemd-sysv-install calls chkconfig
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: systemd-maintainers-at-suse.de
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: dimstar-at-opensuse.org
          Found By: ---
           Blocker: ---

/usr/lib/systemd/systemd-sysv-install calls chkconfig which was dropped with
insserv-compat. I guess it should just say that enabling sysv script is no
longer supported.

Found via bug 1186359


--1622214082.bDF661A0.5105
Date: Fri, 28 May 2021 15:01:22 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186619
           Summary: VUL-0: CVE-2021-32635: singularity: Action commands against library URIs ignore configured remote endpoint
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
               URL: https://smash.suse.de/issue/300901/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Containers
          Assignee: eich-at-suse.com
          Reporter: gianluca.gabrielli-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

In singularity 3.7.2 and 3.7.3, action commands against library:// URIs
erroneously always used the default remote endpoint (cloud.sylabs.io). An
attacker may be able to push a malicious container to the default remote
endpoint with a URI that is identical to the URI used by a victim with a
non-default remote endpoint, thus executing the malicious container.

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


--1622320987.2EB7BBC0.26861
Date: Sat, 29 May 2021 20:43:07 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186637
           Summary: error: lua script failed: [string "%pretrans(filesystem-15.5-40.2.riscv64)"]:37: exit
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Basesystem
          Assignee: lnussel-at-suse.com
          Reporter: schwab-at-suse.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

# rpm -Uhv
/var/cache/zypp/packages/openSUSE-Ports-Tumbleweed-repo-oss/riscv64/filesystem-15.5-40.2.riscv64.rpm
Verifying...                          ################################# [100%]
Make a copy of `/bin'.
Merge the copy with `/usr/bin'.
Clean up duplicates in `/usr/bin'.
Make a copy of `/sbin'.
Merge the copy with `/usr/sbin'.
Clean up duplicates in `/usr/sbin'.
Make a copy of `/lib'.
Merge the copy with `/usr/lib'.
Clean up duplicates in `/usr/lib'.
Make a copy of `/lib64'.
Merge the copy with `/usr/lib64'.
Clean up duplicates in `/usr/lib64'.
Switch to new `/usr/bin'.
renameat2: Invalid argument
Something failed, cleaning up
error: lua script failed: [string
"%pretrans(filesystem-15.5-40.2.riscv64)"]:37: exit
Preparing...                          ################################# [100%]
        file /bin from install of filesystem-15.5-40.2.riscv64 conflicts with
file from package filesystem-15.5-40.1.riscv64
        file /lib from install of filesystem-15.5-40.2.riscv64 conflicts with
file from package filesystem-15.5-40.1.riscv64
        file /lib64 from install of filesystem-15.5-40.2.riscv64 conflicts with
file from package filesystem-15.5-40.1.riscv64
        file /sbin from install of filesystem-15.5-40.2.riscv64 conflicts with
file from package filesystem-15.5-40.1.riscv64


--1622414129.d0C8ceEA1.4772
Date: Sun, 30 May 2021 22:35:29 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186643
           Summary: X-application crashes after installing new libx11-6 version ( 1.6.5-lp152.5.15.1 )
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: openSUSE Leap 15.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: gfx-bugs-at-suse.de
          Reporter: hw01-at-heisch.inka.de
        QA Contact: gfx-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The program 'fdesign' ( from the package xforms-tool-kit ) is quite old and
bases directly on the xlib.
( This package has been widely known as 'xforms' before this name has been
kidnapped by W3. )

After having installed 1.6.5-lp152.5.15.1, this application crashes directly
after the start on one of the first button touches.

I returned to the former version 1.6.5-lp152.5.12.1 and it works again.

Because this program bases directly on the xlib, I assume that other x-based
applications are also in danger.

(Also, here are still a lot of programs in science and industry, which base on
the xforms-library, xforms-tool-kit )

Segmentation fault has been reported. In the next days I will try to find a
more precise description.

Cheers
Werner


body:
--1622438067.fcFbf75C0.11668
Date: Mon, 31 May 2021 05:14:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186647
           Summary: [trackerbug] lxd 4.14 update
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          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.14. The full upstream changelog is available from:
  https://discuss.linuxcontainers.org/t/lxd-4-14-has-been-released/11008

  + ACL support on managed bridges
  + Cluster member certificates
  + Cluster member description
  + Cluster token based join
  + Server warnings
  + Backup and snapshot project restrictions
  + User keys in device configuration
  + More auto-generated REST-API documentation

- Remove upstreamed patches:
  - boo1181549-0001-vm-qemu-configure-spice-using-spice-parameter.patch

summary: [trackerbug] lxd 4.14 update


--1622472025.ECAe6E0D0.16983
Date: Mon, 31 May 2021 14:40:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186669
           Summary: postfix.service has "Requires=var-run.mount"
    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: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

It's been spotted in bsc#1181970 that postfix.service has
"Requires=var-run.mount".

This is probably incorrect as adding a dependency on /var/run, which is
essentially the same as specifying a dep on /run these days, seems unneeded as
/run is guaranteed to be mounted before any services are started.

So would it possible to drop this requirement ?

Thanks.


body:
--1622476354.d2840.22589
Date: Mon, 31 May 2021 15:52:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186672
           Summary: 1wire modules not built
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: opensuse@1.opensuse.bgcomp.co.uk
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Seems none of the 1wire modules have been built for x86_64, although they do
appear to be available for aarch64.

I seriously need them.

summary: 1wire modules not built


--1622583295.8dFD80.2379
Date: Tue, 1 Jun 2021 21:34:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186710
           Summary: wrong/dead symlinks with kernel-default-devel-5.12.4-2.1.x86_64 (after usrmerge?)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: munix9-at-googlemail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

$ rpm -q kernel-default-devel
kernel-default-devel-5.12.4-2.1.x86_64

$ ls -l /lib
lrwxrwxrwx 1 root root 7 May 25 07:58 /lib -> usr/lib/

$ ls -l /lib/modules/5.12.4-2-default
total 0
lrwxrwxrwx 1 root root 53 Jun  1 21:16 build ->
../../../usr/src/linux-5.12.4-2-obj/x86_64/default
lrwxrwxrwx 1 root root 34 Jun  1 21:16 source ->
../../../usr/src/linux-5.12.4-2

but that is one level too few, this are dead symlinks.
it should be

lrwxrwxrwx 1 root root 53 Jun  1 21:16 build ->
../../../../usr/src/linux-5.12.4-2-obj/x86_64/default
lrwxrwxrwx 1 root root 34 Jun  1 21:16 source ->
../../../../usr/src/linux-5.12.4-2

I manually changed this for testing in a chroot environment to compile a kernel
module.

Without changing the original symlinks I get errors when compiling the module.
After creating the correct symlinks, the module compiled correctly.


body:
--1622618137.676D4bB0.8357
Date: Wed, 2 Jun 2021 07:15:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186721
           Summary: Mesa-dri-nouveau automatically installed on update but claims to be dangerous
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Mesa-dri-nouveau gets automatically installed during an update with "zypper
dup", but has a "license" which warns for it:

"WARNING: Nouveau DRI/3D driver selected.

This driver is considered experimental and is known to have issues with
applications that use certain 3D acceleration features of modern
NVIDIA hardware."

It even has:

"Use of this driver is especially not recommended for use with the KDE Desktop
Environment or Qt-based Applications."

So why get this driver automatically installed, if it is dangerous and even not
recommended for my setups (qt and KDE)?

And why do we break automatic updates by requiring a manual license acceptance
during an upgrade?

Either the warning is wrong, then we should remove it. Or the warning is
correct, in this case we should never automatically select and install this
package at upgrade.

Installing a package automatically with a license is already a bad idea,
installing a package automatically, where the license warns for the usage of
this package, is a really bad idea.

pkgs: Mesa openSUSE-EULAs


--1622651269.40848c1.29036
Date: Wed, 2 Jun 2021 16:27:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186775
           Summary: Cannot install git package(s) with "transactional-update pkg install" command
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: MicroOS
          Assignee: kubic-bugs-at-opensuse.org
          Reporter: ldevulder-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 849900
  --> http://bugzilla.opensuse.org/attachment.cgi?id=849900&action=edit
log file

I tried to install git package(s) with the command "transactional-update pkg
install git" but zypper failed with an error code of 107 because a package
tries to write in a file on /etc, which is of course not allowed in MicroOS.

I was able to workaround this by installing the package in a
"transactional-update shell" env (but of course I had the same issue in
zypper).

I attached the transactional-update log file that contains the error.


--1622675173.C07d20.484
Date: Wed, 2 Jun 2021 23:06:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186781
           Summary: filesystem: usrmerge: cp: cannot create hard link: Invalid cross-device link
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: jonaski-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Last night I did a zypper dup update on my main machine, it completely broke
the system.
I had /, /usr, /opt and /var on separate ext4 partitions, and I think this
might be the reason.
It looks like the update was trying to create hard links from files in /usr to
/bin, which won't work since those are different partitions.
After this, the system was completely unusable, and I could not access any
coreutils such as ls and cp, not even the shell.
I ended up booting up a parted magic USB stick, chroot'ed the system, there I
tried to do the same update, and got the following error, which I remember as
identical to the one I got before:

Checking for file conflicts:
................................................................................................................................................................................[done]
(   1/6461) Installing: filesystem-15.5-40.2.x86_64
........................................................................................................................................................[error]
Installation of filesystem-15.5-40.2.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: Make a copy of `/bin'.
cp: cannot create hard link '/usr/bin.usrmerge/ksh93' to '/bin/ksh93': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/rpcinfo' to '/bin/rpcinfo':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/ps' to '/bin/ps': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/fsync' to '/bin/fsync': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/usleep' to '/bin/usleep':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/login' to '/bin/login': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/pgrep' to '/bin/pgrep': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/pkill' to '/bin/pkill': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/[' to '/bin/[': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/b2sum' to '/bin/b2sum': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/base32' to '/bin/base32':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/base64' to '/bin/base64':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/basenc' to '/bin/basenc':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/chcon' to '/bin/chcon': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/chroot' to '/bin/chroot':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/cksum' to '/bin/cksum': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/comm' to '/bin/comm': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/csplit' to '/bin/csplit':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/cut' to '/bin/cut': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/dir' to '/bin/dir': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/dircolors' to '/bin/dircolors':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/dirname' to '/bin/dirname':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/du' to '/bin/du': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/env' to '/bin/env': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/expand' to '/bin/expand':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/expr' to '/bin/expr': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/factor' to '/bin/factor':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/fmt' to '/bin/fmt': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/fold' to '/bin/fold': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/groups' to '/bin/groups':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/head' to '/bin/head': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/hostid' to '/bin/hostid':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/id' to '/bin/id': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/install' to '/bin/install':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/join' to '/bin/join': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/link' to '/bin/link': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/logname' to '/bin/logname':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/mkfifo' to '/bin/mkfifo':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/nice' to '/bin/nice': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/nl' to '/bin/nl': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/nohup' to '/bin/nohup': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/nproc' to '/bin/nproc': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/numfmt' to '/bin/numfmt':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/od' to '/bin/od': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/paste' to '/bin/paste': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/pathchk' to '/bin/pathchk':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/pinky' to '/bin/pinky': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/pr' to '/bin/pr': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/printenv' to '/bin/printenv':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/printf' to '/bin/printf':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/ptx' to '/bin/ptx': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/realpath' to '/bin/realpath':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/runcon' to '/bin/runcon':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/seq' to '/bin/seq': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/sha1sum' to '/bin/sha1sum':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/sha224sum' to '/bin/sha224sum':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/sha256sum' to '/bin/sha256sum':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/sha384sum' to '/bin/sha384sum':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/sha512sum' to '/bin/sha512sum':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/shred' to '/bin/shred': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/shuf' to '/bin/shuf': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/split' to '/bin/split': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/stdbuf' to '/bin/stdbuf':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/sum' to '/bin/sum': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/tac' to '/bin/tac': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/tail' to '/bin/tail': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/tee' to '/bin/tee': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/test' to '/bin/test': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/timeout' to '/bin/timeout':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/tr' to '/bin/tr': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/truncate' to '/bin/truncate':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/tsort' to '/bin/tsort': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/tty' to '/bin/tty': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/unexpand' to '/bin/unexpand':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/uniq' to '/bin/uniq': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/unlink' to '/bin/unlink':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/uptime' to '/bin/uptime':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/users' to '/bin/users': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/vdir' to '/bin/vdir': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/wc' to '/bin/wc': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/who' to '/bin/who': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/whoami' to '/bin/whoami':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/yes' to '/bin/yes': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/arch' to '/bin/arch': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/basename' to '/bin/basename':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/cat' to '/bin/cat': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/chgrp' to '/bin/chgrp': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/chmod' to '/bin/chmod': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/chown' to '/bin/chown': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/cp' to '/bin/cp': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/date' to '/bin/date': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/dd' to '/bin/dd': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/df' to '/bin/df': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/echo' to '/bin/echo': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/false' to '/bin/false': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/ln' to '/bin/ln': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/ls' to '/bin/ls': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/md5sum' to '/bin/md5sum':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/mkdir' to '/bin/mkdir': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/mknod' to '/bin/mknod': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/mktemp' to '/bin/mktemp':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/mv' to '/bin/mv': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/pwd' to '/bin/pwd': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/readlink' to '/bin/readlink':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/rm' to '/bin/rm': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/rmdir' to '/bin/rmdir': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/sleep' to '/bin/sleep': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/sort' to '/bin/sort': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/stat' to '/bin/stat': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/stty' to '/bin/stty': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/sync' to '/bin/sync': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/touch' to '/bin/touch': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/true' to '/bin/true': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/uname' to '/bin/uname': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/bash' to '/bin/bash': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/bashbug' to '/bin/bashbug':
Invalid cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/rbash' to '/bin/rbash': Invalid
cross-device link
cp: cannot create hard link '/usr/bin.usrmerge/sh' to '/bin/sh': Invalid
cross-device link
Something failed, cleaning up
error: lua script failed: [string "%pretrans(filesystem-15.5-40.2.x86_64)"]:37:
exit
error: filesystem-15.5-40.2.x86_64: install skipped
error: filesystem-15.5-40.1.x86_64: erase skipped

Abort, retry, ignore? [a/r/i] (a):

From what I remember I managed to complete the update there by downloading and
copying coreutils and extracting it to /bin, I also created some symbolic links
from /usr/bin/sh to /bin/sh, etc.
However I managed to delete all the symbolic links in /sbin, although I could
boot the system I was missing stuff in /sbin, and I decided to just do a
reinstall instead.

I have a couple of other machines with the same partition setup, and I need to
know if I will run into the same issue there, and what I can do to fix it
without repartitioning the disk. And if this will also be an issue when
upgrading from LP 15.2 to 15.3.


body:
--1622698753.e24Ec20.29995
Date: Thu, 3 Jun 2021 05:39:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186786
           Summary: lxd exec don't work
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: x86-64
                OS: openSUSE Leap 15.2
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: werwolf131313-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

after upgrade leap from 15.2 to 15.3 lxc exec broken

> lxc launch images:ANYTHING test
> lxc exec test /bin/WHATEWER
Error: Failed to retrieve PID of executing child process

> rpm -qa | grep lxd
lxd-bash-completion-4.13-bp153.2.10.noarch
lxd-4.13-bp153.2.10.x86_64

P.S.: sorry for my english

summary: lxd exec don't work


--1622722669.13dE6A4E2.663
Date: Thu, 3 Jun 2021 12:17:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186798
           Summary: [Build 20210601] openQA test fails in yast2_rmt
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
               URL: https://openqa.opensuse.org/tests/1765786/modules/yast
                    2_rmt/steps/19
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: jsrain-at-suse.com
                CC: afaerber-at-suse.com, dmueller-at-suse.com
          Found By: openQA
           Blocker: Yes

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

## Observation

openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-yast2_ncurses@aarch64
fails in
[yast2_rmt](https://openqa.opensuse.org/tests/1765786/modules/yast2_rmt/steps/19)

YaST RMT fails to load properly on aarch64. See log in attachment.

## Test suite description
Maintainer: qsf-y Test for yast2 UI, ncurses only. Running on created gnome
images which provides both text console for ncurses UI tests as well as the
gnome environment for the GUI tests.
riafarov set TIMEOUT_SCALE to improve stability of the test.

## Reproducible

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

## Expected result

Last good: (unknown) (or more recent)

## Further details

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


body:
--1622735036.E8ba0.4197
Date: Thu, 3 Jun 2021 15:43:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186820
           Summary: units_cur throws ImportError
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: pat-cinlug-at-indy.rr.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After performing the openSUSE Leap 15.2 to 15.3 upgrade last night, I tried to
refresh the units exchange rate data by running unit_cur:

> sudo /usr/bin/units_cur
[sudo] password for root:
Traceback (most recent call last):
  File "/usr/bin/units_cur", line 22, in <module>
    import requests
ImportError: No module named requests
> units -V
GNU Units version 2.16
with readline, with utf8, locale en_US
Units data file is '/usr/share/units/definitions.units'

I don't recall if I ever ran this command on openSUSE, so this may have been
broken in the previous version.

Expected result is no output, and change in the exchange rate used by units.
Here is a sample from a non SUSE system:

$ units -V
GNU Units version 2.21
with readline, with utf8, locale en_US
. . .
$ units UKP
        Definition: GBP = ukpound = 1.41674869333 USD = 1.4167487 US$
$ sudo /usr/local/bin/units_cur
[sudo] password for security:
$ units UKP
        Definition: GBP = ukpound = 1.41552495088 USD = 1.415525 US$

summary: units_cur throws ImportError


--1622792173.EbEb480.17838
Date: Fri, 4 Jun 2021 07:36:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186841
           Summary: devel:languages:python/python-maxminddb: Bug
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: sebix+novell.com-at-sebix.at
          Reporter: lundstrom.jerry-at-gmail.com
        QA Contact: screening-team-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Macro seems broken for SLE/leap: "unresolvable: nothing provides python2-devel
>= 3.6, (got version 2.7.18 provided by python-devel)"


--1622793491.Ab510a20.20607
Date: Fri, 4 Jun 2021 07:58:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186843
           Summary: [cups-driverd] Bad driver information file
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Printing
          Assignee: jsmeix-at-suse.com
          Reporter: Ulrich.Windl-at-rz.uni-regensburg.de
        QA Contact: jsmeix-at-suse.com
          Found By: ---
           Blocker: ---

While hunting for some CUPS error, I found these in /var/log/cups/error_log:
E [04/Jun/2021:09:43:21 +0200] [cups-driverd] Bad driver information file
\"/usr/share/cups/drv/sample.drv\"!
E [04/Jun/2021:09:43:21 +0200] [cups-driverd] Bad driver information file
\"/usr/share/cups/drv/cupsfilters.drv\"!
E [04/Jun/2021:09:43:21 +0200] [cups-driverd] Bad driver information file
\"/usr/share/cups/drv/generic-brf.drv\"!
E [04/Jun/2021:09:43:21 +0200] [cups-driverd] Bad driver information file
\"/usr/share/cups/drv/generic-ubrl.drv\"!
E [04/Jun/2021:09:43:21 +0200] [cups-driverd] Bad driver information file
\"/usr/share/cups/drv/indexv3.drv\"!
E [04/Jun/2021:09:43:21 +0200] [cups-driverd] Bad driver information file
\"/usr/share/cups/drv/indexv4.drv\"!


--1622797455.747B4aa6.31195
Date: Fri, 4 Jun 2021 09:04:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186848
           Summary: VUL-0: CVE-2020-27208: downgrade the RDP level and access secrets such as private ECC keys from SRAM via the debug interface
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
               URL: https://smash.suse.de/issue/300545/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: marix-at-marix.org
          Reporter: gianluca.gabrielli-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

The flash read-out protection (RDP) level is not enforced during the device
initialization phase of the SoloKeys Solo 4.0.0 & Somu and the Nitrokey FIDO2
token. This allows an adversary to downgrade the RDP level and access secrets
such as private ECC keys from SRAM via the debug interface.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27208
http://www.cvedetails.com/cve/CVE-2020-27208/
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27208
https://github.com/solokeys/solo/commit/a9c02cd354f34b48195a342c7f524abdef5cbcec
https://www.aisec.fraunhofer.de/de/das-institut/wissenschaftliche-exzellenz/security-and-trust-in-open-source-security-tokens.html
https://twitter.com/SoloKeysSec
https://www.aisec.fraunhofer.de/en/FirmwareProtection.html
https://solokeys.com
https://eprint.iacr.org/2021/640


body:
--1622803320.1cDDfCF40.11628
Date: Fri, 4 Jun 2021 10:42:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186855
           Summary: lsb has broken dependencies
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: duge@pre-sense.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Booted: openSUSE-Leap-15.3-KDE-Live-x86_64-Build9.88-Media.iso

# zypper in lsb
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides /usr/bin/pidof needed by
lsb-4.0.fake-lp153.1.1.x86_64
 Solution 1: do not install lsb-4.0.fake-lp153.1.1.x86_64
 Solution 2: break lsb-4.0.fake-lp153.1.1.x86_64 by ignoring some of its
dependencies

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

In openSUSE-15.2 lsb simply didn't depend on /usr/bin/pidof.

summary: lsb has broken dependencies


--1622810738.875A1234.24856
Date: Fri, 4 Jun 2021 12:45:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186865
           Summary: VUL-1: CVE-2021-33815: ffmpeg: dwa_uncompress in libavcodec/exr.c in FFmpeg 4.4 allows an out-of-bounds array access because dc_count is not strictly checked.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
               URL: https://smash.suse.de/issue/301216/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Other
          Assignee: gnome-bugs-at-suse.de
          Reporter: gianluca.gabrielli-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

dwa_uncompress in libavcodec/exr.c in FFmpeg 4.4 allows an out-of-bounds array
access because dc_count is not strictly checked.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-33815
https://github.com/FFmpeg/FFmpeg/commit/26d3c81bc5ef2f8c3f09d45eaeacfb4b1139a777
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33815


--1622813954.BF6E2AC0.31740
Date: Fri, 4 Jun 2021 13:39:14 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186870
           Summary: python-rpm-macros different dependency generated python-six
    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: rpm-at-fthiessen.de
        QA Contact: qa-bugs-at-suse.de
                CC: mcepl-at-suse.com
          Found By: ---
           Blocker: ---

I am not sure if this is an issue with the python-rpm-macros package or
python-six.

If you use the dependency generator and your package uses python-six it will
generate a dependency like this:

> python3.6dist(six) >= 1.10

But this can not be satisfied, as python-six only provides

> python36-six = 1.16.0-103.2


body:
--1622888534.2e580.30764
Date: Sat, 5 Jun 2021 10:22:14 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186894
           Summary: tumbleweed update with usermerged faild
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: holgerbruenjes-at-gmx.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

i started with zypper dup  today 2021-06-05

                                          (4021/4021),  19.3 KiB (    0   B
unpacked)
Retrieving: texlive-scheme-medium-2021.184.svn54074-51.3.noarch.rpm
...........[done]

Checking for file conflicts:
..................................................[done]
(   1/4021) Installing: bash-completion-doc-2.11-2.3.noarch
...................[done]

(  11/4021) Installing: glibc-2.33-7.1.x86_64
.................................[done]
Additional rpm output:
error: failed to exec scriptlet interpreter /sbin/ldconfig: No such file or
directory
warning: %postun(glibc-2.33-6.1.x86_64) scriptlet failed, exit status 127

(  12/4021) Installing: gtk3-data-3.24.29-1.3.noarch
.........................[error]
Installation of gtk3-data-3.24.29-1.3.noarch failed:
Error: Subprocess failed. Error: RPM failed: Can't exec 'rpm' (No such file or
directory).

Abort, retry, ignore? [a/r/i] (a): r
(  12/4021) Installing: gtk3-data-3.24.29-1.3.noarch
.........................[error]
Installation of gtk3-data-3.24.29-1.3.noarch failed:
Error: Subprocess failed. Error: RPM failed: Can't exec 'rpm' (No such file or
directory).

Abort, retry, ignore? [a/r/i] (a): a
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.

after this no executable where found

eisler:~ # ls -l
-bash: /usr/bin/ls: No such file or directory
eisler:~ # mc
-bash: /usr/bin/whoami: No such file or directory
-bash: /usr/bin/mc: No such file or directory
-bash: /usr/bin/rm: No such file or directory
eisler:~ # zypper dup
-bash: /usr/bin/zypper: No such file or directory

eisler:~ # snapper list
-bash: /usr/bin/snapper: No such file or directory

holger

summary: tumbleweed update with usermerged faild


body:
--1622963198.3f7e7C0.31296
Date: Sun, 6 Jun 2021 07:06:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186906
           Summary: [trackerbug] lxd 4.15 update
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          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.15. The full upstream changelog is available from:
  https://discuss.linuxcontainers.org/t/lxd-4-15-has-been-released/11252

  + Network interface hotplug in VMs
  + Configurable shutdown timeout
  + New persistent warnings (time skew, apparmor and virtiofsd)
  + Location field in /dev/lxd API
  + New type and name columns in lxc config trust list
  + Cluster members acting as database stand-by now visible
  + lxc monitor --pretty now supported with lifecycle events
  + New --expire flag for lxc publish
  + Requestor now recorded in lifecyle events
  + Proxy header support on main API endpoint
  + Full swagger coverage of REST API

summary: [trackerbug] lxd 4.15 update


--1623064042.EbdB0.22109
Date: Mon, 7 Jun 2021 11:07:22 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186929
           Summary: ckb-next incorrect dependency on //bin/bash
    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: kerossin-at-pm.me
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

ckb-next has a dependency for //bin/bash which can only be provided by
bash-legacybin.

Installing bash-legacybin after the recent usr directory merge will mess up the
system.

The actual bash package provides only bash, /bin/bash and /usr/bin/bash.

ckb-next should require /bin/bash instead of //bin/bash.

> sudo zypper in ckb-next
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides 'this-is-only-for-build-envs' needed by the to be
installed bash-legacybin-5.1.4-2.3.x86_64
 Solution 1: do not install ckb-next-0.4.4-1.3.x86_64
 Solution 2: break bash-legacybin-5.1.4-2.3.x86_64 by ignoring some of its
dependencies

Choose from above solutions by number or cancel [1/2/c/d/?] (c): d
Problem: nothing provides 'this-is-only-for-build-envs' needed by the to be
installed bash-legacybin-5.1.4-2.3.x86_64
Detailed information:
        the to be installed ckb-next-0.4.4-1.3.x86_64 requires '//bin/bash',
but this requirement cannot be provided
        nothing provides 'this-is-only-for-build-envs' needed by the to be
installed bash-legacybin-5.1.4-2.3.i586
        nothing provides 'this-is-only-for-build-envs' needed by the to be
installed bash-legacybin-5.1.4-2.3.x86_64
 Solution 1: do not install ckb-next-0.4.4-1.3.x86_64
 Solution 2: break bash-legacybin-5.1.4-2.3.x86_64 by ignoring some of its
dependencies

> sudo zypper info --provides bash
Loading repository data...
Reading installed packages...

Information for package bash:
-----------------------------
Repository     : Main Repository (OSS)
Name           : bash
Version        : 5.1.4-2.3
Arch           : x86_64
Vendor         : openSUSE
Installed Size : 1,3 MiB
Installed      : Yes
Status         : up-to-date
Source package : bash-5.1.4-2.3.src
Summary        : The GNU Bourne-Again Shell
Description    :
    Bash is an sh-compatible command interpreter that executes commands
    read from standard input or from a file.  Bash incorporates useful
    features from the Korn and C shells (ksh and csh).  Bash is intended to
    be a conformant implementation of the IEEE Posix Shell and Tools
    specification (IEEE Working Group 1003.2).
Provides       : [7]
    /bin/sh
    /bin/bash
    bash = 5.1.4-2.3
    config(bash) = 5.1.4-2.3
    bash(x86-64) = 5.1.4-2.3
    /usr/bin/bash
    /usr/bin/sh


body:
--1623092952.f1Df00.4932
Date: Mon, 7 Jun 2021 19:09:12 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1186948
           Summary: Chromium fails to restore open tabs
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: aloisio-at-gmx.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since the last (91.0.4472.77-bp153.2.3.1) I think update, chromium always asks
to restore tabs on startup claiming it was improperly closed.

No difference with blank configuration.

summary: Chromium fails to restore open tabs


--1623155352.0Ab730.10374
Date: Tue, 8 Jun 2021 12:29:12 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187044
           Summary: error reading variable: dwarf2_find_location_expression: Corrupted DWARF expression.
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: tdevries-at-suse.com
          Reporter: schwab-at-suse.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

$ cat hello.c
#include <stdio.h>
#include <locale.h>

int
main (void)
{
  setlocale (LC_ALL, "");
  if (fprintf (stderr, "Hello World!\n") == EOF)
    perror ("fprintf");
}
$ gcc -g hello.c -o hello
$ gdb hello
GNU gdb (GDB; openSUSE Tumbleweed) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "riscv64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from hello...
(gdb) start
Temporary breakpoint 1 at 0x106b4: file hello.c, line 7.
Starting program: /daten/src/test/hello

Temporary breakpoint 1, main () at hello.c:7
7         setlocale (LC_ALL, "");
(gdb) s
__GI_setlocale (
    category=<error reading variable: dwarf2_find_location_expression:
Corrupted DWARF expression.>,
    locale=<error reading variable: dwarf2_find_location_expression: Corrupted
DWARF expression.>) at setlocale.c:225
225       if (__builtin_expect (category, 0) < 0
(gdb)


--1623160354.Dfc2F1a0.26299
Date: Tue, 8 Jun 2021 13:52:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187058
           Summary: libindi and ioptron: wrong time set when DST is in use
    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: pstivanin-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When setting the option "Mount update Kstars for both time and location",
Kstars doesn't set the correct time but, instead, it's off by 1 hour.
On the mount side, the HC is setup like the following:
    DST: Y
    UTC offset: +060

The reported time and date on the HC are perfect. Even when the GPS OK'd,
settings are not changed (obviously) and the information presented are fine.
Then I head over to Kstars, start the CEM70 profile in EKOS and the time it's
set 1 hour off (behind current time). Therefore, if on the HC the time is
15:30:00, on Kstars the time is 14:30:00.

See https://github.com/indilib/indi/issues/1448 for more info.

This issue has already been fixed (and tested) with those two simple commits:
https://github.com/indilib/indi/commit/85d200d1a280364afbef813a9f164ed0e4b6dede
https://github.com/indilib/indi/commit/6e73b0fb6459f0762807adb6becb6317ff07c134

I'm already working on adding them to the current 1.9.0 branch.


body:
--1623231983.7a7c41c0.24504
Date: Wed, 9 Jun 2021 09:46:23 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187101
           Summary: samba-ad-dc requires python3x-dnspython
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Samba
          Assignee: samba-maintainers@SuSE.de
          Reporter: conde.philippe-at-skynet.be
        QA Contact: samba-maintainers@SuSE.de
          Found By: ---
           Blocker: ---

I provisioned a samba-ad-dc on a raspberry pi400. Provision was successfully;
After configuration and start of named(DNS) I start samba-ad-dc and receive
this error

May 28 21:48:51 rasp samba[8051]: [2021/05/28 21:48:51.914772,  0]
../../source4/dsdb/dns/dns_update.c:85(dnsupdate_nameupdate_done)
May 28 21:48:51 rasp winbindd[8049]: [2021/05/28 21:48:51.914788,  0]
../../source3/winbindd/winbindd_cache.c:3204(initialize_winbindd_cache)
May 28 21:48:51 rasp winbindd[8049]:   initialize_winbindd_cache: clearing
cache and re-creating with version number 2
May 28 21:48:51 rasp samba[8051]:   dnsupdate_nameupdate_done: Failed DNS
update with exit code 1
May 28 21:48:51 rasp winbindd[8049]: [2021/05/28 21:48:51.975829,  0]
../../lib/util/become_daemon.c:152(daemon_ready)
May 28 21:48:51 rasp winbindd[8049]:   daemon_ready: daemon 'winbindd' finished
starting up and ready to serve connections
May 28 21:48:53 rasp smbd[8019]: [2021/05/28 21:48:53.129313,  0]
../../lib/util/become_daemon.c:152(daemon_ready)
May 28 21:48:53 rasp smbd[8019]:   daemon_ready: daemon 'smbd' finished
starting up and ready to serve connections
May 28 21:48:58 rasp samba[8029]: [2021/05/28 21:48:58.611583,  0]
../../source4/lib/tls/tlscert.c:154(tls_cert_generate)
May 28 21:48:58 rasp samba[8029]:   TLS self-signed keys generated OK

Installing python38-dnspython package solves this problem.

systemctl status samba-ad-dc output is now

Jun 09 11:31:59 rasp winbindd[23521]: [2021/06/09 11:31:59.670189,  0]
../../lib/util/become_daemon.c:152(daemon_ready)
Jun 09 11:31:59 rasp winbindd[23521]:   daemon_ready: daemon 'winbindd'
finished starting up and ready to serve connections
Jun 09 11:31:59 rasp mitkdc[23509]: [2021/06/09 11:31:59.706160,  0]
../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler)
Jun 09 11:31:59 rasp mitkdc[23509]:   /usr/sbin/krb5kdc: Stash file (null) uses
DEPRECATED enctype !
Jun 09 11:31:59 rasp mitkdc[23509]: [2021/06/09 11:31:59.766003,  0]
../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler)
Jun 09 11:31:59 rasp mitkdc[23509]:   /usr/sbin/krb5kdc: Stash file (null) uses
DEPRECATED enctype !
Jun 09 11:31:59 rasp mitkdc[23509]: [2021/06/09 11:31:59.776810,  0]
../../lib/util/util_runcmd.c:352(samba_runcmd_io_handler)
Jun 09 11:31:59 rasp mitkdc[23509]:   /usr/sbin/krb5kdc: krb5kdc: starting...
Jun 09 11:31:59 rasp smbd[23491]: [2021/06/09 11:31:59.913519,  0]
../../lib/util/become_daemon.c:152(daemon_ready)
Jun 09 11:31:59 rasp smbd[23491]:   daemon_ready: daemon 'smbd' finished
starting up and ready to serve connections

The packages python38-dnspython needs to be required by samba-ad-dc

Regards
Philippe

summary: samba-ad-dc requires python3x-dnspython


body:
--1623221854.50e5DE3.29307
Date: Wed, 9 Jun 2021 06:57:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187089
           Summary: gpsd fails on aarch64 with LTO
    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,
                    martin.liska-at-suse.com
          Found By: ---
           Blocker: ---

gpsd fails to link on aarch64 with LTO.
Error log:
[  389s] gcc -o gpsd-3.22/gpsd/gpsd -pthread gpsd-3.22/gpsd/dbusexport.o
gpsd-3.22/gpsd/gpsd.o gpsd-3.22/gpsd/shmexport.o gpsd-3.22/gpsd/timehint.o
gpsd-3.22/gpsd/sd_socket.o -Lgpsd-3.22 gpsd-3.22/libgpsd.a
gpsd-3.22/libgps/libais_json.a -lusb-1.0 -lbluetooth -lm -lrt -ldbus-1
[  422s] /tmp/ccorEIHR.ltrans7.ltrans.o: in function
`ntpshm_context_init.constprop.0':
[  422s]
/home/abuild/rpmbuild/BUILD/gpsd-3.22/python3/gpsd-3.22/gpsd-3.22/gpsd/timehint.c:152:(.text+0x9c34):
relocation truncated to fit: R_AARCH64_ADR_PREL_PG_HI21 against symbol
`context.lto_priv.0' defined in .bss section in /tmp/ccorEIHR.ltrans0.ltrans.o
[  422s] collect2: error: ld returned 1 exit status
[  422s] scons: *** [gpsd-3.22/gpsd/gpsd] Error 1

summary: gpsd fails on aarch64 with LTO


--1623269900.3Ee400.4892
Date: Wed, 9 Jun 2021 20:18:20 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187141
           Summary: VUL-0: chromium: multiple security issues fixed in 91.0.4472.101
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: gmbr3-at-opensuse.org
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

https://chromereleases.googleblog.com/2021/06/stable-channel-update-for-desktop.html

CVE-2021-30544: Use after free in BFCache
CVE-2021-30545: Use after free in Extensions
CVE-2021-30546: Use after free in Autofill
CVE-2021-30547: Out of bounds write in ANGLE
CVE-2021-30548: Use after free in Loader
CVE-2021-30549: Use after free in Spell check
CVE-2021-30550: Use after free in Accessibility
CVE-2021-30551: Type Confusion in V8
CVE-2021-30552: Use after free in Extensions
CVE-2021-30553: Use after free in Network service
Various fixes from internal audits, fuzzing and other initiatives

Google is aware that an exploit for CVE-2021-30551 exists in the wild.


--1623306310.014A38e0.12482
Date: Thu, 10 Jun 2021 06:25:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187154
           Summary: systemd stopped marking framebuffer as "graphic capable"
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: x86-64
                OS: SUSE Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: uli-at-woodwax.co.nz
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After upgrade from Leap15.2 (systemd v234) to Leap 15.3 (systemd v246) the
computer does not boot into GUI. This is discussed in the forum
(https://forums.opensuse.org/showthread.php/555021-upgrade-from-15-2-no-GUI?p=3038959#post3038959)
See commit 6260d28b8a002a401eab7511f96fd62f471dccdb


body:
--1623326098.eCd5d0.3583
Date: Thu, 10 Jun 2021 11:54:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187171
           Summary: Missing fix in mvpp2 NIC driver
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: aarch64
                OS: SLES 15
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: mw-at-semihalf.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hi,

The latest SLES-15SP2 and OpenSUSE LEAP 15.3 use the v5.3.x Linux kernel, which
has a known issue for the ACPI support in the mvpp2 NIC driver (relevant for
Marvell Armada 7k8k and Octeon TX2 CN913x SoC families).

The regression fix was already backported to v5.4 LTS Linux branch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c?h=v5.4.124&id=76812738841c2daa89420a2f61ab100f0dea8eb9

I'd appreciate applying the patch in your next releases.

Best regards,
Marcin

summary: Missing fix in mvpp2 NIC driver


body:
--1623376943.B2d7A75.2902
Date: Fri, 11 Jun 2021 02:02:23 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187202
           Summary: ibus can not input on Qt5 applications
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: gnome-bugs-at-suse.de
          Reporter: hillwoodroc-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The ibus is invalid on Qt5 applications on GNOME wayland??? such as telegram and
deepin-music. This issue just occurs on Leap 15.3, works fine on Leap 15.2 and
tumbleweed.

summary: ibus can not input on Qt5 applications


--1623398302.fBbc30.704
Date: Fri, 11 Jun 2021 07:58:22 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187213
           Summary: aaa_base: bash completion is fucked up despite not installed
    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: jengelh-at-inai.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

TAB completion gives a lot of nonsense.

Observed:
=========

09:47 a4:../out/Release ? gdb chr<TAB>
chromium  chroot    chrt
09:47 a4:../out/Release ? ls -l chr*
-rwxr-xr-x 1 jengelh users 6739059568 Jun 11 09:39 chrome
-rw-r--r


--1623514134.C58d2eC40.16721
Date: Sat, 12 Jun 2021 16:08:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187254
           Summary: Clang 9 missing EBO for indirect bases causes miscompilations
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: aaronpuchert@alice-dsl.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After the update to GCC 11, there were numerous test failures in llvm9. Easiest
to debug seemed to be that in

unittests/Support/SupportTests --gtest_filter=Parallel.*

Where the constructor std::thread::thread calls _M_start_thread, we can observe
that on both ends of the call the structure looks different. That's not because
anyone changed it, but because the constructor (compiled by Clang 9) thinks a
std::unique_ptr<std::thread::_State> is 16 bytes big, whereas _M_start_thread
(compiled by GCC 11) thinks it's only 8 bytes:

#1  std::thread::thread<[...]>([...]&&) at
/usr/include/c++/11/bits/std_thread.h:143
(gdb) p sizeof(_State_ptr)
$32 = 16
(gdb) down
#0  std::thread::_M_start_thread at [...]/libstdc++-v3/src/c++11/thread.cc:136
(gdb) p sizeof(_State_ptr)
$33 = 8

Oops. Drilling down a bit, we find that both compilers agree on the base
classes of std::_Tuple_impl<0, std::thread::_State*,
std::default_delete<std::thread::_State> >, but not on the class itself.

Clang 9:
std::_Tuple_impl<0, ...>: 16 byte
std::_Tuple_impl<1, std::default_delete<std::thread::_State>> : 1 byte
std::_Head_base<0, std::thread::_State*, false>: 8 byte

GCC 11:
std::_Tuple_impl<0, ...>: 8 byte
std::_Tuple_impl<1, std::default_delete<std::thread::_State>> : 1 byte
std::_Head_base<0, std::thread::_State*, false>: 8 byte

Clang 12 agrees with GCC 11, which is why we're not seeing a problem there. The
difference can also be seen in the types emitted into the IR:

-


--1623684598.FA570.4641
Date: Mon, 14 Jun 2021 15:29:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187316
           Summary: tpm2_checkquote / ERROR: Malformed PCR file, pcr count cannot be greater than 32, got: <BIG NUMBER>
    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: aplanas-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

This (extracted from documentation) works in the upstream code (master and 5.1
tag), but not in the openSUSE 5.1 package nor in the security devel project:

# tpm2_clear -v
tool="tpm2_clear" version="5.1" tctis="libtss2-tctildr" tcti-default=tcti-abrmd

# tpm2_clear

# tpm2_createek -c 0x81010001 -G rsa -u ekpub.pem -f pem

# tpm2_createak -C 0x81010001 -c ak.ctx -G rsa -s rsassa -g sha256 -u akpub.pem
-f pem -n ak.name
loaded-key:
  name: 000b857dee16b05486730b02a7bb8306305a0ca3ca6f4d83df1afeaaed79ad72d319
  qualified name:
000b3231360fe2abd45d9825cc2ce5df8541ab591b5dc205a2f4affc18b85b4be57a

# tpm2_quote -c ak.ctx -l sha256:15,16,22 -q abc123 -m quote.msg -s quote.sig
-o quote.pcrs -g sha256
quoted:
ff54434780180022000b3231360fe2abd45d9825cc2ce5df8541ab591b5dc205a2f4affc18b85b4be57a0003abc12300000000000092b7000000000000000001201910230016363600000001000b03008041002051cdfd15463a712da38c49e9390d861030e28cf1f19ebe9f5a8b6901a9df64fc
signature:
  alg: rsassa
  sig:
161d0ebf260b70572e81cdc947a84e1e85272319ebca6bc21d5042d20f2dade40a7019c6308d4621b6c11ac33acf33124f8b75309864bd91740984e429ed3be9fa3b9fc917e7b4e9c9804ab18e3a43ff816bb3d736d105a2cbe026e802cd3f73961ffdea02cf95f279034ca5fe263753a15a1237767722cb26847736417c01f0c8b3e95b128664c38f953c8f598715b5d5b823e8aaa42c7db28f826d917f030d0cb3fe98243c08ef15248c997c3b0408a7ec2eb556c3b7ad36b2bf45f2bef62c1a25a11daef5863fbd6799413febcc4766245943b612a65ad22b0e3540c493a1b3899fac3809ccd948e032099ea02c44561945d9a3e4fa7779764cf0b699b443
pcrs:
  sha256:
    15: 0x0000000000000000000000000000000000000000000000000000000000000000
    16: 0x0000000000000000000000000000000000000000000000000000000000000000
    22: 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
calcDigest: 51cdfd15463a712da38c49e9390d861030e28cf1f19ebe9f5a8b6901a9df64fc

# tpm2_checkquote -u akpub.pem -m quote.msg -s quote.sig -f quote.pcrs -g
sha256 -q abc123
ERROR: Malformed PCR file, pcr count cannot be greater than 32, got:
2095863776099172353
ERROR: Unable to run tpm2_checkquote

The last command, using the code compiled from the 5.1 tag, produces this:

# tpm2_checkquote -u akpub.pem -m quote.msg -s quote.sig -f quote.pcrs -g
sha256 -q abc123

pcrs:
  sha256:
    15: 0x0000000000000000000000000000000000000000000000000000000000000000
    16: 0x0000000000000000000000000000000000000000000000000000000000000000
    22: 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
sig: ...


--1623690704.Fa3F30.20911
Date: Mon, 14 Jun 2021 17:11:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187319
           Summary: Kinfocenter, no USB section since version 5.22
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: kailed-at-kailed.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since upgrade to Plasma 5.22 USB section is missing from Kinfocenter. Not sure
if is an upstream bug, it seams working on Arch.

https://bugs.kde.org/show_bug.cgi?id=438569


--1623701480.88bB0.3313
Date: Mon, 14 Jun 2021 20:11:20 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187322
           Summary: VUL-0: CVE-2021-34548: tor: RELAY_END or RELAY_RESOLVED spoofing
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: bwiedemann-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

Fixed in tor 0.3.5.15, 0.4.4.9, 0.4.5.9, or 0.4.6.5

  o Major bugfixes (security, backport from 0.4.6.5):
    - Don't allow relays to spoof RELAY_END or RELAY_RESOLVED cell on
      half-closed streams. Previously, clients failed to validate which
      hop sent these cells: this would allow a relay on a circuit to end
      a stream that wasn't actually built with it. Fixes bug 40389;
      bugfix on 0.3.5.1-alpha. This issue is also tracked as TROVE-2021-
      003 and CVE-2021-34548.

https://lists.torproject.org/pipermail/tor-announce/2021-June/000220.html
https://lists.torproject.org/pipermail/tor-announce/2021-June/000221.html


--1623701492.CDAA38DF0.1419
Date: Mon, 14 Jun 2021 20:11:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187324
           Summary: VUL-0: CVE-2021-34549: tor: hashtable-based CPU denial-of-service attack against relays
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: bwiedemann-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

Fixed in tor 0.3.5.15, 0.4.4.9, 0.4.5.9, or 0.4.6.5

  o Major bugfixes (security, denial of service, backport from 0.4.6.5):
    - Resist a hashtable-based CPU denial-of-service attack against
      relays. Previously we used a naive unkeyed hash function to look
      up circuits in a circuitmux object. An attacker could exploit this
      to construct circuits with chosen circuit IDs, to create
      collisions and make the hash table inefficient. Now we use a
      SipHash construction here instead. Fixes bug 40391; bugfix on
      0.2.4.4-alpha. This issue is also tracked as TROVE-2021-005 and
      CVE-2021-34549. Reported by Jann Horn from Google's Project Zero.

https://lists.torproject.org/pipermail/tor-announce/2021-June/000220.html
https://lists.torproject.org/pipermail/tor-announce/2021-June/000221.html


--1623701489.C8fBFea0.3369
Date: Mon, 14 Jun 2021 20:11:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187323
           Summary: VUL-1: tor: errors from RNG not detected
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: bwiedemann-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

Fixed in tor 0.3.5.15, 0.4.4.9, 0.4.5.9, or 0.4.6.5

  o Major bugfixes (security, defense-in-depth, backport from 0.4.6.5):
    - Detect more failure conditions from the OpenSSL RNG code.
      Previously, we would detect errors from a missing RNG
      implementation, but not failures from the RNG code itself.
      Fortunately, it appears those failures do not happen in practice
      when Tor is using OpenSSL's default RNG implementation. Fixes bug
      40390; bugfix on 0.2.8.1-alpha. This issue is also tracked as
      TROVE-2021-004. Reported by Jann Horn at Google's Project Zero.

https://lists.torproject.org/pipermail/tor-announce/2021-June/000220.html
https://lists.torproject.org/pipermail/tor-announce/2021-June/000221.html


--1623701496.B0F20e00.1483
Date: Mon, 14 Jun 2021 20:11:36 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187325
           Summary: VUL-0: CVE-2021-34550: tor: out-of-bounds memory access in v3 onion service descriptor parsing
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: bwiedemann-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

Fixed in tor 0.3.5.15, 0.4.4.9, 0.4.5.9, or 0.4.6.5

    - Fix an out-of-bounds memory access in v3 onion service descriptor
      parsing. An attacker could exploit this bug by crafting an onion
      service descriptor that would crash any client that tried to visit
      it. Fixes bug 40392; bugfix on 0.3.0.1-alpha. This issue is also
      tracked as TROVE-2021-006 and CVE-2021-34550. Reported by Sergei
      Glazunov from Google's Project Zero.

https://lists.torproject.org/pipermail/tor-announce/2021-June/000220.html
https://lists.torproject.org/pipermail/tor-announce/2021-June/000221.html


--1623707579.1Da8bf6b5.11724
Date: Mon, 14 Jun 2021 21:52:59 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187328
           Summary: Foliate E-book reader fails to start, missing dependency
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: GNOME
          Assignee: gnome-bugs-at-suse.de
          Reporter: aramgrigoryan-at-protonmail.ch
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

after selecting in yast software manager and installing it, the Foliate E-book
reader fails to start with the error message:

bash: /usr/bin/foliate: /usr/bin/gjs: bad interpreter: No such file or
directory

after installin the "gjs" package the same way, everything seems to be working.

Please fix this.
Thanks


--1623745039.37D6be7D1.31297
Date: Tue, 15 Jun 2021 08:17:19 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187332
           Summary: zypper ignores the ordering constraints specified by %systemd_ordering
    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: alarrosa-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

As part of fixing https://bugzilla.opensuse.org/show_bug.cgi?id=1186561 I tried
using %systemd_ordering so systemd is installed before pipewire on a brand new
installation.

After the installation is done executing the following command gave:

> grep -e "install|pipewire|0.3.27" -e "install|systemd|246" /var/log/zypp/history
2021-05-24
09:42:57|install|pipewire|0.3.27-2.1|x86_64||openSUSE-20210522-0|b811f374ec767b8f176864ae37e24be5218e6230741e3707bda934c01486e6c1|
2021-05-24
09:43:42|install|systemd|246.13-1.2|x86_64||openSUSE-20210522-0|06a9eb6641d7a28d2a1d2b100828800db9d11bc1bf196c5a04cca1ced1680339|

So it seems %systemd_ordering is being ignored by zypper.


--1623751727.aA3cEf0.7653
Date: Tue, 15 Jun 2021 10:08:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187336
           Summary: java-11-openj9 and java-1_8_0-openj9 do not build correctly with current libdwarf and gcc11
    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: fstrba-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since the move to GCC11 and the default debug format being DWARF5,
java-11-openj9 and java-1_8_0-openj9 builds end-up in error when omr_ddrgen
parses debugging information.

The error with libdwarf-20201201 is:
Error:
<somepath>/openj9-openjdk-jdk11/omr/ddr/lib/ddr-scanner/dwarf/DwarfScanner.cpp:114
getSourcelist - Getting compilation directory string:
DW_DLE_STRP_OFFSET_BAD(204)
Error:
<somepath>/openj9-openjdk-jdk11/omr/ddr/lib/ddr-scanner/dwarf/DwarfScanner.cpp:1524
traverse_cu_in_debug_section - Failed to get source file list.
Error:
<somepath>/openj9-openjdk-jdk11/omr/ddr/lib/ddr-scanner/dwarf/DwarfScanner.cpp:1591
startScan - Failure scanning
/<somepath>/openj9-openjdk-jdk11/build/linux-x86_64-normal-server-release/vm/runtime/libj9ddr_misc29.debuginfo

When upgrading to libdwarf-20210528, the error is different:
Error:
<somepath>/openj9-openjdk-jdk11/omr/ddr/lib/ddr-scanner/dwarf/DwarfScanner.cpp:239
excludedDie - Getting attr value decl_file: DW_DLE_ATTR_FORM_BAD: In function
formudata (internal function) on seeing form  0x21  (DW_FORM_implicit_const)
Error:
<somepath>/openj9-openjdk-jdk11/omr/ddr/lib/ddr-scanner/dwarf/DwarfScanner.cpp:1560
traverse_cu_in_debug_section - Failed to add type.
Error:
<somepath>/openj9-openjdk-jdk11/omr/ddr/lib/ddr-scanner/dwarf/DwarfScanner.cpp:1591
startScan - Failure scanning
/home/fstrba/devel-cvs/openj9-openjdk-jdk11/build/linux-x86_64-normal-server-release/vm/runtime/libj9ddr_misc29.debuginfo


body:
--1623761360.DDeCf0.18946
Date: Tue, 15 Jun 2021 12:49:20 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187352
           Summary: GCC11 with LTO miscompile aespipe
    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
          Found By: ---
           Blocker: ---

aespipe fails in %check with GCC11 with LTO.
Log:
[   70s] /usr/bin/make test-part3
[   70s] make[2]: Entering directory
'/home/abuild/rpmbuild/BUILD/aespipe-v2.4f'
[   70s] md5sum test-file1 >test-file2
[   70s] echo "f9825b79873f5c439ae9371c1a929a6c  test-file1" >test-file5
[   70s] make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/aespipe-v2.4f'
[   70s] make[1]: Entering directory
'/home/abuild/rpmbuild/BUILD/aespipe-v2.4f'
[   70s] cmp test-file2 test-file5
[   70s] test-file2 test-file5 differ: char 1, line 1
[   70s] make[1]: *** [Makefile:120: test-part2] Error 1

If I disable LTO, the tests pass properly.

summary: GCC11 with LTO miscompile aespipe


--1623761856.EB8561c0.1903
Date: Tue, 15 Jun 2021 12:57:35 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187353
           Summary: CUPS-PDF printer always prints out only a single blank page
    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: r.brinkmann@les2r.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since last dist-upgrade "cups-pdf" delivers a pdf-file with a single blank page
on every print to the CUPS-PDF printer.

Tumbleweed last upgrade     2021-06-08
cups-pdf version:           3.0.1-1.16
ghosscript version:         9.54.0-1.1

Changing either config-file "/etc/cups/cups-pdf.conf" or source-file
"cups-pdf.h" to remove the command line "-c .setpdfwrite" option did not help
at all.

Compare:
Bug 1965717 - cups-pdf uses removed '.setpdfwrite' in GS call
https://bugzilla.redhat.com/show_bug.cgi?id=1965717
> BTW: The fix is to omit `-c .setpdfwrite`, this should work in most cases, unless you really need more memory and you do `-c 3000000 setvmthreshold`.


--1623770333.4d6Cff0.31525
Date: Tue, 15 Jun 2021 15:18:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187360
           Summary: tpm2_eventlog cannot read /sys/kernel/security/tpm0/binary_bios_measurements
    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: aplanas-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

(Note, I think that this is a kernel issue because after fixing bsc#1185869,
this was working. See c11 in the previous report for confirmation)

In Tumbleweed tpm2_eventlog do not work when pointed to the securefs:

# uname -a
Linux dhcp189 5.12.9-1-default #1 SMP Thu Jun 3 07:44:58 UTC 2021 (f17eb01)
x86_64 x86_64 x86_64 GNU/Linux

# tpm2_eventlog /sys/kernel/security/tpm0/binary_bios_measurements
ERROR: Unable to run tpm2_eventlog

But works when reading the copied file:

# cp /sys/kernel/security/tpm0/binary_bios_measurements
binary_bios_measurements

# tpm2_eventlog binary_bios_measurements | head
---
version: 1
events:
- EventNum: 0
  PCRIndex: 0
  EventType: EV_NO_ACTION
  Digest: "0000000000000000000000000000000000000000"
  EventSize: 37
  SpecID:
  - Signature: Spec ID Event03

Running strace shows this:

# strace tpm2_eventlog /sys/kernel/security/tpm0/binary_bios_measurements
...
futex(0x7fba8bafbe18, FUTEX_WAKE_PRIVATE, 2147483647) = 0
openat(AT_FDCWD, "/sys/kernel/security/tpm0/binary_bios_measurements",
O_RDONLY) = 3
lseek(3, 0, SEEK_CUR)                   = 0
newfstatat(3, "", {st_mode=S_IFREG|0440, st_size=0, ...}, AT_EMPTY_PATH) = 0
newfstatat(3, "", {st_mode=S_IFREG|0440, st_size=0, ...}, AT_EMPTY_PATH) = 0
lseek(3, 0, SEEK_SET)                   = 0
lseek(3, 0, SEEK_SET)                   = 0
close(3)                                = 0
write(2, "ERROR: ", 7ERROR: )                  = 7
write(2, "Unable to run eventlog", 22Unable to run eventlog)  = 22
write(2, "\n", 1
)                       = 1
exit_group(1)                           = ?
+++ exited with 1 +++

# strace tpm2_eventlog binary_bios_measurements
...
futex(0x7fb147cede18, FUTEX_WAKE_PRIVATE, 2147483647) = 0
openat(AT_FDCWD, "binary_bios_measurements", O_RDONLY) = 3
lseek(3, 0, SEEK_CUR)                   = 0
newfstatat(3, "", {st_mode=S_IFREG|0440, st_size=10494, ...}, AT_EMPTY_PATH) =
0
newfstatat(3, "", {st_mode=S_IFREG|0440, st_size=10494, ...}, AT_EMPTY_PATH) =
0
lseek(3, 8192, SEEK_SET)                = 8192
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
2302) = 2302
lseek(3, 0, SEEK_SET)                   = 0
close(3)                                = 0
openat(AT_FDCWD, "binary_bios_measurements", O_RDONLY) = 3
newfstatat(3, "", {st_mode=S_IFREG|0440, st_size=10494, ...}, AT_EMPTY_PATH) =
0
read(3, "\0\0\0\0\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0%\0\0\0"...,
8192) = 8192
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
4096) = 2302
close(3)                                = 0
write(1, "---", 3)                      = 3
...


--1623775980.E85F80.937
Date: Tue, 15 Jun 2021 16:53:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1187371
           Summary: [Build 20210614] qgis uninstallable due to grass build fail
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/1789037/modules/qgis
                    /steps/21
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: openQA
           Blocker: Yes

## Observation

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

grass has failed to build against the latest gdal update, which in turn makes
qgis unresolvable and uninstallable.

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

## Reproducible

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

## Expected result

Last good: (unknown) (or more recent)

## Further details

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