body:
--1533775052.aC4A0baC0.13597
Date: Thu, 9 Aug 2018 00:37:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1104264

            Bug ID: 1104264
           Summary: Recommended packages that are missing:
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: luizluca@tre-sc.jus.br
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,

Multiple files recommends packages that does not exist:

kfilemetadata5-5.48.0-1.1.x86_64 recommends catdoc
elfutils-0.173-1.1.x86_64 recommends elfutils.lang
libgcr-3-1-3.28.0-1.2.x86_64 recommends gcr-ask-pass
patterns-base-enhanced_base-20170410-4.1.x86_64 recommends genisoimage
libgtk-3-0-3.22.30-4.1.x86_64 recommends gtk3-immodule-tigrigna
kactivitymanagerd-5.13.4-1.1.x86_64 recommends kactivitymanagerd-imports
patterns-base-enhanced_base_opt-20170410-4.1.x86_64 recommends ksymoops
patterns-base-enhanced_base-20170410-4.1.x86_64 recommends recode
patterns-base-minimal_base-20170410-4.1.x86_64 recommends system-group-trusted
terminfo-base-6.1-6.5.x86_64 recommends terminfo-screeen
patterns-yast-yast2_basis-20180613-1.1.x86_64 recommends yast2-ldap-client

summary: Recommended packages that are missing:


body:
Build Identifier:

If package is also an application (as if in "zypper if -t application"), zypper
does not consider it as unneeded if it is installed automatically (as
dependency) and present in /var/lib/zypp/AutoInstalled. "zypper pa --unneeded"
doesn't show these packages, and "zypper rm --clean-deps" on packages that
depend on such packages doesn't remove them.

Reproducible: Always

Steps to Reproduce:
1. "zypper in xfce4-screenshooter"
2. "echo xfce4-screenshooter >> /var/lib/zypp/AutoInstalled"
3. "zypper pa --unneeded"
Actual Results:
"zypper pa --unneded" doesn't find any unneeded packages.

Expected Results:
"zypper pa --unneded" should show xfce4-screenshooter.

summary: zypper does not consider packages that are also applications as unneeded if they are automatically installed


--1533885774.6E14Ae0.14801
Date: Fri, 10 Aug 2018 07:22:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1104452

            Bug ID: 1104452
           Summary: transactional-update: /var/lib/zypp not a directory
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kubic
          Assignee: iforster-at-suse.com
          Reporter: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On current openSUSE Kubic:

# transactional-update reboot pkg install kubectl systemd-container
Checking for newer version.
transactional-update 2.5 started
Options: reboot pkg install kubectl systemd-container
Separate /var detected.
Creating read-only snapshot of current system state (#1)
Copying /etc state into snapshot /.snapshots/3/snapshot
Copying /etc state into snapshot /.snapshots/4/snapshot
cp: cannot create regular file '/.snapshots/4/snapshot/var/lib/zypp/': Not a
directory


--1533919528.cfECE4.12179
Date: Fri, 10 Aug 2018 16:45:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1104531
           Summary: /etc/profile.d/bash_completion.sh syntax error in ksh
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: ecmartinson-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When connecting to a LEAP 15 system as a user with ksh login shell, the
/etc/profile.d/bash_completion.sh file reports a syntax error:

ksh: /etc/profile.d/bash_completion.sh[2]: syntax error: unexpected
operator/operand '=~'

When comparing this file to the same file on LEAP 42.3, there are some simple
syntax changes that aren't compatible with ksh.  I updated my copy of the
script to match the 42.3 release and the problem is gone.  That is the only
difference.


--1533927207.57c52a0.895
Date: Fri, 10 Aug 2018 18:53:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1104543
           Summary: config.postfix does not start tlsmgr in master.cf when using POSTFIX_SMTP_TLS_CLIENT="must"
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: x86-64
                OS: SUSE Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: uli-at-bluewin.ch
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

/usr/sbin/config.postfix comments out the tlsmgr line in /etc/postfix/master.cf
unless $tlsserver or $tlsclient is set to "yes". This breaks the "must" option
from /etc/sysconfig/postfix:

## Type:        list(no,yes,must)
## Default:     no
## Config:      postfix
#
# Do you want to enable postfix smtp client to use TLS
#
POSTFIX_SMTP_TLS_CLIENT="must"

config.postfix excerpt:
        if ( $tlsclient ne "yes" && $tlsserver ne "yes" && $sslserver ne "yes"
) {
            $line = "#".$1;
        } else {
            $line = $1;
        }


body:
Build Identifier:

In a fully updated openSUSE Leap 15 with konqueror-17.12.3-lp150.1.3.x86_64
downloaded files get a strange modify timestamp which prohibits sorting by file
date with ls -t.

Files downloaded and saved with konqueror get modify timestamp of
2106-02-07 07:28:15.000000000 +0100

which according to
https://www.unixtimestamp.com/index.php
represents
the epoch value 4294967295

Is equivalent to:

02/07/2106 @ 6:28am (UTC)
2106-02-07T06:28:15+00:00 in ISO 8601

Sun, 07 Feb 2106 06:28:15 +0000 in RFC 822, 1036, 1123, 2822

Sunday, 07-Feb-06 06:28:15 UTC in RFC 2822

2106-02-07T06:28:15+00:00 in RFC 3339

And 4294967295 = 0xFFFFFFFF = UINT_MAX

Reproducible: Always

Steps to Reproduce:
e.g.
1. use konqueror to navigate to
http://download.opensuse.org/update/leap/15.0/oss/x86_64/
2. right click "apache2-mod_php7-7.2.5-lp150.1.7_lp150.2.6.1.x86_64.drpm" and
select "save link to" to download the file to your system
3. display the file timestamps, e.g. with stat <saved-file> and check the value
of the modify timestamp

Actual Results:
Faulty modify timestamp:

$ stat apache2-mod_php7-7.2.5-lp150.1.7_lp150.2.6.1.x86_64.drpm
  File: apache2-mod_php7-7.2.5-lp150.1.7_lp150.2.6.1.x86_64.drpm
  Size: 80280           Blocks: 160        IO Block: 4096   regular file
Device: fe06h/65030d    Inode: 23597146    Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/  user)   Gid: (  100/   users)
Access: 2018-08-12 12:29:08.318988332 +0200
Modify: 2106-02-07 07:28:15.000000000 +0100
Change: 2018-08-12 12:29:07.190969355 +0200
 Birth: -

Expected Results:
 Copying the URL and downloading the same file (ignoring mirrorbrain) with wget
results in "normal" values for the modify timestamp:
 $ stat apache2-mod_php7-7.2.5-lp150.1.7_lp150.2.6.1.x86_64.drpm.1
  File: apache2-mod_php7-7.2.5-lp150.1.7_lp150.2.6.1.x86_64.drpm.1
  Size: 80280           Blocks: 168        IO Block: 4096   regular file
Device: fe06h/65030d    Inode: 23597148    Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/  user)   Gid: (  100/   users)
Access: 2018-08-12 12:39:20.000000000 +0200
Modify: 2018-07-19 21:46:39.000000000 +0200
Change: 2018-08-12 12:39:20.861303254 +0200
 Birth: -

This modify timestamp is consistent with the file date displayed at the
website:
19-Jul-2018 19:46 (UTC)

I remember I observed such faulty timestamps also when transferring files via
krdc and a shared directory to the machine running krdc. So maybe the problem
is not konqueror specific.
Another thought: the value UINT_MAX could be the initial value, and the actual
value of the remote side is written somewhere else in memory, then this might
even ba e security issue.

summary: files downloaded with konqueror get modify timestamp 2106-02-07 07:28:15.000000000 +0100


--1534103642.FAdf4.4199
Date: Sun, 12 Aug 2018 19:54:02 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1104598
           Summary: /etc/crictl.yaml owned by wrong package (cri-o not cri-tools)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kubic
          Assignee: vrothberg-at-suse.com
          Reporter: rbrown-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: kubic-bugs-at-opensuse.org, vrothberg-at-suse.com
          Found By: ---
           Blocker: ---
                CC: vrothberg-at-suse.com
             Flags: needinfo?(vrothberg-at-suse.com)

/etc/crictl.yaml is consumed by the crictl binary provided by cri-tools

But /etc/crictl.yml is currently packaged as part of cri-o

This seems very wrong to me

And also has very real world issues - as crictl on Kubic is constantly
complaining about the deprecated syntax for it's container runtime endpoint,
which should be unix:///var/run/crio/crio.sock not the current
/var/run/crio/crio.sock

2 Solutions are possible

Option a) get crictl.yaml packaged in cri-tools instead
or
b) get cri-o packaged in devel:kubic and caught up with the respective
cri-tools version to solve this discrepency

Valentin, which do you prefer?


--1534144915.3e7A4E0.30952
Date: Mon, 13 Aug 2018 07:21:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1104620

            Bug ID: 1104620
           Summary: Datovka package needs to be kept at latest version in openSUSE distribution
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: tchvatal-at-suse.com
          Reporter: tchvatal-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Without always providing latest version of the package czech egov communication
will not be working right.

There are simply too many changes to communication to rely on older release.


--1534208914.287C00F70.3948
Date: Tue, 14 Aug 2018 01:08:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1104749
           Summary: security:netfilter/xtables-addons: Bug build for kernel/stable 4.18 fails
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: All
                OS: openSUSE Factory
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: 3rd party software
          Assignee: jengelh-at-inai.de
          Reporter: pgnet.dev-at-gmail.com
        QA Contact: bnc-team-screening-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

1st stab at building xtables-addons 3.0 against kernel/stable 4.18, with gcc
8.2.1

with manual overwrite of $kminor check

    https://www.spinics.net/lists/netfilter-devel/msg55667.html

in

    configure
        ...
        if test "$kmajor" -gt 4 -o "$kmajor" -eq 4 -a "$kminor" -gt 16; then
        if test "$kmajor" -gt 4 -o "$kmajor" -eq 4 -a "$kminor" -gt 18; then
        ...

build fail log

https://build.opensuse.org/package/live_build_log/home:pgnd:Kernel:stable/xtables-addons/openSUSE_Leap_15.0/x86_64


body:
Build Identifier:

Clean installs of Leap 15.0 with the latest patches applied always crashes when
attempting to boot into the Xen Dom0 world on Dell R210II servers but always
succeeds to boot the non-virtualized kernel.

Some Googling based on the serial log output led me to this post of a fix
applied to the Xen code which another part of the thread said ended up in
4.15.5:

    https://lists.xenproject.org/archives/html/xen-devel/2018-04/msg00158.html

The first link near the bottom of the post describes the problem as the
compiler making reference to the %gs register before its initialized and the
second link points to the fix.  Later parts of the thread indicate the fix went
into 4.15.5.

It should be noted that the fix author (Jeurgen) had was a page fault issue and
the original poster (Ajay) had an unhandled invalid opcode fault like I'm
seeing.  This post which includes dialog from both Ajay and Jeurgen suggests
this patch may have solved the invalid opcode issue:

    https://lists.xenproject.org/archives/html/xen-devel/2018-04/msg00294.html

As an aside, you'll see a comment in the console log about missing
"iommu_inclusive_mapping=1" but I've added that every way I could think of and
did it a second round with the addition of "iommu=1" but I later found that
these are supposed to be the defaults in Xen 4.10 so I'm not sure if this is a
Red Herring:

     http://xenbits.xen.org/docs/4.10-testing/misc/xen-command-line.html

Reproducible: Always

Steps to Reproduce:
Install Leap 15.0 on a 250GB SSD with a 512MB /boot/efi partition and the rest
an LVM partition.  A 20GB root (/) and 3GB swap are created in the LVM
partition - NO OTHER partitions or DomU configuration is used.  The KDE Desktop
option was chosen.  The Software selections are changed to add "Console Tools,"
"Xen Virtual Machine/Host Server," "Help and Support Documentation,"
"Documentation" and "Network Administration."  Removed are "Multimedia,"
"Office Software," "Graphics," and "Games."  Individual RPMs for "vlan,"
"bridge-utils" and "patch" were also added.  YaST Online Update was used to
bring in any updates.  The firewall was disabled and SSH enabled.  Note that to
use YaST for the updates the machine was booted into the non-VM kernel after
the installation.  It's the next (or any successive boot) to the Xen kernel
that dies.  I can always go back to the non-VM kernel with no problems.
Actual Results:
The machine crashes.  The instructions below suggest I should add my captured
logs as attachments after the bug is created so that's where the detail will
appear.

Expected Results:
A boot to at least a console prompt if not a full KDE login window.

I'll attach the console log I pulled off the serial port by adding "

summary: Xen Dom0 Boot crashes with unhandled invalid opcode fault - fix may exist in kernel 4.15.5


body:
--1534260033.3caAccBE0.1432
Date: Tue, 14 Aug 2018 15:20:33 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1104820
           Summary: libvirt json parse errors
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: jfehlig-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

libvirt 4.6.0 switched from using yajl to jansson for parsing json. Is some
cases qemu creates non-compliant json, which yajl could handle but jansson
cannot. E.g.

virsh define foo.xml
virsh start foo --paused
virsh domstats foo
virsh resume foo
error: Failed to resume domain foo
error: internal error: failed to parse JSON 1:59: too big integer near
'18446744073709551615'

A standards-compliant JSON implementation need not support integers outside of
the range of JavaScript's Number.MIN_SAFE_INTEGER to Number.MAX_SAFE_INTEGER
[1], but qemu relies on clients supporting full unsigned 64-bit integers.
Unfortunately the upstream jansson community is not fond of supporting unsigned
64-bit integers [2].

Due to this and other problems with the yajl->jansson switch, the upstream
libvirt community has decided to revert the switch and continue using yajl for
json parsing.

[1]
http://www.ecma-international.org/ecma-262/6.0/index.html#sec-number.max_safe_integer
[2] https://github.com/akheron/jansson/issues/154

summary: libvirt json parse errors


body:
--1534260493.7fDeeD0.4278
Date: Tue, 14 Aug 2018 15:28:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1104821
           Summary: Make cri-o default for kubernetes on Kubic
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kubic
          Assignee: rbrown-at-suse.com
          Reporter: rbrown-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

https://trello.com/c/EB1v0dVq/19-make-cri-o-default-for-k8s

Use cri-runtime provides so docker-kubic can be a drop in replacement

pkgs: kubernetes patterns-caasp


--1534262552.eF53B3.14934
Date: Tue, 14 Aug 2018 16:02:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1104824

            Bug ID: 1104824
           Summary: Bug in xen-netfront.c, concerning replacement of MAX_SKB_FRAGS with XEN_NETIF_NR_SLOTS_MIN
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: Manfred.Haertel@rz-online.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After a recent kernel upgrade in a DomU, which run on a system with an older
kernel in Dom0, the DomU crashed on heavy incoming network load.

So I filed https://bugzilla.suse.com/show_bug.cgi?id=1102997 and later I
invalidated my own bug report, because I could not reproduce the bug with a
current Dom0 kernel.

However, after some debugging and trying to understand how the driver works, I
still think that the change where MAX_SKB_FRAGS was replaced by
XEN_NETIF_NR_SLOTS_MIN is not completely correct. I hope my wording is correct
(or at least understandable), trying to explain what I think is wrong.

The variable max in xennet_get_responses() can now become larger by one than
before.

BEFORE the patch, the variable was 17 or 18, depending on rx->status <=
RX_COPY_THRESHOLD, which means it depends on the size of the first fragment. If
the first fragment was larger than the threshold, the variable became 17, and
18 otherwise.

So, if a (ethernet GSO) frame with 18 fragments was received AND the first
fragment was "large" (larger than the threshold), the condition slots > max in
xennet_get_responses() was met, and the whole frame was discarded (and the
infamous message "Too many slots" appeared).

I don't think the Xen network code allows a frame with 19 fragments, so the
condition slots > max could not be met at all when the first fragment was
"small".

So, in xennet_fill_frags() we could be sure, that if we have a frame with 18
fragments, then the first fragment would be "small".

In THIS case, if the condition shinfo->nr_frags == MAX_SKB_FRAGS was met
(meaning we have 18 fragments), we knew that the first fragment was small and
so __pskb_pull_tail() was able to decrement nr_frags by one. So,
BUG_ON(shinfo->nr_frags >= MAX_SKB_FRAGS) could never lead to a crash because
nr_frags was now smaller than MAX_SKB_FRAGS.

NOW the variable max in xennet_get_responses() can become 18 or 19, again
depending on the size of the first fragment. Again, as (I think) a frame with
19 or even 20 fragments is not possible, the condition slots > max is NEVER met
and the message "Too many slots" is actually impossible.

However, in xennet_fill_frags() things are different. A frame with 18 fragments
is now possible even if the first fragment is "large" (larger than
RX_COPY_THRESHOLD). The problem is, that in this case __pskb_pull_tail() is NOT
able to decrement shinfo->nr_frags by one. I THINK this is coded in the
following lines in xennet_poll():

NETFRONT_SKB_CB(skb)->pull_to = rx->status;
if (NETFRONT_SKB_CB(skb)->pull_to > RX_COPY_THRESHOLD)
        NETFRONT_SKB_CB(skb)->pull_to = RX_COPY_THRESHOLD;

(I admit that I do not really understand what this actually does).

So, with a "large" first fragment, shinfo->nr_frags is *still* MAX_SKB_FRAGS
(18) after the pull, and so

BUG_ON(shinfo->nr_frags >= MAX_SKB_FRAGS);

causes a crash.

It seems that the crash does NOT happen with a recent Dom0 kernel. I also tried
to understand why.

It seems as if the xen-netback driver in recent kernels does send only a
maximum of *16* fragments (at least, I could not provoke it to send more). So,
of course, the crash can never happen.

On the other hand, I think, the code in xen-netfront is not correct in general.
A Dom0 kernel which sends 18 fragments with a "large" first fragment is able to
crash the DomU. For example, older linux kernels in Dom0, though I do not know
when the change in netback to a fewer number of fragments happened.

I also do not understand which is the universally correct solution.


--1534265359.a2bF3e573.26300
Date: Tue, 14 Aug 2018 16:49:19 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1104833
           Summary: Initramfs unpacking failed: junk in compressed archive
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: armv7
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: matwey.kornilov-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,

I am trying to run
openSUSE-Tumbleweed-ARM-JeOS-beaglebone.armv7l-2018.08.13-Build1.1 at
BeagleBone Black board.

I see the following after Grub2:

Loading kernel...
Loading initrd...
[    0.005152] timer_probe: no matching timers found
[    0.424134] Initramfs unpacking failed: junk in compressed archive
[    0.757548] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
[    0.765875] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.17.13-1-default #1
openSUSE Tumbleweed (unreleased)
[    0.775657] Hardware name: Generic AM33XX (Flattened Device Tree)
[    0.781830] [<c0321000>] (unwind_backtrace) from [<c0319640>]
(show_stack+0x20/0x28)
[    0.789618] [<c0319640>] (show_stack) from [<c0de3998>]
(dump_stack+0xb8/0xe4)
[    0.796886] [<c0de3998>] (dump_stack) from [<c036c1a0>] (panic+0xf0/0x28c)
[    0.803806] [<c036c1a0>] (panic) from [<c15018ec>]
(mount_block_root+0x26c/0x31c)
[    0.811328] [<c15018ec>] (mount_block_root) from [<c1501a30>]
(mount_root+0x94/0x98)
[    0.819111] [<c1501a30>] (mount_root) from [<c1501b94>]
(prepare_namespace+0x160/0x1a8)
[    0.827155] [<c1501b94>] (prepare_namespace) from [<c1501420>]
(kernel_init_freeable+0x42c/0x440)
[    0.836075] [<c1501420>] (kernel_init_freeable) from [<c0df8a44>]
(kernel_init+0x18/0x128)
[    0.844382] [<c0df8a44>] (kernel_init) from [<c03010ac>]
(ret_from_fork+0x14/0x28)
[    0.851984] Exception stack(0xdb137fb0 to 0xdb137ff8)
[    0.857057] 7fa0:                                     00000000 00000000
00000000 00000000
[    0.865272] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000
[    0.873487] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[    0.880154] Rebooting in 90 seconds..


--1534286644.C204d0.2952
Date: Tue, 14 Aug 2018 22:44:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1104876

            Bug ID: 1104876
           Summary: Installing libxmlsec1-openssl1 does not upgrade libxmlsec1-1 to the same version
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: kallan-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

During the installation of open-vm-tools 1.3.0, libxmlsec1-openssl1 is also
required to be installed.  Doing a zypper in on open-vm-tools triggers the
install of libxmlsec1-openssl1.  Vrsion 1.2.26 gets installed.
libxmlsec1-openssl1 depends on libxemsec1-1.  libxmsec1-1 was already installed
and remained at version 1.2.25.  After open-vm-tools was installed, trying to
start the open-vm-tools vgauthd service service failed due to version
incompatibilities between libxmlsec1-openss1 and libxmlsec1-1.

Subsequently, updating libxmlsec1-1 to the available version1.2.26 allowed the
vgauthd service to start.


body:
--1534321120.B2D54B0.25963
Date: Wed, 15 Aug 2018 08:18:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1104898
           Summary: rpc.rquotad takes 100% CPU
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: 64bit
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: martin-at-gabelmann.biz
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The quota daemon eats 100% CPU when setting the variable RQUOTAD_PORT in
/etc/sysconfig/nfs.

This bug was already reported here:
https://bugs.launchpad.net/ubuntu/+source/quota/+bug/1774431
and a new patch was pushed to the qutoa main repos.

Please ship this update as we cannot simply open our firewall. First users on
our servers reported that their quota is not updated although they cleaned up
their directories, so the daemon is not functional.

summary: rpc.rquotad takes 100% CPU


--1534348532.043647C23.6188
Date: Wed, 15 Aug 2018 15:55:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1104952
           Summary: WINE: No sound in 32-bit SDL applications due to missing libpulse0-32bit package
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: bugreporter-at-candymail.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On an x86-64 host, there is no sound in WINE 32-bit SDL applications because
libpulse0-32bit is not installed by default.
To fix this, add libpulse0-32bit as a dependency or recommendation to
wine-32bit.


--1534370954.CBB00.23047
Date: Wed, 15 Aug 2018 22:09:14 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1104990

            Bug ID: 1104990
           Summary: firewalld cannot use NetworkManager interfaces
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: luizluca@tre-sc.jus.br
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,

Since firewalld upgraded to 0.6.0 (TW 20180812), it cannot use NetworkManager
interfaces:

# nmcli connection
NAME                              UUID                                  TYPE
  DEVICE
xxxx            a2e01b3f-1af6-498a-97ed-926c949c623d  ethernet  eno1

# nmcli connection show a2e01b3f-1af6-498a-97ed-926c949c623d | grep zone
connection.zone:                        public

# grep -i zone /etc/NetworkManager/system-connections/xxxx
zone=public

# grep -i zone /etc/sysconfig/network/ifcfg-eno1
ZONE=public

Everything looks ok, but:

# firewall-cmd --get-default-zone
public
# firewall-cmd --get-zone-of-interface=eno0
no zone
# firewall-cmd --get-active-zones
vms
  interfaces: vboxnet0 vboxnet1

# firewall-cmd --zone=public --add-interface=eno1
The interface is under control of NetworkManager and already bound to 'public'
The interface is under control of NetworkManager, setting zone to 'public'.
success

In the end, I have no iptables rules for public zone.

I downgraded to firewalld-0.5.3-lp150 from LEAP15. Now it works:

# firewall-cmd --get-active-zones
public
  interfaces: eno1
vms
  interfaces: vboxnet0 vboxnet1

Even through, this still (since always?) fails

# firewall-cmd --get-zone-of-interface=eno0
no zone


--1534421034.A4B85.16738
Date: Thu, 16 Aug 2018 12:03:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1105068

            Bug ID: 1105068
           Summary: xfsprogs: systemd service files not built
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: jeffm-at-suse.com
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: lurodriguez-at-suse.com
          Found By: ---
           Blocker: ---

when playing with prjconf I found that xfsprogs behaves differently when
systemd is present in the build root. It builds systemd service files in that
case which our package normally lacks. Is that by intention or should xfsprogs
ship the service files? (you don't need to pull in systemd for that, just the
macros)


--1534427296.a87C5.31267
Date: Thu, 16 Aug 2018 13:48:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1105084

            Bug ID: 1105084
           Summary: ledger - Fails to build with Boost 1.68.0
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: amajer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1105081
          Found By: ---
           Blocker: ---

New Boost library has been released and unfortunately this package fails to
build with it. The new boost library is already submitted to
devel:libraries:c_c++/boost and will be submitted to openSUSE:Factory shortly.

https://build.opensuse.org/package/show/home:adamm:boost_test/ledger

> [   58s] [ 14%] Building CXX object src/CMakeFiles/ledger.dir/ptree.cc.o
> [   58s] cd /home/abuild/rpmbuild/BUILD/ledger-3.1.1/build/src && /usr/bin/c++   -I/home/abuild/rpmbuild/BUILD/ledger-3.1.1/lib/utfcpp/v2_0/source -I/home/abuild/rpmbuild/BUILD/ledger-3.1.1/build  -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -DNDEBUG -O2 -g -DNDEBUG   -std=c++11 -o CMakeFiles/ledger.dir/ptree.cc.o -c /home/abuild/rpmbuild/BUILD/ledger-3.1.1/src/ptree.cc
> [   62s] In file included from /home/abuild/rpmbuild/BUILD/ledger-3.1.1/src/exprbase.h:57,
> [   62s]                  from /home/abuild/rpmbuild/BUILD/ledger-3.1.1/src/expr.h:45,
> [   62s]                  from /home/abuild/rpmbuild/BUILD/ledger-3.1.1/src/op.h:45,
> [   62s]                  from /home/abuild/rpmbuild/BUILD/ledger-3.1.1/src/scope.h:45,
> [   62s]                  from /home/abuild/rpmbuild/BUILD/ledger-3.1.1/src/item.h:45,
> [   62s]                  from /home/abuild/rpmbuild/BUILD/ledger-3.1.1/src/xact.h:45,
> [   62s]                  from /home/abuild/rpmbuild/BUILD/ledger-3.1.1/src/iterators.h:45,
> [   62s]                  from /home/abuild/rpmbuild/BUILD/ledger-3.1.1/src/generate.h:45,
> [   62s]                  from /home/abuild/rpmbuild/BUILD/ledger-3.1.1/src/generate.cc:34:
> [   62s] /home/abuild/rpmbuild/BUILD/ledger-3.1.1/src/utils.h:47:10: fatal error: boost/uuid/sha1.hpp: No such file or directory
> [   62s]  #include <boost/uuid/sha1.hpp>
> [   62s]           ^~~~~~~~~~~~~~~~~~~~~
> [   62s] compilation terminated.


--1534515129.fB6c75.19402
Date: Fri, 17 Aug 2018 14:12:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1105217

            Bug ID: 1105217
           Summary: aegisub: fails to build with Boost 1.68.0
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: amajer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1105081
          Found By: ---
           Blocker: ---

New Boost library has been released and unfortunately this package fails to
build with it. The new boost library is already in devel:libraries:c_c++/boost
and will be submitted to openSUSE:Factory shortly.

https://build.opensuse.org/package/show/home:adamm:boost_test/aegisub

[  229s]
/home/abuild/rpmbuild/BUILD/aegisub-3.2.2/src/search_replace_engine.cpp: In
member function 'bool SearchReplaceEngine::ReplaceAll()':
[  229s]
/home/abuild/rpmbuild/BUILD/aegisub-3.2.2/src/search_replace_engine.cpp:317:61:
error: call of overloaded
'distance(boost::u32regex_iterator<__gnu_cxx::__normal_iterator<const char*,
std::__cxx11::basic_string<char> > >,
boost::u32regex_iterator<__gnu_cxx::__normal_iterator<const char*,
std::__cxx11::basic_string<char> > >)' is ambiguous
[  229s]       boost::u32regex_iterator<std::string::const_iterator>());
[  229s]                                                              ^
[  229s] In file included from /usr/include/boost/range/distance.hpp:18,
[  229s]                  from /usr/include/boost/range/functions.hpp:21,
[  229s]                  from
/usr/include/boost/range/iterator_range_core.hpp:38,
[  229s]                  from /usr/include/boost/range/iterator_range.hpp:13,
[  229s]                  from
/usr/include/boost/range/adaptor/filtered.hpp:16,
[  229s]                  from
/home/abuild/rpmbuild/BUILD/aegisub-3.2.2/src/agi_pre.h:104:
[  229s] /usr/include/boost/iterator/distance.hpp:49:9: note: candidate:
'typename boost::iterators::iterator_difference<Iterator>::type
boost::iterators::distance_adl_barrier::distance(SinglePassIterator,
SinglePassIterator) [with SinglePassIterator =
boost::u32regex_iterator<__gnu_cxx::__normal_iterator<const char*,
std::__cxx11::basic_string<char> > >; typename
boost::iterators::iterator_difference<Iterator>::type = long int]'
[  229s]          distance(SinglePassIterator first, SinglePassIterator last)
[  229s]          ^~~~~~~~
[  229s] In file included from /usr/include/c++/8/bits/stl_algobase.h:66,
[  229s]                  from /usr/include/c++/8/algorithm:61,
[  229s]                  from
/home/abuild/rpmbuild/BUILD/aegisub-3.2.2/src/agi_pre.h:72:
[  230s] /usr/include/c++/8/bits/stl_iterator_base_funcs.h:138:5: note:
candidate: 'typename std::iterator_traits<_Iterator>::difference_type
std::distance(_InputIterator, _InputIterator) [with _InputIterator =
boost::u32regex_iterator<__gnu_cxx::__normal_iterator<const char*,
std::__cxx11::basic_string<char> > >; typename
std::iterator_traits<_Iterator>::difference_type = long int]'
[  230s]      distance(_InputIterator __first, _InputIterator __last)
[  230s]      ^~~~~~~~
[  232s]
/home/abuild/rpmbuild/BUILD/aegisub-3.2.2/src/resolution_resampler.cpp: In
function 'void ResampleResolution(AssFile*, ResampleSettings)':
[  232s]
/home/abuild/rpmbuild/BUILD/aegisub-3.2.2/src/resolution_resampler.cpp:235:24:
warning: this statement may fall through [-Wimplicit-fallthrough=]
[  232s]     border_horizontally = !border_horizontally;
[  232s]     ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
[  232s]
/home/abuild/rpmbuild/BUILD/aegisub-3.2.2/src/resolution_resampler.cpp:236:3:
note: here
[  232s]    case ResampleARMode::AddBorder:
[  232s]    ^~~~


--1534544899.Ca5FE58e0.3394
Date: Fri, 17 Aug 2018 22:28:19 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105262
           Summary: Openshot-qt package is broken because it is missing a dependency
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: jeanbarloy-at-hotmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello guys,

Openshot-QT (Leap-15.0-Oss repo) package is broken on Leap 15.

It needs a dependency which is not specified: Python-Request

"logger:ERROR import requests
      logger:ERROR ModuleNotFoundError
      logger:ERROR :
      logger:ERROR No module named 'requests'
"

(I had to manually install it from Yast to make it work)


--1534555001.e245DF41.2598
Date: Sat, 18 Aug 2018 01:16:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105268
           Summary: Wayland: Screen rotation to left or right gives blank screen from second attempt onward
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: xorg-maintainer-bugs-at-forge.provo.novell.com
          Reporter: badshah400-at-gmail.com
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

GNOME 3.28.2 on Wayland

Rotating the screen to the left or right from its default orientation works the
first time, but gives a blank screen thereafter, with the following log
recorded on the journal:

Aug 18 03:08:41 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic
update failure on pipe A (start=140995 end=140996) time 1818 us, min 1907, max
1919, scanline start 1870, end 89
Aug 18 03:08:42 gsd-color[4609]: failed to set screen _ICC_PROFILE: Failed to
open file
“/home/badshah/.local/share/icc/edid-400eada130818d341c3ea2fa3de67f03.icc”:
Permission denied
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:45 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:45 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:45 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:45 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space
left on device
Aug 18 03:08:45 gnome-shell[4401]: Failed to read EDID from 'eDP-1': No such
file or directory
Aug 18 03:08:45 gnome-shell[4401]: Failed to read EDID from 'eDP-1': No such
file or directory
Aug 18 03:08:45 gnome-shell[4401]: Failed to read EDID from 'eDP-1': No such
file or directory
Aug 18 03:08:45 gsd-color[4609]: failed to set screen _ICC_PROFILE: Failed to
open file
“/home/badshah/.local/share/icc/edid-400eada130818d341c3ea2fa3de67f03.icc”:
Permission denied


--1534591127.5AE2e673.23350
Date: Sat, 18 Aug 2018 11:18:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1105271

            Bug ID: 1105271
           Summary: Kernel 4.4.143-65-default does not boot on Dell Precision T5810 (Xeon E5-1620 v3)
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: sebastian.parschauer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: L3
           Blocker: ---

Created attachment 780104
  --> http://bugzilla.suse.com/attachment.cgi?id=780104&action=edit
Photo of screen when hanging after early ucode update

The new Leap 42.3 kernel 4.4.143-65-default does not boot on my Dell Precision
Tower 5810 SUSE R&D workstation with Intel Xeon E5-1620 v3 CPU.

Please note: *That CPU has an unstable TSC.*

Boot hangs directly after early microcode update. Had to boot the previous
kernel 4.4.140-62-default.


--1534666180.18fF4841.20463
Date: Sun, 19 Aug 2018 08:09:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105278
           Summary: zabbix30 jsLoader unable to load the jquery
    Classification: openSUSE
           Product: openSUSE Backports
           Version: SLE-12
          Hardware: S/390
                OS: SLES 12
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Packages
          Assignee: packagehub-bugs-at-suse.com
          Reporter: uhaider.msee15seecs-at-seecs.edu.pk
        QA Contact: packagehub-bugs-at-suse.com
          Found By: ---
           Blocker: ---

Testing on s390x with chrome, firefox and IE the web interface was not working
properly. The page was taking too much time to load and top menu was not
working. Chrome dev tools following errors

Uncaught ReferenceError: jQuery is not defined
MMenu is not defined
...

Also the status of jsLoader in network tab was failed.

Solution:

In jsLoader.php changing

header('Content-Type: application/javascript; charset=UTF-8');
to
header('Content-Type: text/javascript; charset=UTF-8');

solved the issue.


--1534831099.25621BA0.32335
Date: Tue, 21 Aug 2018 05:58:18 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105438
           Summary: VUL-1: CVE-2018-1000221: pkgconf: contains a Buffer Overflow vulnerability indequote() that can result in dequote() function returns 1-byte allocation ifinitial length is 0, leading to buffer ov
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/213101/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Development
          Assignee: ngompa13-at-gmail.com
          Reporter: meissner-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-1000221

pkgconf version 1.5.0 to 1.5.2 contains a Buffer Overflow vulnerability in
dequote() that can result in dequote() function returns 1-byte allocation if
initial length is 0, leading to buffer overflow. This attack appear to be
exploitable via specially crafted .pc file. This vulnerability appears to have
been fixed in 1.5.3.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000221
https://git.dereferenced.org/pkgconf/pkgconf/pulls/3


--1534858613.F7C1Ad7d4.18736
Date: Tue, 21 Aug 2018 13:36:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105510
           Summary: iPXE build failure: Unrecognised relocation type 4
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: jjolly-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 780322
  --> http://bugzilla.opensuse.org/attachment.cgi?id=780322&action=edit
ipxe-efi-recognize-plt32-relocation.patch

iPXE build is failing with the following error:

    ./util/elf2efi64 --subsystem=10 bin-x86_64-efi/ipxe.efi.tmp
bin-x86_64-efi/ipxe.efi
    Unrecognised relocation type 4

This is due to a change in the buildtools that causes the efi build to set some
relocatable symbols to R_X86_64_PLT32 instead of R_X86_64_PC32.

The simple solution is to allow the elf2efi tool to recognize the PLT32
relocation symbols just as it would the PC32 symbols.


--1534868210.a25BaDD3.11281
Date: Tue, 21 Aug 2018 16:16:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105536
           Summary: Spectre V2 : System has more than MAX_PA/2 memory. L1TF mitigation not effective.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: studio-at-anchev.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

A system with kernel-default-4.12.14-lp150.12.16.1.x86_64 shows the following
info:

# dmesg | grep -i l1tf
[    0.020108] Spectre V2 : System has more than MAX_PA/2 memory. L1TF
mitigation not effective.

# find /sys/devices/system/cpu/vulnerabilities/ -type f -print -exec
/usr/bin/cat '{}' \;
/sys/devices/system/cpu/vulnerabilities/spectre_v2
Mitigation: Full generic retpoline, IBPB, IBRS_FW
/sys/devices/system/cpu/vulnerabilities/spec_store_bypass
Mitigation: Speculative Store Bypass disabled via prctl and seccomp
/sys/devices/system/cpu/vulnerabilities/l1tf
Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v1
Mitigation: __user pointer sanitization
/sys/devices/system/cpu/vulnerabilities/meltdown
Mitigation: PTI

CPU flags show that "flush_l1d" is available:

# lscpu | egrep "Model name:|Flags"
Model name:          Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est
tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer
aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp
tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida
arat pln pts flush_l1d

# zypper se -si ucode-intel microcode
Loading repository data...
Reading installed packages...

S  | Name        | Type    | Version              | Arch   | Repository
---+-------------+---------+----------------------+--------+--------------
i+ | ucode-intel | package | 20180807-lp150.2.7.1 | x86_64 | *Update (OSS)

An attempt to mitigate the L1TF vulnerability using kernel boot command line
options kvm-intel.enable_ept=0 or l1tf=full,force didn't change anything -
still vulnerable and not effective. Additionally I tried disabling
HyperThreading from BIOS but that didn't help either.

According to https://lore.kernel.org/patchwork/patch/974259/:

"Note there is no workaround for [...] systems which have more than MAX_PA/2
worth of memory. The later case is very unlikely to happen on real systems."

However the dmesg line seems to show this exact case. The system has 32GB of
RAM (the maximum which the CPU and the mainboard support).

Based on a forum discussion it was suggested to file these findings in a bug
report.


--1534945365.8BBeAbD0.22080
Date: Wed, 22 Aug 2018 13:42:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105633
           Summary: jemalloc fails in unit tests with gcc8 and profiling enabled
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: armv7
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 780422
  --> http://bugzilla.opensuse.org/attachment.cgi?id=780422&action=edit
Build log with gcc8 and profiling enabled

jemalloc fails in tests with gcc8 and profiling enabled (-enable-prof option).
Last line of test is:
  === test/unit/arena_reset ===

jemalloc passes all the tests if:
* CC is gcc7 instead of gcc8 (with profiling enabled)
* CC is gcc8 but profiling is disabled


--1534950244.2aef7e9.24564
Date: Wed, 22 Aug 2018 15:04:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105654
           Summary: mesa-dri-nouveau: Incorrect description when confirming the package license
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Installation
          Assignee: yast2-maintainers-at-suse.de
          Reporter: lgrimmer-at-suse.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

During the initial installation on my physical system using the
openSUSE-Tumbleweed-NET-x86_64-Snapshot20180818-Media.iso image, I receive a
popup window with the following title:

"Confirm Package License: Mesa-dri-nouveau"

The last paragraph of the message that is displayed here (which isn't actually
a "license", but rather a warning/disclaimer) reads:

'Please click "Accept" if you accept the risks that may come with the
installation of this driver. Choose "Cancel" to prevent installation of the
driver and use software emulation instead.'

However, the popup window does not provide any buttons with these labels - they
are labeled "I Agree" and "I Disagree".

I guess the text of that message should probably be updated to reflect this
change (and eventually any other package that contains a similar message?).


--1535032422.a4dd11.2497
Date: Thu, 23 Aug 2018 13:53:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105792
           Summary: firstboot wizard missing/broken branding
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: lnussel-at-suse.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

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

yast2-firstboot looks rather odd. It has a side bar but no other branding. See
attached screenshot.

To reproduce
# zypper in yast2-firstboot
# touch /var/lib/YaST2/reconfig_system
# reboot


--1535036033.F0E550.19631
Date: Thu, 23 Aug 2018 14:53:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105798
           Summary: [Build 20180820] Plasma 5 on wayland: wallpaper is missed
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/740782/modules/start
                    _wayland_plasma5/steps/24
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: oorlov-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

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

After log in to Wayland session, the wallpaper is missed (black).

Steps to reproduce:

1. Run clean installation of TW with KDE (Build 20180820);
2. Update repos to 'Snapshot20180820';
3. Execute 'pkcon install -yp plasma5-session-wayland' and wait until the
installation is finished;
4. Log out;
5. Select "Desktop Session: Plasma(Wayland)";
6. Enter password and log in.

Expected result:
Wallpaper is shown.
Actual result:
Wallpaper is missed. Please see the screenshot
(https://openqa.opensuse.org/tests/740782#step/start_wayland_plasma5/24)

Please, also see 'wayland-session.log' logs.

The issue was found with openQA. Please see more details below:
----------------------------------------------------------------------------

## Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-kde-wayland@64bit_virtio
fails in
[start_wayland_plasma5](https://openqa.opensuse.org/tests/740782/modules/start_wayland_plasma5/steps/24)

## Reproducible

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

## Expected result

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

## Further details

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


--1535037013.a2AC0.28051
Date: Thu, 23 Aug 2018 15:10:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105803
           Summary: openSUSE:Backports:SLE-15/tls: error "protocol not supported"
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: x86-64
                OS: SLES 15
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: idonmez-at-suse.com
          Reporter: gerard.ranke-at-kmt.hku.nl
        QA Contact: bnc-team-screening-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

We use tcl scripts to connect to our ldapserver. With sles15 or leap15, the
openssl version requires one to use tls v1.7.14 or higher. However, opening a
tclsh and entering "ldap::secure_connect <ldapserver> 636 always gives a
"protocol not supported" error. More info:
% set errorInfo
protocol not supported
    while executing
"tls::import $sock -cafile "" -certfile "" -keyfile ""  -request 1 -server 0
-require 0 -ssl2 no -ssl3 yes -tls1 yes"
    (procedure "ldap::secure_connect" line 18)
    invoked from within
"ldap::secure_connect yoda.hku.nl"
On other servers (with tlsv1.6.7), it connects just fine. Also, running an
ldapserver on the same host, with tlsv1.7.14, always gives "protocol not
found". Last, no matter what sles or leap version, I can always set up a
session with our ldapservers using openssl s_client -CApath /etc/ssl/certs
-connect <ldapserver>:636. It then reports:
Protocol  : TLSv1.2
Cipher    : AES256-GCM-SHA384
Using a tclsh, and entering:
tls::ciphers tls1.2
it shows a list of ciphers, and I can see AES256-GCM-SHA384 is included.
Thanks for your attention!


body:
--1535047244.0b5A5d200.8603
Date: Thu, 23 Aug 2018 18:00:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1105821

            Bug ID: 1105821
           Summary: firewalld drops icmpv6
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: markos.chandras-at-suse.com
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 780614
  --> http://bugzilla.suse.com/attachment.cgi?id=780614&action=edit
nft list ruleset

It seems that after firewalld switched to nft, icmpv6 is completely dropped:
ping6 fe80::4748:4aeb:6d22:254d%br-lan
PING fe80::4748:4aeb:6d22:254d%br-lan (fe80::4748:4aeb:6d22:254d%br-lan): 56
data bytes
^C
-

summary: firewalld drops icmpv6


body:
Build Identifier:

Package "terminator" is missing required dependency python2-cairo - it does not
run without it.

Reproducible: Always

Steps to Reproduce:
$ terminator
Actual Results:
Traceback (most recent call last):
  File "/usr/bin/terminator", line 47, in <module>
    import terminatorlib.optionparse
  File "/usr/lib/python2.7/site-packages/terminatorlib/optionparse.py", line
22, in <module>
    from util import dbg, err
  File "/usr/lib/python2.7/site-packages/terminatorlib/util.py", line 19, in
<module>
    import cairo
ImportError: No module named cairo

summary: terminator: Missing dependency on python2-cairo


--1535103789.8Ace20.2004
Date: Fri, 24 Aug 2018 09:43:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105899
           Summary: [Build 20180820] not name resolution inside docker containers with default network
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/740986/modules/docke
                    r/steps/57
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Containers
          Assignee: containers-bugowner-at-suse.de
          Reporter: slindomansilla-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

## Observation

A docker container started with default network is not able to resolve domain
names.
If the container is started with "--network host", the names can be resolved.
This issue happens since snapshot 20180818 and it may be causing that OBS is
not able to build docker images because dependencies cannot be downloaded
without name resolution.

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-docker_image@64bit fails
in
[docker](https://openqa.opensuse.org/tests/740986/modules/docker/steps/57)

## Reproducible

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

## Expected result

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

## Further details

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


--1535114032.Ba3f320.19567
Date: Fri, 24 Aug 2018 12:33:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105930
           Summary: Update drivers for Kobo (new firmware 4.10.11586) and Kindle (cover images in KFX) in Calibre
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Maintenance
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: cornelis-at-solcon.nl
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Kobo has released a new firmware version and calibre needs a minor update to
add support for this.

Upstream calibre has added support for cover images for the KFX formate.

Until now when there was a driver update needed for an e-reader we released the
version then in Factory. Because of the fix for bug #1104597 I prefer not to do
this now. That fix is not urgent for Leap and causes warnings during update.
This means we loose updates for websites that can be read in Calibre, but I
consider that minor (until someone submits a bug for this). Keep the drivers
for e-readers up-to-date is important, because communicating with e-readers is
the most important function of calibre. I am preparing a package that backports
these updates.


--1535220802.eb13D11e5.32074
Date: Sat, 25 Aug 2018 18:13:22 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1105992
           Summary: Transactional-Update broken in snapshot 20180824
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Kubic
          Assignee: iforster-at-suse.com
          Reporter: rbrown-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: kubic-bugs-at-opensuse.org
          Found By: ---
           Blocker: ---

0824 introduced transactional-update 2.6

https://build.opensuse.org/package/rdiff/openSUSE:Factory/transactional-update?linkrev=base&rev=32

It's failing all tests and appears to be displaying incorrect behaviour

https://openqa.opensuse.org/tests/742638#step/transactional_update/57

Compared to 0822 I'm noticing the following differences:

https://openqa.opensuse.org/tests/741289#step/transactional_update/57

(note: the code for the test does not appear to have changed:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/caasp/transactional_update.pm
)

Update test #2 is meant to be a no-op, because it should be updating when there
is nothing to do

In 0822 the pointless `cleanup up` test produced the following logs:

> # Result:
> Checking for newer version.
> transactional-update 2.6 started
> Options: cleanup up
> Separate /var detected.
> Adding cleanup algorithm to snapshot #6
> Adding "important=yes" to snapshot #6
> zypper: nothing to update
> transactional-update finished
> trup-0-

In 0824 the exact same test produces the following logs:

> # Result:
> Checking for newer version.
> transactional-update 2.6 started
> Options: cleanup up
> Separate /var detected.
> Adding cleanup algorithm to snapshot #6
> Adding "important=yes" to snapshot #6
> /usr/sbin/transactional-update: line 760: [: too many arguments
> Creating read-only snapshot of current system state (#8)
> Copying /etc state into snapshot /.snapshots/9/snapshot
> Copying /etc state into snapshot /.snapshots/10/snapshot
> Calling zypper up
> Loading repository data...
> Reading installed packages...
>
> Nothing to do.
> Trying to rebuild kdump initrd
> Please reboot your machine to activate the changes and avoid data loss.
> transactional-update finished
> trup-0-

I find the following lines in 0824 suspicious, leading me to the questions
below:

> /usr/sbin/transactional-update: line 760: [: too many arguments

Why does txl-upd now complain about too many arguments?

> Creating read-only snapshot of current system state (#8)
> Copying /etc state into snapshot /.snapshots/9/snapshot
> Copying /etc state into snapshot /.snapshots/10/snapshot

Why does txl-upd make 3 snapshots (8, 9, 10) even when there is nothing to do?

Why does txl-upd make 2 snapshots for /etc? (This is less suspicious, I'm just
curious)

Bug marked as Major because it makes all of Kubics tests red ;)


--1535288094.bb2250.30812
Date: Sun, 26 Aug 2018 12:54:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106000
           Summary: llvm-config contains gcc-incompatible flags
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: msrb-at-suse.com
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

llvm-config --cflags contains "-Werror=unguarded-availability-new" which makes
builds with gcc fail:

cc1plus: error: -Werror=unguarded-availability-new: no option
-Wunguarded-availability-new


--1535346167.A1f860.16728
Date: Mon, 27 Aug 2018 05:02:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1106014

            Bug ID: 1106014
           Summary: cross-arm-none-gcc8-8.1.1+r262873-1.3.x86_64 -mcpu=cortex-m0plus emits incorrect arch
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: william-at-blackhats.net.au
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hi,

The cross-arm-none-gcc8 package in OpenSUSE may have an incorrect definition
for -mcpu=cortex-m0plus.

On Fedora27 compiling the code found in the tomu-sample repo causes the ELF to
have the following details:

No version information found in this file.
Attribute Section: aeabi
File Attributes
  Tag_CPU_name: "Cortex-M0+"
  Tag_CPU_arch: v6S-M
  Tag_CPU_arch_profile: Microcontroller
  Tag_THUMB_ISA_use: Thumb-1
  Tag_ABI_PCS_wchar_t: 4
  Tag_ABI_FP_denormal: Needed
  Tag_ABI_FP_exceptions: Needed
  Tag_ABI_FP_number_model: IEEE 754
  Tag_ABI_align_needed: 8-byte
  Tag_ABI_align_preserved: 8-byte, except leaf SP
  Tag_ABI_enum_size: small
  Tag_ABI_optimization_goals: Aggressive Size

Please note the Tap_CPU_arch.

On OpenSUSE the following is shown:

No version information found in this file.
Attribute Section: aeabi
File Attributes
  Tag_CPU_name: "ARM v6K"
  Tag_CPU_arch: v6K
  Tag_CPU_arch_profile: Microcontroller
  Tag_ARM_ISA_use: Yes
  Tag_THUMB_ISA_use: Thumb-1
  Tag_ABI_PCS_wchar_t: 4
  Tag_ABI_FP_denormal: Needed
  Tag_ABI_FP_exceptions: Needed
  Tag_ABI_FP_number_model: IEEE 754
  Tag_ABI_align_needed: 8-byte
  Tag_ABI_align_preserved: 8-byte, except leaf SP
  Tag_ABI_enum_size: small
  Tag_ABI_optimization_goals: Aggressive Size

This causes the development board to fail to initialise as it is the wrong CPU
arch. There are other platforms (arch linux, macOSX) where they correctly emit
armv6s-m for -mcpu=cortex-m0plus.

Version of affected packages:

cross-arm-binutils-2.31-1.1.x86_64
cross-arm-none-newlib-devel-3.0.0-2.5.x86_64
cross-arm-none-gcc8-8.1.1+r262873-1.3.x86_64

Reproduction:

https://github.com/im-tomu/tomu-samples

Follow the readme, or:

git submodule init
git submodule update

make -C libopencm3
make -C usb_simple

readelf -A usb_simple/usb_simple.elf


body:
--1535359605.e026D13.18240
Date: Mon, 27 Aug 2018 08:46:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1106051

            Bug ID: 1106051
           Summary: Huge Nautilus icon in Xfce menu
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: shundhammer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 780824
  --> http://bugzilla.suse.com/attachment.cgi?id=780824&action=edit
Screenshot: Huge icon in menu

In my Xfce menu, the icon for the Nautilus file manager is huge: 512x512
pixels. All other applications in that menu seem to use a 32x32 icon, except
for Nautilus.

See screenshots.

[shundhammer @ morgul] ~ % cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20180815"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20180815"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20180815"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"

Involved package versions:

nautilus-3.28.1-1.3.x86_64

xfce4-appfinder-4.12.0-1.10.x86_64
xfce4-appfinder-lang-4.12.0-1.10.noarch
xfce4-dict-0.8.1-1.1.x86_64
xfce4-dict-lang-0.8.1-1.1.noarch
xfce4-icon-theme-4.4.3-28.5.noarch
xfce4-mixer-4.11.0-2.4.x86_64
xfce4-mixer-lang-4.11.0-2.4.noarch
xfce4-notifyd-0.4.2-1.2.x86_64
xfce4-notifyd-branding-upstream-0.4.2-1.2.noarch
xfce4-notifyd-lang-0.4.2-1.2.noarch
xfce4-panel-4.12.2-2.2.x86_64
xfce4-panel-branding-upstream-4.12.2-2.2.noarch
xfce4-panel-lang-4.12.2-2.2.noarch
xfce4-power-manager-1.6.1-2.2.x86_64
xfce4-power-manager-branding-openSUSE-4.12.0-9.5.noarch
xfce4-power-manager-lang-1.6.1-2.2.noarch
xfce4-screenshooter-1.9.2-1.2.x86_64
xfce4-screenshooter-lang-1.9.2-1.2.noarch
xfce4-session-4.12.1-7.3.x86_64
xfce4-session-branding-upstream-4.12.1-7.3.noarch
xfce4-session-lang-4.12.1-7.3.noarch
xfce4-settings-4.12.4-1.1.x86_64
xfce4-settings-branding-openSUSE-4.12.0-9.5.noarch
xfce4-settings-lang-4.12.4-1.1.noarch
xfce4-splash-branding-openSUSE-15.0-3.2.noarch
xfce4-taskmanager-1.2.1-1.1.x86_64
xfce4-taskmanager-lang-1.2.1-1.1.noarch
xfce4-terminal-0.8.7.4-1.2.x86_64
xfce4-terminal-lang-0.8.7.4-1.2.noarch

(see also attached rpm-qa.txt for a complete list)

It took me a while that it's Nautilus; it's not my desktop's default file
manager, and it is utterly confusing that it's called only "files" in the menu
and in its own "about" dialog. I have about 3-5 file managers installed, so
those things should clearly tell me which one it is that I see. But that's
another bug.

summary: Huge Nautilus icon in Xfce menu


body:
--1535376041.23Da04.20360
Date: Mon, 27 Aug 2018 13:20:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106103
           Summary: owncloud-client v2.4.2 segfaults
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: aeszter-at-gwdg.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On my system, the owncloud client (executable is named owncloud) always
segfaults immediately after launch. v2.4.1 used to work fine.

This may be triggered by my desktop environment (i3), although I did not
analyze beyond the following:
The culprit appears to be fix-systray-menu-pos.patch: with upstream,
platformMenu is checked against NULL before dereferencing it; but with the
patch, the pointer is dereferenced unconditionally, the NULL check comes too
late.

summary: owncloud-client v2.4.2 segfaults


--1535470223.aA18f0.19840
Date: Tue, 28 Aug 2018 15:30:23 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106279
           Summary: VUL-1: CVE-2018-1000656 python-flask: Improper Input Validation via crafted JSON file
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/213087/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Other
          Assignee: mimi.vx-at-gmail.com
          Reporter: meissner-at-suse.com
        QA Contact: security-team-at-suse.de
                CC: petr-at-cervinka.net
          Found By: Security Response Team
           Blocker: ---

rh#1623131

The Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper
Input Validation vulnerability in flask that can result in Large amount of
memory usage possibly leading to denial of service. This attack appear to be
exploitable via Attacker provides JSON data in incorrect encoding. This
vulnerability appears to have been fixed in 0.12.3.

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1623131
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000656
https://github.com/pallets/flask/pull/2691
https://github.com/pallets/flask/releases/tag/0.12.3


--1535495030.faCff1.25939
Date: Tue, 28 Aug 2018 22:23:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106319
           Summary: Exception when starting firewall tool from YaST2 GUI
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: petorrus-at-gmail.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

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

Wanted to use the firewall config GUI for the first time today, so yast
installed it. When trying to run it I get this error message (see attachment),
possible related to this forumpost:
https://forums.opensuse.org/showthread.php/532842-firewall-config-not-running?p=2878654#post2878654


--1535522896.33B6e20.25588
Date: Wed, 29 Aug 2018 06:08:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106341
           Summary: VUL-1: CVE-2017-15430: chromium: Unsafe navigation in Chromecast in Google Chrome prior to 63.0.3239.84 allowed aremote attacker to bypass navigation restrictions via a crafted HTML page.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/213430/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Other
          Assignee: tchvatal-at-suse.com
          Reporter: meissner-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2017-15430

Unsafe navigation in Chromecast in Google Chrome prior to 63.0.3239.84 allowed
a
remote attacker to bypass navigation restrictions via a crafted HTML page.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-15430
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15430
https://crbug.com/780484


body:
--1535533302.e5A1730.7259
Date: Wed, 29 Aug 2018 09:01:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1106366

            Bug ID: 1106366
           Summary: collectl daemon failed to start
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: glin-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

In my single CPU VM, the collectl daemon always failed to start without an
obvious error or warning.

# systemctl status collectl
? collectl.service - Performance data collection for a number of subsystems
   Loaded: loaded (/usr/lib/systemd/system/collectl.service; enabled; vendor
preset: disabled)
   Active: inactive (dead) since Wed 2018-08-29 10:00:37 CST; 9min ago
  Process: 1162 ExecStart=/usr/bin/collectl $OPTS /etc/collectl.conf
(code=exited, status=0/SUCCESS)
 Main PID: 1162 (code=exited, status=0/SUCCESS)

It turned out that the type of collectl.service is not forking, so systemd
won't wait on the creation of /var/run/collectl.pid. In my case, the pid file
wasn't created in time, so systemd just terminated both parent and child
collectl processes.

summary: collectl daemon failed to start


--1535534245.6A263.12788
Date: Wed, 29 Aug 2018 09:17:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106369
           Summary: oops when reading /sys/module/kvm_intel/parameters/vmentry_l1d_flush
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: seife-at-novell.slipkontur.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Trying to find out if my machine is safe against L1TF, i tried to read
/sys/module/kvm_intel/parameters/vmentry_l1d_flush with "cat". Result:
segmentation fault.

[316179.538612] general protection fault: 0000 [#1] SMP PTI
[316179.538628] Modules linked in: reiserfs minix hfs vfat fat ebtable_filter
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables devlink
tcp_diag inet_diag af_packet iscsi_ibft iscsi_boot_sysfs tun msr xfs libcrc32c
bcache isl6421 cx24120 mt312 stv0297 bcm3510 lgdt330x nxt200x mt352 pl2303 i915
usbserial video drm_kms_helper b2c2_flexcop_pci gpio_ich drm e1000e
b2c2_flexcop drm_panel_orientation_quirks fb_sys_fops s5h1420 syscopyarea
sysfillrect ptp cx24113 sysimgblt cx24123 iTCO_wdt i2c_algo_bit coretemp
mei_wdt iTCO_vendor_support mei_me mei kvm_intel lpc_ich kvm pps_core pcspkr
shpchp i2c_i801 irqbypass button acpi_cpufreq ppdev nfsd auth_rpcgss nfs_acl
lockd grace sunrpc hid_generic serio_raw ehci_pci uhci_hcd ehci_hcd usbhid
usbcore parport_serial parport_pc parport edd fan ata_piix
[316179.538773]  ahci libahci ata_generic pata_jmicron thermal dm_mirror
dm_region_hash dm_log sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc
scsi_dh_alua tpm_rng fuse stv0299 budget_ci rc_core budget_core ttpci_eeprom
saa7146 dvb_core bridge stp llc
[316179.538818] CPU: 1 PID: 32170 Comm: cat Not tainted
4.12.14-lp150.12.16-default #1 openSUSE Leap 15.0
[316179.538831] Hardware name: FUJITSU SIEMENS ESPRIMO E5730
/D2824-A1, BIOS 6.00 R1.19-03.2824.A1            07/12/2011
[316179.538854] task: ffff880202efa280 task.stack: ffffc90005080000
[316179.538872] RIP: 0010:string+0x20/0x80
[316179.538884] RSP: 0018:ffffc90005083cf0 EFLAGS: 00010286
[316179.538897] RAX: 646e69775f656c71 RBX: ffff880169add000 RCX:
ffff0a00ffffff04
[316179.538910] RDX: 646e69775f656c70 RSI: ffff8801e9adcfff RDI:
ffffffffffffffff
[316179.538922] RBP: ffff8801e9adcfff R08: fffffffffffffffe R09:
ffff880169add000
[316179.538935] R10: ffffc90005083da8 R11: 0000000000000000 R12:
000000007fffffff
[316179.538948] R13: ffffc90005083d48 R14: ffffffffa039c472 R15:
ffffffffa039c472
[316179.538962] FS:  00007fc499203500(0000) GS:ffff88020dd00000(0000)
knlGS:0000000000000000
[316179.538975] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[316179.538987] CR2: 00007fc49918f000 CR3: 000000011580c000 CR4:
00000000000406e0
[316179.539000] Call Trace:
[316179.539015]  vsnprintf+0x299/0x490
[316179.539029]  sprintf+0x42/0x50
[316179.539043]  ? kernel_param_unlock+0x20/0x20
[316179.539057]  param_attr_show+0x55/0xa0
[316179.539067]  module_attr_show+0x1c/0x30
[316179.539079]  sysfs_kf_seq_show+0xb3/0x110
[316179.539089]  seq_read+0xde/0x430
[316179.539101]  __vfs_read+0x26/0x140
[316179.539111]  vfs_read+0x89/0x130
[316179.539121]  SyS_read+0x42/0x90
[316179.539132]  do_syscall_64+0x7b/0x150
[316179.539143]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[316179.539154] RIP: 0033:0x7fc498d2eb41
[316179.539162] RSP: 002b:00007ffc8eec5978 EFLAGS: 00000246 ORIG_RAX:
0000000000000000
[316179.539173] RAX: ffffffffffffffda RBX: 0000000000020000 RCX:
00007fc498d2eb41
[316179.539183] RDX: 0000000000020000 RSI: 00007fc499190000 RDI:
0000000000000003
[316179.539193] RBP: 0000000000020000 R08: ffffffffffffffff R09:
0000000000000000
[316179.539203] R10: 000000000000038b R11: 0000000000000246 R12:
00007fc499190000
[316179.539213] R13: 0000000000000003 R14: 00007fc49919000f R15:
0000000000020000
[316179.539222] Code: ff 66 2e 0f 1f 84 00 00 00 00 00 49 89 f9 48 89 cf 48 c1
ff 30 48 81 fa ff 0f 00 00 4c 8d 47 ff 76 45 48 85 ff 74 51 48 8d 42 01 <0f> b6
12 84 d2 74 46 49 01 c0 4c 89 cf eb 0c 48 83 c0 01 0f b6
[316179.539277] RIP: string+0x20/0x80 RSP: ffffc90005083cf0
[316179.539312] ---[ end trace c15f829bcf6318d2 ]---

This is on a not so new Core2 duo, which did not get a ucode update:

server:~ # rpm -q ucode-intel; dmesg |head -1
ucode-intel-20180807-lp150.2.7.1.x86_64
[    0.000000] microcode: microcode updated early to revision 0xa0b, date =
2010-09-28

processor    : 1
vendor_id    : GenuineIntel
cpu family    : 6
model        : 23
model name    : Intel(R) Core(TM)2 Duo CPU     E8500  @ 3.16GHz
stepping    : 10
microcode    : 0xa0b
cpu MHz        : 1999.000
cache size    : 6144 KB
physical id    : 0
siblings    : 2
core id        : 1
cpu cores    : 2
apicid        : 1
initial apicid    : 1
fpu        : yes
fpu_exception    : yes
cpuid level    : 13
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64
monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm pti
tpr_shadow vnmi flexpriority dtherm
bugs        : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips    : 6333.80
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

server:/sys/devices/system/cpu/vulnerabilities # grep . *
l1tf:Mitigation: PTE Inversion; VMX: SMT disabled, L1D EPT disabled
meltdown:Mitigation: PTI
spec_store_bypass:Vulnerable
spectre_v1:Mitigation: __user pointer sanitization
spectre_v2:Mitigation: Full generic retpoline

I was actually wondering if I could enable EPT without rebooting when I tripped
over this bug. ;-)

Probably the missing flush_l1d flag in this CPU was never considered...


body:
Build Identifier:

I installed the package 'pari-gp' with 'pari-elldata' via "zypper in pari-gp
pari-elldata". Everything was okay, except pari-elldata is not installed
correctly. I mean, I can run pari/gp calculator via "gp", and can do some
normal computations. However, if I want to access the "elliptic curve data",
i.e. 'pari-elldata', the gp calculator complains:

? ellsearch(11)
  ***   at top-level: ellsearch(11)
  ***                 ^-------------
  *** ellsearch: error opening elldata file: `/usr/share/pari/elldata/ell0'.
  ***   Break loop: type 'break' to go back to GP prompt
break> break

I checked there are files in /usr/share/pari. I found them in
/usr/share/pari/data/elldata. So I symlinked:
/usr/share/pari/elldata -> /usr/share/pari/data/elldata

I think we need to repackage 'pari-elldata' in order to install correctly.

Reproducible: Always

Steps to Reproduce:
1.Install pari-gp and pari-elldata: zypper in pari-gp pari-elldata.
2.Run the gp calculator: gp
3.Try to access pari-elldata, for example: ellsearch(11)
Actual Results:
? ellsearch(11)
  ***   at top-level: ellsearch(11)
  ***                 ^-------------
  *** ellsearch: error opening elldata file: `/usr/share/pari/elldata/ell0'.
  ***   Break loop: type 'break' to go back to GP prompt
break> break

Expected Results:
%1 = [["11a1", [0, -1, 1, -10, -20], []], ["11a2", [0, -1, 1, -7820, -263580],
[]], ["11a3", [0, -1, 1, 0, 0], []]]

N/A

pkgs: pari-elldata pari-galdata pari-galpol pari-seadata

summary: pari-elldata is not installed correctly


--1535546032.cDa2a5.6624
Date: Wed, 29 Aug 2018 12:33:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106405
           Summary: patterns-base: do not pull in hardware specific packages
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Patterns
          Assignee: dimstar-at-opensuse.org
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: fvogt-at-suse.com, simonf.lees-at-suse.com
          Found By: ---
           Blocker: ---

The base pattern pulls in quite some packages that are not needed in a
container/chroot. For example dracut, grub2, device-mapper, btrfsprogs etc.

In the same way we do not pull in a kernel via patterns, we should not require
packages only relevant to physical machines resp VMs. YaST will for example
select grub2 itself. btrfsprogs has filesystem namespace that pulls it in etc.


--1535612569.c7860d1.15981
Date: Thu, 30 Aug 2018 07:02:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106528
           Summary: Update wireless-regdb to version 2018.05.31
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: mpluskal-at-suse.com
          Reporter: mpluskal-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

This version contains updated power limits for France


--1535637733.f8FF14.2994
Date: Thu, 30 Aug 2018 14:02:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106598
           Summary: sssd: D-Bus service not registered for InfoPipe responder (D-Bus file wrong/missing?)
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: varkoly-at-suse.com
          Reporter: kbabioch-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: ckowalczyk-at-suse.com, jengelh-at-inai.de,
                    mpluskal-at-suse.com
          Found By: ---
           Blocker: ---

While looking into SSSD I've stumbled upon the following error:

kbabioch-sso-client:~ # sssctl domain-list
Unable to get domains list [3]: Communication error
org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.sssd.infopipe was not provided by any .service files
Check that SSSD is running and the InfoPipe responder is enabled. Make sure
'ifp' is listed in the 'services' option in sssd.conf.

There is a sssd-ifp sub-package, which contains the sssd-ifp binary. However
there is no service file registering the D-Bus service. In the upstream project
this is done via a systemd unit file [1], but this unit file is not installed
on Leap 15.0 at all.

Also there is a D-Bus service file in the upstream project, because it
registers the sss_signal binary, which will send a signal (SIGUSR2) to the sssd
process. This will trigger sssd to go online.

[1]:
https://github.com/SSSD/sssd/blob/13c8450788a429fa49ba532b40ebfd7f3a4132e4/src/sysv/systemd/sssd-ifp.service.in
[2]:
https://github.com/SSSD/sssd/blob/13c8450788a429fa49ba532b40ebfd7f3a4132e4/src/responder/ifp/org.freedesktop.sssd.infopipe.service.in


--1535670271.5C8Ac620.13132
Date: Thu, 30 Aug 2018 23:04:31 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106676
           Summary: Xplayer error at launch: couldn't load '/usr/lib64/xplayer/plugins/grilo/grilo.ui' interface.
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Xfce
          Assignee: bnc-team-xfce-at-forge.provo.novell.com
          Reporter: maurizio.galli-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 781416
  --> http://bugzilla.opensuse.org/attachment.cgi?id=781416&action=edit
screenshot of error dialog

Hello,
When starting Xplayer I get the following error prompt:

Couldn't load '/usr/lib64/xplayer/plugins/grilo/grilo.ui' interface.
/usr/lib64/xplayer/plugins/grilo/grilo.ui:113:1 Invalid Object type
'XplayerSearchEntry'

After this error the Xplayer quits.

I attached a screenshot for reference.


body:
--1535717576.35A128811.28658
Date: Fri, 31 Aug 2018 12:12:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1106751

            Bug ID: 1106751
           Summary: iptables does not work with kernel-default-base
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Initially reported as
https://github.com/kubic-project/automation/pull/474#issuecomment-417329301

Docker (and cri-o) do not work in Kubic VM images as iptables does not work:

g47:~ # iptables -L
iptables: No chain/target/match by that name.

pkgs: kernel-default-base kernel-source


--1535747395.bC8D7.24768
Date: Fri, 31 Aug 2018 20:29:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106809
           Summary: Wicked receives SIGSEGV after system reboot (/usr/sbin/wicked --systemd ifup all).
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: jacob.long-at-unisys.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 781600
  --> http://bugzilla.opensuse.org/attachment.cgi?id=781600&action=edit
This zip contains a full backtrace.txt and structures.txt showing values at
time of core dump.

Running the following package levels:
libwicked-0-6-0.6.40-37.2.x86_64.rpm
libwicked-0-6-debuginfo-0.6.40-37.2.x86_64.rpm
wicked-0.6.40-37.2.x86_64.rpm
wicked-debuginfo-0.6.40-37.2.x86_64.rpm
wicked-debugsource-0.6.40-37.2.x86_64.rpm
wicked-service-0.6.40-37.2.x86_64.rpm

Wicked segfaults and dumps core on system reboot when running ifup command,
e.g.:
ExecStart=/usr/sbin/wicked/ --systemd ifup all

It seems that ni_fsm_process_find_pending_worker() in src/fsm.c allows index
'i' to overrun the value of 'fsm->workers.count' in the 'fsm->workers.data'
array.

A full backtrace.txt is attached as well as structures.txt showing the value of
i and the pointers referenced at time of the SIGSEGV.

   5530 static ni_ifworker_t *
   5531 ni_fsm_process_rename_find_pending_worker(ni_fsm_t *fsm, const
   ni_ifworker_     t *w)
   5532 {
   5533         ni_ifworker_t *c;
   5534         unsigned int i;
   5535
   5536         for (i = 0; fsm->workers.count; ++i) {
   5537                 c = fsm->workers.data[i];
   5538                 if (!c || c == w || c->type != w->type || c->device)
   5539                         continue;
   5540                 if (!c->pending || !ni_string_eq(c->name, w->name))
   5541                         continue;
   5542                 return c;
   5543         }
   5544         return NULL;
   5545 }


--1535843080.4BbBbb3.17406
Date: Sat, 1 Sep 2018 23:04:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106838
           Summary: system does not boot up due to ccp (AMD Secure Processor driver) module
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: opensuse_org-at-xibo.at
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

My system is based on an AMD Ryzen 7 2700X cpu on a Gigabyte B450 Aorus Pro
Mainboard.

Booting stops right after entering the password for the encrypted volumes:
..
Please enter passphrase for disk Corsair_Force_3_SSD (cr_sdb3)! ************
[OK] Started Cryptography Setup for cr_sdb3
[OK] Reached target Encrypted Volumes.
[OK] Reached target System Initialization.
[OK] Reached target Basic System.
_

After 480 seconds there is an additional message:
https://cloud.celarek.at/index.php/s/mqxGYbcmyMsgMyL

In the opensuse forum I was told that this is probably the cpp module (AMD
Secure Processor driver). Passing modprobe.blacklist=ccp as a kernel parameter
in grub allowed me to boot again.

This is the forum post:
https://forums.opensuse.org/showthread.php/532902-System-stops-after-quot-Reached-target-Basic-System-quot-on-AMD-Ryzen-7-B450?p=2879087#post2879087


--1535908277.ad4D0.14367
Date: Sun, 2 Sep 2018 17:11:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1106843
           Summary: msgfmt crashes when writing java source code and the .po file has a POT-Creation-Date header
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: gbl-at-guntram.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

$ msgfmt --version
msgfmt (GNU gettext-tools) 0.19.8.1

$ msgfmt --java2 --source -d . -r Messages -l de messages.po
Aborted (core dumped)

The .po file in question is
-------------------------------------------
msgid ""
msgstr ""
"Project-Id-Version: \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-08-30 16:51+0200\n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-1\n"
"Content-Transfer-Encoding: 8bit\n"

#: some/source.java:10
msgid "dog"
msgstr "Hund"
-------------------------------------------

Removing the POT-Creation-Date header from the .po file works around the
problem.

From a first evaluation, it seems like some part of the code removes the
POT-Creation-Date header from the header list while reading the .po file,
without updating the msgstr_len field in the corresponding message struct. This
leads to an abort() in the write_java_msgstr function in write-java.c.