--1525865104.eCEcec70.12041
Date: Wed, 9 May 2018 11:25:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092540
           Summary: VUL-0: CVE-2018-1046: PowerDNS Security Advisory 2018-02
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/205418/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: kbabioch-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-1046

    CVE: CVE-2018-1046
    Date: May 8th 2018
    Credit: Wei Hao
    Affects: dnsreplay from 4.0.0 up to and including 4.1.1
    Not affected: dnsreplay 3.4.11, 4.1.2
    Severity: High
    Impact: Arbitrary code execution
    Exploit: This problem can be triggered via a crafted PCAP file
    Risk of system compromise: Yes
    Solution: Upgrade to a non-affected version

An issue has been found in the dnsreplay tool provided with PowerDNS
Authoritative, where replaying a specially crafted PCAP file can trigger a
stack-based buffer overflow, leading to a crash and potentially arbitrary code
execution. This buffer overflow only occurs when the –ecs-stamp option of
dnsreplay is used. Regardless of this issue, the use of dnsreplay with
untrusted PCAP files is not advised. This issue has been assigned CVE-2018-1046
by Red Hat.

PowerDNS Authoritative from 4.0.0 up to and including 4.1.1 is affected.

We would like to thank Wei Hao for finding and subsequently reporting this
issue.

References:
https://doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2018-02.html
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1046
http://seclists.org/oss-sec/2018/q2/97
https://doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2018-02.html
https://github.com/PowerDNS/pdns/commit/f9c57c98da1b1007a51680629b667d57d9b702b8


body:
--1525865403.fF6F0.3974
Date: Wed, 9 May 2018 11:30:03 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

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

https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:C/xen/standard/x86_64

summary: GCC 8: xen build fails


body:
--1525865505.D6Abc14.5567
Date: Wed, 9 May 2018 11:31:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092544
           Summary: GCC 8: mariadb test fails
    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: martin.liska-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:C:DVD/mariadb/standard/x86_64

summary: GCC 8: mariadb test fails


body:
--1525876785.4E7cfba0.19312
Date: Wed, 9 May 2018 14:39:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092585
           Summary: gem2rpm /etc/os-release handling
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Ruby
          Assignee: ruby-devel-at-suse.de
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

gem2rpm looks for /etc/os-release but according to the spec that file may be
missing and /usr/lib/os-release used instead.

Furthermore it should probably iterate over ID and ID_LIKE to figure out the
template.

summary: gem2rpm /etc/os-release handling


--1525895206.44b7ada50.20357
Date: Wed, 9 May 2018 19:46:46 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092648
           Summary: nVidia drivers should install modprobe configuration under /lib/modprobe.d
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 3rd Party Driver
          Assignee: xorg-maintainer-bugs-at-forge.provo.novell.com
          Reporter: arvidjaar-at-gmail.com
        QA Contact: sndirsch-at-suse.com
          Found By: ---
           Blocker: ---

nvidia drivers depend on modprobe configuration and are explicitly added to
initrd. When creating host-independent ("giant") initrd dracut skips content of
/etc/modprobe.d which is considered "host specific" which results in
non-functional drivers (even though they are loaded in initrd). dracut still
unconditionally includes content of /lib/modprobe.d. See
/usr/lib/dracut/modules.d/90kernel-modules/module-setup.sh, install() function.


--1525900553.10FcAA0.29693
Date: Wed, 9 May 2018 21:15:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092655
           Summary: xfce4-terminal - alt-f<num> does not work for switching tabs
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Xfce
          Assignee: bnc-team-xfce-at-forge.provo.novell.com
          Reporter: bosim-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Upstream bug: https://bugzilla.xfce.org/show_bug.cgi?id=14247

Seems to be fixed upstream in version 0.8.7.1


body:
--1525938838.8D8aB4.15567
Date: Thu, 10 May 2018 07:53:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092697
           Summary: LLVM build fails on armv7l
    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: msrb-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The llvm4/5/6 build fails on armv7l because it is running out of memory. It is
happening during linking of stage1, most likely because of the size of
debuginfo. Stage1 should not be built with debuginfo (it is only used to
compile the next stage), but it got the "-g" parameter accidentally from
%optflags.

summary: LLVM build fails on armv7l


body:
--1525971789.AE4b4.14180
Date: Thu, 10 May 2018 17:03:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092820
           Summary: Unit name rfkill-block@.service is missing the instance name.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: per-at-computer.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Seen during "zypper dup

pkgs: python-libmount util-linux


body:
--1525984227.feB4070.8883
Date: Thu, 10 May 2018 20:30:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092833
           Summary: Opera 53.0.2907.37 maintenance update
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Maintenance
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: sor.alexei-at-meowr.ru
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

An update of Opera from 52.0.2871.30 to 53.0.2907.37 for openSUSE Leap 42.3:
https://blogs.opera.com/desktop/changelog-for-53/

summary: Opera 53.0.2907.37 maintenance update


--1525986290.d141DB4.9962
Date: Thu, 10 May 2018 21:04:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092839
           Summary: brltty hogs USB serial ports without obvious way to disable
    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: afaerber-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: lnussel-at-suse.com
          Found By: ---
           Blocker: ---

On Leap 15.0 certain /dev/ttyUSBx devices are not showing up as expected. For
example, I attach a hub with e.g. two USB UART adapters:

Bus 004 Device 012: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102/CP2109
UART Bridge Controller [CP210x family]
Bus 004 Device 011: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102/CP2109
UART Bridge Controller [CP210x family]

but there's only a /dev/ttyUSB0 and no /dev/ttyUSB1.

This appears to be related to brltty, because "zypper rm brltty" and
re-plugging the hub fixes the issue. However, brltty appears to come back with
the next "zypper dup", so it's no permanent fix. The actual brltty@foo service
instance cannot be stopped either.

The accessibility pane in GNOME Control Center does not appear to offer any
options to disable this behavior. No related YaST module that I can spot
either.

Can we please get sane defaults again like in 42.3 and only activate such
destructive accessibility services when explicitly requested by the user?


body:
--1526023308.c0f80.19148
Date: Fri, 11 May 2018 07:21:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092877
           Summary: zypper dup core dumps
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: libzypp
          Assignee: zypp-maintainers-at-forge.provo.novell.com
          Reporter: marco.varlese-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When running "zypper dup" the program core dumps due to a memory allocation
failure.

The version installation taken from /etc/os-release below:
NAME="openSUSE Tumbleweed"
# VERSION="20180320"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="20180320"
PRETTY_NAME="openSUSE Tumbleweed"

=====/=====

The full BT below:

Loading repository data...
Reading installed packages...
Computing distribution upgrade...
malloc(): memory corruption

Program received signal SIGABRT, Aborted.
0x00007ffff653d9eb in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x00007ffff653d9eb in raise () from /lib64/libc.so.6
#1  0x00007ffff653eda1 in abort () from /lib64/libc.so.6
#2  0x00007ffff6580c87 in __libc_message () from /lib64/libc.so.6
#3  0x00007ffff658729a in malloc_printerr () from /lib64/libc.so.6
#4  0x00007ffff658a30c in _int_malloc () from /lib64/libc.so.6
#5  0x00007ffff658badc in malloc () from /lib64/libc.so.6
#6  0x00007ffff65864a7 in __GI__IO_str_overflow () from /lib64/libc.so.6
#7  0x00007ffff6585504 in __GI__IO_default_xsputn () from /lib64/libc.so.6
#8  0x00007ffff6557a65 in vfprintf () from /lib64/libc.so.6
#9  0x00007ffff6611a38 in __vasprintf_chk () from /lib64/libc.so.6
#10 0x00007ffff7a5165d in zypp::str::form[abi:cxx11](char const*, ...) () from
/usr/lib64/libzypp.so.1702
#11 0x00007ffff7a61417 in
zypp::base::LogControl::LineFormater::format(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&,
zypp::base::logger::LogLevel, char const*, char const*, int,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
const&) () from /usr/lib64/libzypp.so.1702
#12 0x00007ffff7a68641 in ?? () from /usr/lib64/libzypp.so.1702
#13 0x00007ffff6bf257a in std::ostream::put(char) () from
/usr/lib64/libstdc++.so.6
#14 0x00007ffff6bf275f in std::basic_ostream<char, std::char_traits<char> >&
std::endl<char, std::char_traits<char> >(std::basic_ostream<char,
std::char_traits<char> >&) () from /usr/lib64/libstdc++.so.6
#15 0x00007ffff78b5d69 in
zypp::solver::detail::SATResolver::solverInit(std::__cxx11::list<zypp::PoolItem,
std::allocator<zypp::PoolItem> > const&) () from /usr/lib64/libzypp.so.1702
#16 0x00007ffff78b7f26 in
zypp::solver::detail::SATResolver::resolvePool(std::unordered_set<zypp::Capability,
std::hash<zypp::Capability>, std::equal_to<zypp::Capability>,
std::allocator<zypp::Capability> > const&, std::unordered_set<zypp::Capability,
std::hash<zypp::Capability>, std::equal_to<zypp::Capability>,
std::allocator<zypp::Capability> > const&, std::__cxx11::list<zypp::PoolItem,
std::allocator<zypp::PoolItem> > const&, std::set<zypp::Repository,
std::less<zypp::Repository>, std::allocator<zypp::Repository> > const&) () from
/usr/lib64/libzypp.so.1702
#17 0x0000555555670cf5 in solve_and_commit(Zypper&) ()
#18 0x00005555555ccfae in Zypper::doCommand() ()
#19 0x00005555555dedd1 in Zypper::safeDoCommand() ()
#20 0x000055555559e7a5 in Zypper::main(int, char**) ()
#21 0x000055555559dd89 in main ()

summary: zypper dup core dumps


--1526025281.EB21eaF5.27675
Date: Fri, 11 May 2018 07:54:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092881
           Summary: [HPC, scalapack] For non-HPC builds package BLACS headers only once
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: eich-at-suse.com
          Reporter: eich-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: jberry-at-suse.com
          Found By: Development
           Blocker: ---

The BLACs headers are packaged separately for non-HPC builds, the header
package is independent of the flavor. Thus install and build the headers only
once.


--1526042428.5DBdC0.28892
Date: Fri, 11 May 2018 12:40:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092933
           Summary: Version update spec-cleaner to version 1.0.8
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: tchvatal-at-suse.com
        QA Contact: qa-bugs-at-suse.de
        Depends on: 1089297
          Found By: ---
           Blocker: ---

In order to bring latest fixes implemented in spec-cleaner we need to update
version of spec-cleaner on stable products to latest release.

This brings changes since release 1.0.7 which provide quite few interesting
features and fixes as per changelog.


--1526043717.A6F15d0.2086
Date: Fri, 11 May 2018 13:01:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092939
           Summary: Postfixes postconf gives a lot of LDAP related warnings
    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: stefan.schaefer-at-fsproductions.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Postfixes postconf gives a lot of LDAP related warnings:

snip
Mai 11 14:46:00 invis14 postfix[6656]: /usr/sbin/postconf: warning:
ldap:/etc/postfix/r-canonical.cf: unused parameter: bind=yes
Mai 11 14:46:00 invis14 postfix[6656]: /usr/sbin/postconf: warning:
ldap:/etc/postfix/r-canonical.cf: unused parameter: version=3
Mai 11 14:46:00 invis14 postfix[6656]: /usr/sbin/postconf: warning:
ldap:/etc/postfix/r-canonical.cf: unused parameter: bind_dn=ldap.admin@lea>
Mai 11 14:46:00 invis14 postfix[6656]: /usr/sbin/postconf: warning:
ldap:/etc/postfix/r-canonical.cf: unused parameter: server_host=127.0.0.1
Mai 11 14:46:00 invis14 postfix[6656]: /usr/sbin/postconf: warning:
ldap:/etc/postfix/r-canonical.cf: unused parameter: result_attribute=fspLo>
Mai 11 14:46:00 invis14 postfix[6656]: /usr/sbin/postconf: warning:
ldap:/etc/postfix/r-canonical.cf: unused parameter: search_base=cn=Additio>
Mai 11 14:46:00 invis14 postfix[6656]: /usr/sbin/postconf: warning:
ldap:/etc/postfix/ldap-groups.cf: unused parameter: special_result_attribu>
Mai 11 14:46:00 invis14 postfix[6656]: /usr/sbin/postconf: warning:
ldap:/etc/postfix/ldap-groups.cf: unused parameter: query_filter=(&(object>
Mai 11 14:46:00 invis14 postfix[6656]: /usr/sbin/postconf: warning:
ldap:/etc/postfix/ldap-groups.cf: unused parameter: start_tls=yes
snip

Our config works fine under leap 42.3 with postfix 3.2.

Perhaps this could help:
http://postfix.1071664.n5.nabble.com/LDAP-related-quot-postconf-warning-quot-with-most-recent-build-td92435.html

Stefan


--1526049340.d6Ff0.16182
Date: Fri, 11 May 2018 14:35:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092953
           Summary: Include information about new Transactional Server System Role in Release Notes
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Release Notes
          Assignee: sknorr-at-suse.com
          Reporter: rbrown-at-suse.com
        QA Contact: lnussel-at-suse.com
          Found By: ---
           Blocker: ---

The new transactional server role is important enough to justify a mention in
the release notes

It should probably be a summary of the existing documentation that announced
it:

https://kubic.opensuse.org/blog/2018-04-04-transactionalupdates/
Updated: https://kubic.opensuse.org/blog/2018-04-20-transactionalupdates2/


body:
--1526056124.cEe1CA0.12203
Date: Fri, 11 May 2018 16:28:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1092981
           Summary: apr: build failed at armv7l
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: armv7
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: matwey.kornilov-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,

Currently, apr 1.6.2 build is failing at armv7l with the following unit-test
failures:

https://build.opensuse.org/build/openSUSE:Leap:15.0:Ports/ports/armv7l/apr/_log

[  480s] apr_socket_recv() (expected APR_EOF)->70007/The timeout specified has
expired
[  480s] Creating a test file...
[  480s] Sending the file...
[  480s] apr_socket_sendfile() updated offset with 0
[  480s] apr_socket_sendfile() updated len with 370049
[  480s] bytes really sent: 370049
[  480s] After apr_socket_sendfile(), the kernel file pointer is at offset 0.
[  480s] apr_socket_recv() (expected APR_EOF)->104/Connection reset by peer
[  480s] Creating a test file...
[  480s] Sending the file...
[  480s] Calling apr_socket_sendfile()...
[  480s] Headers (3):
[  480s]     15 bytes (1)
[  480s]     5 bytes (E)
[  480s]     80000 bytes (^)
[  480s] File: 200000 bytes from offset 0
[  480s] Trailers (3):
[  480s]     19 bytes
[  480s]     10 bytes
[  480s]     90000 bytes
[  480s] apr_socket_sendfile()->0, sent 370049 bytes
[  480s] After apr_socket_sendfile(), the kernel file pointer is at offset 0.
[  482s] Creating a test file...
[  482s] Sending the file...
[  482s] Calling apr_socket_sendfile()...
[  482s] Headers (3):
[  482s]     15 bytes (1)
[  482s]     5 bytes (E)
[  482s]     80000 bytes (^)
[  482s] File: 200000 bytes from offset 0
[  482s] Trailers (3):
[  482s]     19 bytes
[  482s]     10 bytes
[  482s]     90000 bytes
[  482s] apr_socket_sendfile()->0, sent 370049 bytes
[  482s] After apr_socket_sendfile(), the kernel file pointer is at offset 0.
[  482s] client: apr_socket_sendfile() worked as expected!
[  482s] Waiting for a client to connect...
[  482s] Processing a client...
[  482s] server: apr_socket_sendfile() worked as expected!
[  482s] Programs failed: 'sendfile mode blocking' 'sendfile mode nonblocking'

Unfortunately, apr is a package with 57 direct dependencies.
Fortunately, two fixes were introduced in apr 1.6.3 and armv7l build is known
working for 1.6.3. Updated apr package is in the devel project Apache now and
it also has been sent to openSUSE:Factory:

https://build.opensuse.org/request/show/606135
https://build.opensuse.org/request/show/606113

Unfortunately, apr in openSUSE:Leap:15.0 come from SLES and I can not just
submit request there.
I suggest to pick this minor version update to SLES and then to Leap 15.0 in
order to fix armv7l port build.

summary: apr: build failed at armv7l


body:
Build Identifier:

gajim breaks in the newest release

Reproducible: Always

Steps to Reproduce:
1. open gajim in terminal of your choice
Actual Results:
~# gajim

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

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/gajim", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3147,
in <module>
    @_call_aside
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3131,
in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3160,
in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 668,
in _build_master
    return cls._build_from_requirements(__requires__)
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 681,
in _build_from_requirements
    dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 870,
in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'nbxmpp>=0.6.5' distribution was not
found and is required by gajim

Expected Results:
gajim should open w/o errors :)

Information for package gajim:
------------------------------
Repository     : 15.0-oss
Name           : gajim
Version        : 1.0.2-lp150.1.1
Arch           : noarch
Vendor         : openSUSE
Installed Size : 11.3 MiB
Installed      : Yes
Status         : up-to-date
Source package : gajim-1.0.2-lp150.1.1.src
Summary        : XMPP client written in Python and Gtk3

Information for package python3-nbxmpp:
---------------------------------------
Repository     : 15.0-oss
Name           : python3-nbxmpp
Version        : 0.6.4-lp150.1.2
Arch           : noarch
Vendor         : openSUSE
Installed Size : 833.3 KiB
Installed      : Yes (automatically)
Status         : up-to-date
Source package : python-nbxmpp-0.6.4-lp150.1.2.src
Summary        : XMPP library by Gajim team

summary: nbxmpp has wrong version 0.6.4 not 0.6.5 and causes gajim to crash at startup


--1526084333.6Af64B0.7465
Date: Sat, 12 May 2018 00:18:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.novell.com/show_bug.cgi?id=1093019

            Bug ID: 1093019
           Summary: korganizer crashes loading data from CalDAV source with RELATED-TO pointing to a non-existent element
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: eduard-at-rysavy.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 769976
  --> http://bugzilla.novell.com/attachment.cgi?id=769976&action=edit
korganizer crash debug output

korganizer crashes on startup after loading data from a CalDAV resource with at
least one element having a "RELATED-TO:" attribute pointing to an element not
included in the data.

Cf. attached debug output.

In incidencetreemodel.cpp -> sortedPrenodes:
if (parentUid.isEmpty()) {
...
} else {
    if (prenodeByUid.contains(parentUid)) {
     ...
    }
    --> else branch is missing!
}

The problem seems to be caused by:
if (prenodeByUid.contains(parentUid)) is false, node->depth is undefined, and
std::sort(sorted.begin(), sorted.end(), greaterThan) crashes in greaterThan

After removing the Attribute - in my case: "RELATED-TO:libkcal-786590685.242" -
and restarting akonadi (to resync) korganizer starts normally.


--1526092114.60220.8437
Date: Sat, 12 May 2018 02:28:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093020
           Summary: Enable ChaCha20/Poly1305 support in strongswan
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: et-at-pithyphrase.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The version of Strongswan currently shipped with Tumbleweed (5.6.0) supports
ChaCha20/Poly1305 but the RPM spec doesn't enable that support.

I was able to enable this support in a locally built RPM with these changes to
the spec file:

304a305,306
>       --enable-chapoly \
>       --enable-ntru \
621a624,626
> %config(noreplace) %attr(600,root,root) %{strongswan_configs}/charon/chapoly.conf
> %config(noreplace) %attr(600,root,root) %{strongswan_configs}/charon/mgf1.conf
> %config(noreplace) %attr(600,root,root) %{strongswan_configs}/charon/ntru.conf
823a829,831
> %{strongswan_plugins}/libstrongswan-chapoly.so
> %{strongswan_plugins}/libstrongswan-mgf1.so
> %{strongswan_plugins}/libstrongswan-ntru.so
925a934,936
> %{strongswan_templates}/config/plugins/chapoly.conf
> %{strongswan_templates}/config/plugins/mgf1.conf
> %{strongswan_templates}/config/plugins/ntru.conf


--1526103316.0c7420.15371
Date: Sat, 12 May 2018 05:35:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093021
           Summary: Suse, KDE icon (left bottom) - games and multimedia - content is not shown correctly
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: x86-64
                OS: SUSE Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: armin.mohring-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

KDE / Suse Icon on taskbar - games and multimedia folder content is not shown
correctly.
If I move from games to multimedia, then the content of multimedia is the same
as content of games.
If I move from education to multimedia, then the content of multimedia is
correctly shown (k3B, vlc and dragon player)


--1526117514.aeA30.26193
Date: Sat, 12 May 2018 09:31:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093025
           Summary: php7 session.safe_path has wrong permissions
    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: stefan.schaefer-at-fsproductions.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The webserver has no write permissions in /var/lib/php7. PHP-Sessiondata could
not be written to this directory:

wrong:
drwxr-xr-x  2 root        root        4096  7. Mai 18:21 php7

works:
drwxrwxr-x  2 root        www        4096  7. Mai 18:21 php7

Stefan


--1526118256.381fea24.26973
Date: Sat, 12 May 2018 09:44:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093027
           Summary: The SB live 5.1 card lost Analog output in Leap 15.0
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: hillwoodroc-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 769977
  --> http://bugzilla.opensuse.org/attachment.cgi?id=769977&action=edit
output list in Leap 15.0

This sound card works fine in Leap 42.3 and Tumbleweed. But there is not any
Analog output option in output list for SB live 5.1 (EMU10K1).


--1526129962.01aDa3A81.25237
Date: Sat, 12 May 2018 12:59:22 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093029
           Summary: [Build 20180511] openQA test fails in yast2_dns_server - "named.service is not active, cannot reload."
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/674858/modules/yast2
                    _dns_server/steps/44
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: okurz-at-suse.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

## Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ncurses@64bit
fails in
[yast2_dns_server](https://openqa.opensuse.org/tests/674858/modules/yast2_dns_server/steps/44)
because the "named" service is not active after the yast configuration part
exits.

Error output from y2log:

```
2018-05-12 04:07:39 <1> susetest(24233) [Ruby] yast2/systemctl.rb:32 systemctl
show named.service  --property=Id  --property=MainPID  --property=Description
--property=LoadState  --property=ActiveState  --property=SubState
--property=UnitFileState  --property=FragmentPath
2018-05-12 04:07:39 <1> susetest(24233) [Ruby] yast2/systemctl.rb:32 systemctl
reload named.service
2018-05-12 04:07:39 <3> susetest(24233) [bash] ShellCommand.cc(shellcommand):78
named.service is not active, cannot reload.
```

## Reproducible

Failed already two times in the snapshot in before the "last good", 20180508. I
assume it is sporadic.

## Expected result

The service should be running at the time of exiting the yast configuration
part as was the case in before

Last good: Build
[20180510](https://openqa.opensuse.org/tests/674165#step/yast2_dns_server/10)

### Problem

Could be that the service would actually be running after some waiting time. I
will see what we can do to improve the investigation in the test itself to find
out more information.

## Further details

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


--1526204978.61Fee3.29429
Date: Sun, 13 May 2018 09:49:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093035
           Summary: ideapad_laptop prevents wireless from working on Lenovo Ideapad MIIX 720-12IKB
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: i686
                OS: openSUSE 42.3
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: robin.roevens1-at-pandora.be
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 769988
  --> http://bugzilla.opensuse.org/attachment.cgi?id=769988&action=edit
Added Lenovo Ideapad MIIX 720-12IKB to no_hw_rfkill_list

Booting openSUSE on a Lenovo Ideapad MIIX 720-12IKB results in wireless being
reported as hardware-blocked by rfkill. This seems to be caused by the
ideapad_laptop module and is fixed by blacklisting the module.
However other ideapad_laptop features are then also lost. When adding the
vendor and product version into the no_hw_rfkill_list of the module, wireless
is no longer hardware blocked.
See attached patch.


--1526278439.7E8cAC560.4494
Date: Mon, 14 May 2018 06:13:59 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093056
           Summary: VUL-0: CVE-2018-10992: lilypond: Does not validate strings before launching the program specified by the BROWSER environment variable, which allows remote attackers to conduct argument-injection attacks
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/205725/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: davejplater-at-gmail.com
          Reporter: jsegitz-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-10992

lilypond-invoke-editor in LilyPond 2.19.80 does not validate strings before
launching the program specified by the BROWSER environment variable, which
allows remote attackers to conduct argument-injection attacks via a crafted
URL,
as demonstrated by a --proxy-pac-file argument, because the GNU Guile code uses
the system Scheme procedure instead of the system* Scheme procedure. NOTE: this
vulnerability exists because of an incomplete fix for CVE-2017-17523.

We don't have the fix for CVE-2017-17523 yes, so we're technically not
affected. Please take this as information on how to fix CVE-2017-17523
properly.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-10992
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898373


--1526279494.2Ccf1.2759
Date: Mon, 14 May 2018 06:31:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093059
           Summary: [Build 20180508] openQA test fails in firefox - firefox "dumped core"
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
               URL: https://openqa.opensuse.org/tests/674991/modules/firef
                    ox/steps/6
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Firefox
          Assignee: bnc-team-mozilla-at-forge.provo.novell.com
          Reporter: okurz-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: Yes

## Observation

openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-xfce@aarch64 fails in
[firefox](https://openqa.opensuse.org/tests/674991/modules/firefox/steps/6)
with firefox crashing. A core dump is available. See the logs archive in
https://openqa.opensuse.org/tests/674991/file/firefox-problem_detection_logs.tar.xz
contaning log files and the core dump.

There is also a core dump for "login" which should rather be handled in
https://bugzilla.opensuse.org/show_bug.cgi?id=1091349

## Reproducible

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

## Expected result

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

## Further details

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


--1526289148.4Dc05.11840
Date: Mon, 14 May 2018 09:12:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093088
           Summary: prosody 0.9.13 maintenance release available
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: mvetter-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Has some important fixes in it.
Needs to go to Leap 42.3.


body:
--1526292186.B7c2AA00.25208
Date: Mon, 14 May 2018 10:03:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093098
           Summary: document minimum disk size
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Release Notes
          Assignee: sknorr-at-suse.com
          Reporter: lnussel-at-suse.com
        QA Contact: lnussel-at-suse.com
                CC: ancor-at-suse.com
          Found By: ---
           Blocker: ---

The installer will only propose a partitioning scheme if the available hard
disk size is larger than 12GB. Administrators wanting to install e.g. very
small virtual machines images will have to use the guided setup to tune the
parameters for the partitioning manually.

summary: document minimum disk size


--1526312138.1B1A74.11512
Date: Mon, 14 May 2018 15:35:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093163
           Summary: mdadm: using service templates in preun is wrong:
    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: ro-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

in mdadm.spec:
%preun
%service_del_preun %services mdmon@.service mdadm-last-resort@.service
mdadm-grow-continue@.service

leads to:
# rpm -e mdadm --nodeps
Failed to stop mdmon@.service: Unit name mdmon@.service is missing the instance
name.
See system logs and 'systemctl status mdmon@.service' for details.
Failed to stop mdadm-last-resort@.service: Unit name mdadm-last-resort@.service
is missing the instance name.
See system logs and 'systemctl status mdadm-last-resort@.service' for details.
Failed to stop mdadm-grow-continue@.service: Unit name
mdadm-grow-continue@.service is missing the instance name.
See system logs and 'systemctl status mdadm-grow-continue@.service' for
details.
Failed to get load state of mdmon@.service: Unit name mdmon@.service is neither
a valid invocation ID nor unit name.
Failed to get load state of mdadm-last-resort@.service: Unit name
mdadm-last-resort@.service is neither a valid invocation ID nor unit name.
Failed to get load state of mdadm-grow-continue@.service: Unit name
mdadm-grow-continue@.service is neither a valid invocation ID nor unit name.

a service template file (foo@.service) can not be used with the
%service_add/del macros.


--1526312270.20bBCF4.11498
Date: Mon, 14 May 2018 15:37:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093165
           Summary: csync2 using service template csync2@.service in preun
    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: ro-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

%preun
%service_del_preun csync2.socket csync2@.service

# rpm -e csync2
Failed to stop csync2@.service: Unit name csync2@.service is missing the
instance name.
See system logs and 'systemctl status csync2@.service' for details.
Failed to get load state of csync2@.service: Unit name csync2@.service is
neither a valid invocation ID nor unit name.

service templates can not be used with the %service_add/del macros.


--1526312970.cbA5b8811.14413
Date: Mon, 14 May 2018 15:49:30 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093169
           Summary: qemu guest-agent using systemd service template in pre/preun/post/postun
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KVM
          Assignee: kvm-bugs-at-forge.provo.novell.com
          Reporter: ro-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

a service template (foo@.service) can only be used with a parameter
on the commandline but will not work in the specfile without the parameter.

%service_add_pre qemu-ga@.service
%service_del_preun qemu-ga@.service
%service_add_post qemu-ga@.service
%service_del_postun qemu-ga@.service

(1/1) Removing qemu-guest-agent-2.11.1-4.6.x86_64
........................[done]
Additional rpm output:
Failed to stop qemu-ga@.service: Unit name qemu-ga@.service is missing the
instance name.
See system logs and 'systemctl status qemu-ga@.service' for details.
Failed to get load state of qemu-ga@.service: Unit name qemu-ga@.service is
neither a valid invocation ID nor unit name.


--1526313660.eE3beF4.16693
Date: Mon, 14 May 2018 16:01:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093170
           Summary: rdma-core srp_daemon using service template file in pre/postun
    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: ro-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

%service_add_pre srp_daemon.service srp_daemon_port@.service
%service_add_post srp_daemon.service srp_daemon_port@.service
%service_del_postun -n  srp_daemon_port@.service
%service_del_postun -n  srp_daemon_port@.service

a service template (foo@.service) can only be used with a parameter
on the commandline but will not work in the specfile without the parameter.


body:
--1526315132.fa4d874.20230
Date: Mon, 14 May 2018 16:25:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093176
           Summary: util-linux using service template file in pre/postun
    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: ro-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

%service_add_pre raw.service rfkill-block@.service rfkill-unblock@.service
%service_add_post raw.service rfkill-block@.service rfkill-unblock@.service
%service_del_preun raw.service rfkill-block@.service rfkill-unblock@.service
%service_del_postun raw.service rfkill-block@.service rfkill-unblock@.service

a service template (foo@.service) can only be used with a parameter
on the commandline but will not work in the specfile without the parameter.

see also
https://discourse.nordisch.org/t/hooking-up-instantiated-services-with-rpm/476


--1526397152.Dc3f6C535.15992
Date: Tue, 15 May 2018 15:12:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093378
           Summary: conflicting udev rules completely break USB Serial bridges
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: sbrabec-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: jreuter-at-suse.com, kkaempf-at-suse.com,
                    matwey.kornilov-at-gmail.com, mbrugger-at-suse.com,
                    mgorse-at-suse.com, oneukum-at-suse.com, ro-at-suse.com,
                    sckang-at-suse.com, sndirsch-at-suse.de,
                    stefan.bruens@rwth-aachen.de, trenn-at-suse.com
        Depends on: 1092839, 1007652
          Found By: ---
           Blocker: ---

Following USB ids represent most common generic USB UART Bridges:

10C4:EA60 CP210x UART Bridge
https://usb-ids.gowdy.us/read/UD/10c4/ea60

10C4:EA80 CP2110 HID UART Bridge
https://usb-ids.gowdy.us/read/UD/10c4/ea80

0403:6001 FT232 USB-Serial (UART) IC
https://usb-ids.gowdy.us/read/UD/0403/6001

(There are more such chips and ids)

Many hardware vendors ignore rules and sell their products with this generic
USB ids.

As as result, plugging of such device starts an udev rule fight, which actually
ends by a completely non-functional device.

Actually, these applications fight for these devices:

brttty: Recognizes it as a Braille terminal or display (bug 1092839)
upower: Recognizes it as a Watts Up? Pro
gpsd: Recognizes it as SiRF Star III 20ch Gmouse GPS (or another GPS device for
other ids)
ModemManager: Recognizes it as a modem candidate
argyllcms: Recognized as JETI & KLEIN Spectrophotometer (bug 1007652, already
fixed)

Other packages that might attempt to steal these ids as well (or at least did
it in past):
avrdude: Recognizes it as a AVR programmer
sigrok: Recognizes it as CEM DT-8852, Dangerous Prototypes Buspirate, ChronoVu
LA8, ChronoVu LA16
openocd: Sets it up as a serial bridge to the embedded device (hopefully, only
privileges are set)

Found by:
grep -ir '\(6001\|ea60\|ea80\)' /usr/lib/udev/rules.d /etc/udev/rules.d

If hardware vendors ignore rules and release a device with a USB UART Bridge id
and textual identification, Linux has no chance to recognize the device
plugged.


--1526401243.8da4e8aa3.28222
Date: Tue, 15 May 2018 16:20:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093389
           Summary: Bug in Lenovo wireless keyboards detection (HID) based on Primax Electronics
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: OES - Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: 4sg-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 770312
  --> http://bugzilla.opensuse.org/attachment.cgi?id=770312&action=edit
Patch that fixes the problem on kernel-4.4.126_48_default (openSUSE 42.3)

OS/kernel is unable to operate Lenovo wireless keyboards based on Primax
Electronics chips. The reason is likely that HID information communicated by
the chip is misinterpreted by the kernel (hid-core module).

The issue is extensively discussed at:
https://forums.lenovo.com/t5/Linux-Discussion/Professional-Wireless-Keyboard-not-working-on-Linux/td-p/3726486
https://askubuntu.com/questions/897729/lenovo-professional-wireless-keyboard-and-mouse-combo-not-working-in-ubuntu
and diagnosed/patched at:
https://unix.stackexchange.com/a/377873/239474

Reproducible: Always

Steps to Reproduce:
1. Install openSUSE 42.3
2. Plug in Lenovo Wireless Professional keyboard (e.g. https://lnv.gy/2ImwNuh ,
with optional Mouse)

Actual Results:
Typing does not have any effect except for Win and volume control buttons.
Optional mouse works, that is, the USB dongle/receiver work, however the
regular keys are not processed by the system/kernel. A VM running, e.g.,
Windows on the same machine works with this keyboard as expected.

Expected Results:
User was told what this hardware works with any AT-compatible PC with USB. In
linux, the hardware does not function properly.

Solutions found:
There is a patch available at
https://unix.stackexchange.com/a/377873/239474
which fixes the issue on openSUSE 42.3 (tested on kernels 4.4.126-48-default
and 4.4.120-45-default, openSUSE 42.3). Patching every kernel update works, but
as such is a great nuisance. Applying this patch upstream would be nice.


--1526402953.2FfEF1.32126
Date: Tue, 15 May 2018 16:49:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093392
           Summary: yast2 timezone does not change /etc/sysconfig/clock correctly
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: P.Suetterlin-at-royac.iac.es
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

I just came home 1 hour early - the clock on my computer had been wrong.

I work in two timezones, summer in Atlantic/Canary and winter in
Europe/Stockholm.  When I switch, I adjust the timezone using 'yast2 timezone'.
I did this April 1.

Today, after updating Tumbleweed (20180502->20180513) my timezone had been
changed back to Stockholm (which I did not notice, and leave early....).

It turned out that /etc/sysconfig/clock contains
TIMEZONE="Europe/Stockholm"
DEFAULT_TIMEZONE="US/Eastern"

and obviously some setup (likely from the timezone package, though there was
nothing reported in the zypper log) used this to set the timezone and change
the link /etc/localtime->/usr/share/zoneinfo/Europe/Stockholm

So I just changed the timezone back using yast, and after that /etc/localtime
correctly points to /usr/share/zoneinfo/Atlantic/Canary again, and I have the
correct time.

However, /etc/sysconfig/clock still contains TIMEZONE="Europe/Stockholm",
although it does have the timestamp when I called yast to change the TZ.
Yast seems to have written the wrong (old) information to the file.

It must be an older bug already (at least since April 1)


body:
Build Identifier:

an email on opensuse-factory:

Hi,

There is two itens in the release notes that conflict itselves:

* Use update-alternatives to Set Login Manager and Desktop Session

this item states that /etc/sysconfig editor doesn't work anymore to
change the login manager and tell us to use update-alternatives

* No Screen Lock When Using GNOME Shell But Not GDM

this item tell us to change the login manager using /etc/sysconfig editor...

Regards,

Luiz

Reproducible: Always

summary: 2 conflict items in release notes with /etc/sysconfig


--1526471655.7Bf4Fe0.7708
Date: Wed, 16 May 2018 11:54:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093501
           Summary: Cloud:Tools/cloud-init: Bug ds-identify: fails to recognize NoCloud datasource on boot cause it does not have /sbin in $PATH and thus does not find blkid
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: jdsn-at-suse.com
          Reporter: martin.steigerwald-at-teamix.de
        QA Contact: bnc-team-screening-at-forge.provo.novell.com
                CC: rjschwei-at-suse.com
          Found By: ---
           Blocker: ---

Please see upstream bug report for all the details on this:

ds-identify: fails to recognize NoCloud datasource on boot cause it does not
have /sbin in $PATH and thus does not find blkid
https://bugs.launchpad.net/cloud-init/+bug/1771382

Minimal patch to fix the issue:

slestemplate:~ # diff -u ds-identify.orig /usr/lib/cloud-init/ds-identify
-


--1526511804.7bBDeFbc3.22583
Date: Wed, 16 May 2018 23:03:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093604
           Summary: monitor refresh rate is set by driver at lowest value
    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: otosaxel-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

system uses intel UHD620 graphics i5 8250 + bumblebee nvidia 130mx

refresh rate of monitor is always set on lowest value in system settings ->
display and monitor. which is 48hz.

glxgears confirms it.

glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
243 frames in 5.0 seconds = 48.436 FPS
240 frames in 5.0 seconds = 47.998 FPS
240 frames in 5.0 seconds = 47.999 FPS

but xrand shows correct value:
 xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis)
340mm x 190mm
   1920x1080     60.00*+  59.93    48.00
   1680x1050     59.88
   1400x1050     59.98
   1600x900      60.00    59.95    59.82
   1280x1024     60.02
   1400x900      59.96    59.88
   1280x960      60.00
   1368x768      60.00    59.88    59.85
   1280x800      59.81    59.91
   1280x720      59.86    60.00    59.74
   1024x768      60.00
   1024x576      60.00    59.90    59.82
   960x540       60.00    59.63    59.82
   800x600       60.32    56.25
   864x486       60.00    59.92    59.57
   640x480       59.94
   720x405       59.51    60.00    58.99
   640x360       59.84    59.32    60.00
HDMI1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

similar problem I found in arch forums:
https://bbs.archlinux.org/viewtopic.php?id=232354

setting by hand to 59.93 gives this result:

glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
305 frames in 5.0 seconds = 60.886 FPS
298 frames in 5.0 seconds = 59.593 FPS
300 frames in 5.0 seconds = 59.997 FPS


--1526540019.BBb5ce0a0.10458
Date: Thu, 17 May 2018 06:53:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093625
           Summary: biosdevname crashes due to infitie recursion in smbios_setslot
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: trenn-at-suse.com
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 770539
  --> http://bugzilla.suse.com/attachment.cgi?id=770539&action=edit
lspci -vvvxxnn

> #0  0x00007ffff788ebbe in _int_malloc (av=av@entry=0x7ffff7bc4c40 <main_arena>, bytes=bytes@entry=6) at malloc.c:3557
> #1  0x00007ffff7890adc in __GI___libc_malloc (bytes=6) at malloc.c:3057
> #2  0x00007ffff78943da in __GI___strdup (s=s@entry=0x55555575fb45 "Slot2") at strdup.c:42
> #3  0x0000555555559a37 in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=-1, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2")
>     at src/dmidecode/dmidecode.c:150
> #4  0x0000555555559afb in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=-1, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2")
>     at src/dmidecode/dmidecode.c:157
> #5  0x0000555555559afb in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=-1, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2")
>     at src/dmidecode/dmidecode.c:157
> #6  0x0000555555559afb in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=-1, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2")
>     at src/dmidecode/dmidecode.c:157
> #7  0x0000555555559afb in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=-1, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2")
>     at src/dmidecode/dmidecode.c:157
> #8  0x0000555555559afb in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=-1, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2")
>     at src/dmidecode/dmidecode.c:157
> #9  0x0000555555559afb in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=-1, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2")
>     at src/dmidecode/dmidecode.c:157
> #10 0x0000555555559afb in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=-1, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2")
>     at src/dmidecode/dmidecode.c:157
> #11 0x0000555555559afb in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=-1, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2")
>     at src/dmidecode/dmidecode.c:157
> #12 0x0000555555559afb in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=-1, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2")
>     at src/dmidecode/dmidecode.c:157
> #13 0x0000555555559afb in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=-1, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2")

...
> #1558 0x0000555555559afb in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=-1, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2") at src/dmidecode/dmidecode.c:157
> #1559 0x0000555555559afb in smbios_setslot (state=0x55555575d260, domain=0, bus=0, device=28, func=-1, type=0, slot=1, index=0, label=0x55555575fb45 "Slot2") at src/dmidecode/dmidecode.c:157
> #1560 0x0000555555559e65 in dmi_decode (ver=<optimized out>, state=0x55555575d260, h=0x7fffffffdb60) at src/dmidecode/dmidecode.c:179
> #1561 dmi_table (base=<optimized out>, len=6183, num=<optimized out>, ver=<optimized out>, devmem=devmem@entry=0x55555555a8f4 "/dev/mem", state=state@entry=0x55555575d260) at src/dmidecode/dmidecode.c:277
> #1562 0x0000555555559eea in smbios_decode (buf=0x55555575f6f0 "_SM_\333\037\003", devmem=0x55555555a8f4 "/dev/mem", state=0x55555575d260) at src/dmidecode/dmidecode.c:292
> #1563 0x000055555555a046 in dmidecode_main (state=state@entry=0x55555575d260) at src/dmidecode/dmidecode.c:437
> #1564 0x000055555555813b in get_pci_devices (state=state@entry=0x55555575d260) at src/pci.c:716
> #1565 0x00005555555564f0 in setup_bios_devices (namingpolicy=0, prefix=0x55555555a8fa "em") at src/bios_device.c:370
> #1566 0x0000555555555c99 in main (argc=<optimized out>, argv=<optimized out>) at src/bios_dev_name.c:205

Device 28 is 1c which is:
> 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1) (prog-if 00 [Normal decode])
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>         Latency: 0
>         Interrupt: pin A routed to IRQ 122
>         Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
>         I/O behind bridge: None
>         Memory behind bridge: ec200000-ec2fffff [size=1M]
>         Prefetchable memory behind bridge: None
>         Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
>         BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
>                 PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
>         Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
>                 DevCap: MaxPayload 256 bytes, PhantFunc 0
>                         ExtTag- RBE+
>                 DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
>                         RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
>                         MaxPayload 256 bytes, MaxReadReq 128 bytes
>                 DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
>                 LnkCap: Port #1, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <16us
>                         ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
>                 LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+
>                         ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
>                 LnkSta: Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
>                 SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
>                         Slot #4, PowerLimit 10.000W; Interlock- NoCompl+
>                 SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
>                         Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
>                 SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
>                         Changed: MRL- PresDet+ LinkState+
>                 RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
>                 RootCap: CRSVisible-
>                 RootSta: PME ReqID 0000, PMEStatus- PMEPending-
>                 DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd+
>                          AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
>                 DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd-
>                          AtomicOpsCtl: ReqEn- EgressBlck-
>                 LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
>                          Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
>                          Compliance De-emphasis: -6dB
>                 LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
>                          EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
>         Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
>                 Address: fee00278  Data: 0000
>         Capabilities: [90] Subsystem: Dell Device [1028:079f]
>         Capabilities: [a0] Power Management version 3
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
>                 Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>         Capabilities: [100 v1] Advanced Error Reporting
>                 UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
>                 UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
>                 UESvrt: DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
>                 CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
>                 CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
>                 AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
>                         MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
>                 HeaderLog: 00000000 00000000 00000000 00000000
>                 RootCmd: CERptEn- NFERptEn- FERptEn-
>                 RootSta: CERcvd- MultCERcvd- UERcvd- MultUERcvd-
>                          FirstFatal- NonFatalMsg- FatalMsg- IntMsg 0
>                 ErrorSrc: ERR_COR: 0000 ERR_FATAL/NONFATAL: 0000
>         Capabilities: [140 v1] Access Control Services
>                 ACSCap: SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd- EgressCtrl- DirectTrans-
>                 ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
>         Capabilities: [200 v1] L1 PM Substates
>                 L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
>                           PortCommonModeRestoreTime=40us PortTPowerOnTime=44us
>                 L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
>                            T_CommonMode=60us LTR1.2_Threshold=163840ns
>                 L1SubCtl2: T_PwrOn=60us
>         Capabilities: [220 v1] #19
>         Kernel driver in use: pcieport
>         Kernel modules: shpchp


body:
--1526551015.62fFE0.21286
Date: Thu, 17 May 2018 09:56:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093665
           Summary: psmisc: Incorrect mountinfo parser
    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: martin.koegler-at-brz.gv.at
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

You just need to run "mount --make-private <mount point>". "fuser -m
<mount-point>" will fail.

mountinfo file format according to the kernel documentation:

=========================
This file contains lines of the form:

36 35 98:0 /mnt1 /mnt2 rw,noatime master:1 - ext3 /dev/root rw,errors=continue
(1)(2)(3)   (4)   (5)      (6)      (7)   (8) (9)   (10)         (11)

(1) mount ID:  unique identifier of the mount (may be reused after umount)
(2) parent ID:  ID of parent (or of self for the top of the mount tree)
(3) major:minor:  value of st_dev for files on filesystem
(4) root:  root of the mount within the filesystem
(5) mount point:  mount point relative to the process's root
(6) mount options:  per mount options
(7) optional fields:  zero or more fields of the form "tag[:value]"
(8) separator:  marks the end of the optional fields
(9) filesystem type:  name of filesystem of the form "type[.subtype]"
(10) mount source:  filesystem specific information or "none"
(11) super options:  per super block options
=========================

In fuser.c init_mntinfo, the parsing breaks, if there is not exactly one field
( (7  - option fields) :
        while (fscanf
               (mnt, "%i %i %u:%u %*s %s %*s %*s - %s %*[^\n]",
                &mid, &parid, &maj, &min, &mpoint[0], &type[0]) == 6)

The kernel formating code is (proc_namespace.c):
    /* Tagged fields ("foo:X" or "bar") */
    if (IS_MNT_SHARED(r))
        seq_printf(m, " shared:%i", r->mnt_group_id);
    if (IS_MNT_SLAVE(r)) {
        int master = r->mnt_master->mnt_group_id;
        int dom = get_dominating_id(r, &p->root);
        seq_printf(m, " master:%i", master);
        if (dom && dom != master)
            seq_printf(m, " propagate_from:%i", dom);
    }
    if (IS_MNT_UNBINDABLE(r))
        seq_puts(m, " unbindable");

This not working parser code is added by
0001-Use-mountinfo-to-be-able-to-use-the-mount-identity.patch from
werner-at-suse.de.

summary: psmisc: Incorrect mountinfo parser


body:
--1526551900.EBCeC6bE5.26391
Date: Thu, 17 May 2018 10:11:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093671
           Summary: Update prosody 0.10.1 for Leap 15.0
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: mvetter-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

prosody 0.10.1 has some nice fixes.
Would be good to have them in Leap 15.0.

summary: Update prosody 0.10.1 for Leap 15.0


--1526562253.1fFf2.21200
Date: Thu, 17 May 2018 13:04:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093707
           Summary: devel:tools:compiler/llvm6: duplicate binaries produced with llvm5 and  llvm4
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: msrb-at-suse.com
          Reporter: jberry-at-suse.com
        QA Contact: bnc-team-screening-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

libFuzzer:
  - llvm4
  - llvm5
  libc++-devel:
  - llvm4
  - llvm5
  - llvm6
  libc++1:
  - llvm4
  - llvm5
  - llvm6
  libc++abi-devel:
  - llvm4
  - llvm5
  - llvm6
  libc++abi1:
  - llvm4
  - llvm5
  - llvm6
  python3-clang:
  - llvm4
  - llvm5
  - llvm6

See dashboard/duplicate_binaries which is updated once daily:
https://build.opensuse.org/package/view_file/openSUSE:Factory:Staging/dashboard/duplicate_binaries.

It would seem the primary version of llvm should produce them and/or
suffix/prefix with llvm version and use provides/conflicts to the current
names. In that case it may require prefer added to project config.

As it currently, stands identical binaries are produced which may have
undefined behavior in OBS in terms of which is used.


body:
--1526568722.5F74AD0.31922
Date: Thu, 17 May 2018 14:52:02 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093731
           Summary: virtualbox fails to build against Qt 5.11
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Other
          Assignee: Larry.Finger-at-gmail.com
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:L:DVD/virtualbox/standard/x86_64

[ 1285s] /usr/include/qt5/QtWidgets/qabstractbutton.h:53:7: note: forward
declaration of 'class QButtonGroup'
[ 1285s]  class QButtonGroup;

Just missing #includes AFAICT.

pkgs: kbuild+virtualbox virtualbox


body:
--1526568793.7AAd7.31922
Date: Thu, 17 May 2018 14:53:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093732
           Summary: vlc fails to build against Qt 5.11
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: dimstar-at-opensuse.org
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:L:DVD/vlc/standard/x86_64

[  292s] gui/qt/components/simple_preferences.cpp:777:47: error: invalid use of
incomplete type 'class QButtonGroup'
[  292s]              radioGroup = new QButtonGroup(this);

summary: vlc fails to build against Qt 5.11


--1526568839.360Fb12.31033
Date: Thu, 17 May 2018 14:53:59 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093733
           Summary: wireshark fails to build against Qt 5.11
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: lszhu-at-suse.com
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:L:DVD/wireshark/standard/x86_64

[  889s] packet_format_group_box.cpp: In constructor
'PacketFormatGroupBox::PacketFormatGroupBox(QWidget*)':
[  889s] packet_format_group_box.cpp:21:18: error: aggregate 'QStyleOption
style_opt' has incomplete type and cannot be defined
[  889s]      QStyleOption style_opt;

Missing #includes.


--1526574593.eD17c0.31598
Date: Thu, 17 May 2018 16:29:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093743
           Summary: Missing Italian Translation in KDE Plasma5 Software Updates Applet for PackageKit
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: aloisio-at-gmx.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Also missing in 42.3


--1526586684.C5ad5.6955
Date: Thu, 17 May 2018 19:51:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093767
           Summary: Mozilla Firefox 60 ESR upstream regression fixes in 60.0.1 ESR
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Firefox
          Assignee: bnc-team-mozilla-at-forge.provo.novell.com
          Reporter: astieger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: pcerny-at-suse.com, wolfgang-at-rosenauer.org
          Found By: Security Response Team
           Blocker: ---

Some upstream regressions is 60.0 ESR are fixed in 60.0.1 ESR

From https://www.mozilla.org/en-US/firefox/60.0.1esr/releasenotes/

* Avoid overly long cycle collector pauses with some add-ons installed
* After unckecking the "Sponsored Stories" option, the New Tab page now
immediately stops displaying "Sponsored content" cards
* On touchscreen devices, fixed momentum scrolling on non-zoomable pages
* Restored translations of the Preferences panels when using a language pack

Submitted for Leap 15.0 in https://build.opensuse.org/request/show/610154


body:
Build Identifier:

Leap 42.3 comes with gpg2-2.0, while Leap 15.0 upgrades that to gpg2-2.2. This
incurs an incompatible change of the database used for storing the secret keys.
Users ought to be informed about this change because it may result in
data/e-mails which can no longer be decrypted. For details see
<http://bugzilla.suse.com/show_bug.cgi?id=1093836>

Reproducible: Always

Steps to Reproduce:
1. Use a shared $HOME/.gnupg directory for your installation(s)
2. Use it on Leap 42.3 or even before
3. Use it on Leap 15.0, then switch back (i.e. reboot) to Leap 42.3
Actual Results:
Using enigmail >= 2.0 makes it impossible to decrypt e-mails which could be
decrypted before.

Expected Results:
Anything encrypted using your own private GPG key ought to be decryptable using
later versions of gpg2.

It might help to use a distinct directory for ~/.gnupg on every different OS
you're using, but this contradicts the expectation to spread copies of the
private key to as least copies as possible/necessary.

summary: Upgrade from Leap 42.3 changes the secret keys format for GPG keys


body:
--1526808368.FbDb00.6472
Date: Sun, 20 May 2018 09:26:08 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093988
           Summary: gcompris-qt 0.91 bug fix has been release
    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: bruno@ioda-net.ch
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

To ensure the best experience to all users, gcompris-qt 0.91 should be
integrated in Leap 15.0 (replacing the previous 0.90 version)

pkgs: gcompris-qt gcompris-qt-voices


--1526808483.b4542e230.6825
Date: Sun, 20 May 2018 09:28:03 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1093989
           Summary: gcompris-qt 0.91 bug fix has been release
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: bruno@ioda-net.ch
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

gcompris-qt has now release bugfix version 0.9.1 which sould be offered to all
end users as update.


body:
--1526893160.6D5eC175.25221
Date: Mon, 21 May 2018 08:59:20 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1094025
           Summary: Make LXQt pattern XFCE independant
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LXDE
          Assignee: andrea-at-opensuse.org
          Reporter: mvetter-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Currently the LXQt pattern requires xfce4-power-manager and
xfce4-screenshooter.
Both are not needed as we have lxqt-powermanagement and lximage-qt covers the
screenshot capability. It does this via the -s option. It also has comes with a
desktop file to have this easily available.

SR#610746 is changing this for TW.

I think it would be good to have this also in 15.0 not to pull in unneeded
stuff.

summary: Make LXQt pattern XFCE independant


body:
--1526970772.6e555b0.25006
Date: Tue, 22 May 2018 06:32:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1094138
           Summary: VUL-0: CVE-2018-11243: upx: PackLinuxElf64::unpack in p_lx_elf.cpp in UPX 3.95 allows remote attackers to cause a denial of service
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/206156/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Maintenance
          Assignee: meissner-at-suse.com
          Reporter: vpereira-at-microfocus.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-11243

PackLinuxElf64::unpack in p_lx_elf.cpp in UPX 3.95 allows remote attackers to
cause a denial of service (double free), limit the ability of a malware scanner
to operate on the entire original data, or possibly have unspecified other
impact via a crafted file.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-11243
http://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-11243.html
https://github.com/upx/upx/blob/devel/NEWS
https://github.com/upx/upx/issues/206
https://github.com/upx/upx/issues/207

pkgs: ucl upx


body:
--1526971554.dbbe46BD12.28001
Date: Tue, 22 May 2018 06:45:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1094141
           Summary: hpijs segfault
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Printing
          Assignee: jsmeix-at-suse.com
          Reporter: tiwai-at-suse.com
        QA Contact: jsmeix-at-suse.com
          Found By: ---
           Blocker: ---

When printing a PDF file from evince, I've got a segfault from hpijs, and the
printing fails.

May 22 08:22:26 valkyrie.site kernel: hpijs[23309]: segfault at 54 ip
000055f40e8ea983 sp 00007ffef264d3d0 error 6 in hpijs[55f40e8c2000+61000]

gdb shows a NULL pointer in pMode[0].

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000055a4dd0f0983 in apdk::DJGenericVIP::DJGenericVIP (
    this=0x55a4dd772f50, pSS=<optimized out>, proto=<optimized out>)
    at prnt/hpijs/djgenericvip.cpp:90
90            pMode[i]->bFontCapable = FALSE;
[Current thread is 1 (Thread 0x7f96dde6f080 (LWP 1954))]
(gdb) print pMode
$1 = {0x0, 0x0, 0x55a4dd774ff0, 0x55a4dd7360e0, 0x55a4dd778220,
  0x55a4dd7744a0, 0x55a4dd7745a0, 0x55a4dd776170, 0x55a4dd776270,
  0x55a4dd776370, 0x55a4dd7739f0, 0x55a4dd773af0, 0x0, 0x0, 0x0, 0x0, 0x0,
  0x0, 0x0, 0x0}
(gdb)

I remember that I could print on this machine a few weeks ago with Leap 15.0,
and I'm not sure what broke it.

summary: hpijs segfault


--1526975492.F86fE6.16748
Date: Tue, 22 May 2018 07:51:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1094148
           Summary: [SLE-Classic] The "Applications" window floats far away from the menu bar.
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: gwang-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 770947
  --> http://bugzilla.opensuse.org/attachment.cgi?id=770947&action=edit
"Applications" window floats far away from the menu bar

Steps:
1. Install gnome-shell-classic manually
2. Login with SLE-Classic session selected
3. Click "Applications" on the left-bottom corner

Actual Result:
The popup window floats above the menu bar with some distance.
Please find the attachment for details.

Expected Result:
The popup window should be above and next to the menu bar.


body:
--1526993032.2bdAA4BC4.6199
Date: Tue, 22 May 2018 12:43:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1094203
           Summary: Kernel 4.4.132-51 default will not boot
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: jamesrome-at-alum.mit.edu
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I updated to 4.4.132-51 default kernel on my 64-bit system. It will no longer
boot. The process tries to wait on 8 startup items over and over. It is
impossible to read everything on the low-resolution boot screen, but I get
messages like:

Sleeping function called from an invalid context in_atomic() irqs_disabled()
BUG: scheduling while atomic: systemd-udevd/220/....
BUG: Workqueue leaked lock or atomic: kworker/6:
    last function: bpf_done_on_this_cpu

It boots properly using the previous kernel, so I believe this is a kernel bug.

summary: Kernel 4.4.132-51 default will not boot


--1527000714.366E0F0.29708
Date: Tue, 22 May 2018 14:51:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1094222
           Summary: gcc-8 on opensuse tumbleweed points to wrong location when displaying error
    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: jmcdonough-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 770999
  --> http://bugzilla.suse.com/attachment.cgi?id=770999&action=edit
.i file from building lib/util/debug.c

Compiling the latest upstream samba with -O3, -Werror, among other flags, fails
but doesn't point to the correct error location.  The line it's giving us
doesn't make any sense for the error printed.

Below is the failing command and error messages.  I'll attach the .i as well.

gcc-8 -O3 -DDEVELOPER -DDEBUG_PASSWORD -fPIC -D_REENTRANT
-D_POSIX_PTHREAD_SEMANTICS -fstack-protector -g -Wall -Wshadow
-Wmissing-prototypes -Wcast-align -Wcast-qual -fno-common -Werror=address
-Werror=strict-prototypes -Wstrict-prototypes -Werror=write-strings
-Wwrite-strings -Werror-implicit-function-declaration -Werror=pointer-arith
-Wpointer-arith -Werror=declaration-after-statement
-Wdeclaration-after-statement -Werror=return-type -Wreturn-type
-Werror=uninitialized -Wuninitialized -Wimplicit-fallthrough
-Werror=strict-overflow -Wstrict-overflow=2 -Wformat=2 -Wno-format-y2k
-Wno-format-zero-length -Werror=format-security -Wformat-security
-Werror=format -Werror -Wno-error=deprecated-declarations
-Wno-error=tautological-compare -DSTATIC_samba_debug_MODULES=NULL
-DSTATIC_samba_debug_MODULES_PROTO="extern void
__samba_debug_dummy_module_proto(void)" -MD -Idefault/include/public
-I../include/public -Idefault/source4 -I../source4 -Idefault/lib -I../lib
-Idefault/source4/lib -I../source4/lib -Idefault/source4/include
-I../source4/include -Idefault/include -I../include -Idefault/lib/replace
-I../lib/replace -Idefault -I.. -Idefault/lib/talloc -I../lib/talloc
-I/usr/local/include -D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H=1 -D_GNU_SOURCE=1
-D_XOPEN_SOURCE_EXTENDED=1 ../lib/util/debug.c -c -save-temps -o
default/lib/util/debug_11.o

../lib/util/debug.c: In function 'debug_parse_levels':
../lib/util/debug.c:796:5: error: assuming pointer wraparound does not occur
when comparing P +- C1 with P +- C2 [-Werror=strict-overflow]
 bool debug_parse_levels(const char *params_str)
     ^~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors


--1527027553.47BCCAfc0.25310
Date: Tue, 22 May 2018 22:19:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1094283
           Summary: VUL-0: tor: malicious protocol version string allowed for DoS against directory authorities
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: astieger-at-suse.com
          Reporter: astieger-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

from https://gitweb.torproject.org/tor.git/plain/ReleaseNotes?id=tor-0.3.3.6

  o Major bugfixes (security, directory authority, denial-of-service):
    - Fix a bug that could have allowed an attacker to force a directory
      authority to use up all its RAM by passing it a maliciously
      crafted protocol versions string. Fixes bug 25517; bugfix on
      0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.

https://trac.torproject.org/projects/tor/ticket/25517
https://gitweb.torproject.org/tor.git/commit/?h=maint-0.3.3&c=42&id=a3a8d80bebdbb8988a2f33dea8b18a41e445c06f

Fixed in 0.3.3.6, and planned for 0.3.2.x after 0.3.2.10


--1527066779.3fDAa6.29073
Date: Wed, 23 May 2018 09:12:59 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1094323
           Summary: packages do not build reproducibly from pip install
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: bwiedemann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: ja+suse-at-matejcik.cz, toddrme2178-at-gmail.com
            Blocks: 1062303
          Found By: Development
           Blocker: ---

When working on reproducible builds for openSUSE I found that
some packages use pip install which creates .pyc files
that contain a random tmp path in them that is different for every build

affects at least:
python-cluster
python-jupyter_bqplot
python-jupyter_imatlab_kernel
python-PsyLab
python-sphinxcontrib-github-alt

here is an example diff:

/usr/lib/python3.6/site-packages/cluster/method/__pycache__/kmeans.cpython-36.pyc
@@ -110,7 +110,7 @@
 000006d0  00 5a 0e 63 6f 6e 74 72  6f 6c 5f 6c 65 6e 67 74  |.Z.control_lengt|
 000006e0  68 da 04 69 74 65 6d a9  00 72 13 00 00 00 fa 3a  |h..item..r.....:|
 000006f0  2f 74 6d 70 2f 70 69 70  2d 69 6e 73 74 61 6c 6c  |/tmp/pip-install|
-00000700  2d 32 75 38 6a 6f 79 74  76 2f 63 6c 75 73 74 65  |-2u8joytv/cluste|
+00000700  2d 6e 69 6c 34 6b 39 77  73 2f 63 6c 75 73 74 65  |-nil4k9ws/cluste|
 00000710  72 2f 63 6c 75 73 74 65  72 2f 6d 65 74 68 6f 64  |r/cluster/method|
 00000720  2f 6b 6d 65 61 6e 73 2e  70 79 da 08 5f 5f 69 6e  |/kmeans.py..__in|
 00000730  69 74 5f 5f 2e 00 00 00  73 20 00 00 00 00 01 06  |it__....s ......|

IMHO, those .pyc files should not contain any tmp path
because it does not exist in the target system anyway.


body:
--1527074858.2a71B26C0.15597
Date: Wed, 23 May 2018 11:27:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1094343
           Summary: Gajim's Plugin Installer is broken
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: opensuse-at-trummer.xyz
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Gajim's Plugin Installer is broken as of Tumbleweed 20180521 because it can't
find the required certificate. See

https://dev.gajim.org/gajim/gajim-plugins/issues/316

pkgs: gajim python-nbxmpp

summary: Gajim's Plugin Installer is broken


--1527194359.a021A73.8592
Date: Thu, 24 May 2018 20:39:19 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1094575
           Summary: qeth_l2 (s390x): 4.17-rc6 kernel assigns different MAC address than 4.16 or SLE15
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: S/390-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: mkubecek-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

While working on bsc#1083710, I tried to reproduce the issue with 4.17-rc6
kernel from Devel:Kernel:master IBS project (KotD for master branch) on orthos
machine s390vsl205.arch.suse.de. With this kernel, network device eth0 (qeth_l2
driver) did not work at all and I found message

  qeth 0.0.0800: MAC address 02:00:00:00:42:cd is not authorized

in kernel log (02:00:00:00:42:cd was MAC address assigned to eth0). With SLE15
or Devel:Kernel:stable (stable branch, 4.16.11) kernel, the device got
different address 02:00:00:00:01:08 and eth0 worked fine. Even with 4.17-rc6,
eth0 started to work once I assigned 02:00:00:00:01:08 manually (using
"ip link").

Checking git log between v4.16 and v4.17-rc6, these two commits caught my eye:

  b7493e91c11a  s390/qeth: use Read device to query hypervisor for MAC
  bcacfcbc82b4  s390/qeth: fix MAC address update sequence

and with these two reverted, eth0 got 02:00:00:00:01:08 and worked. Note:
SLE15 kernel has backport of ec61bd2fd2a2 which one of these refers to with
Fixes tag (it came in 4.13-rc1) but not any of these two.

As I don't understand how is MAC address assignment supposed to work, I don't
know if this is really a regression from these two commits or rather result of
misconfiguration (wrong address assigned by SLE15 or stable kernel configured
as "correct" so that correct one assigned by 4.17-rc6 is rejected).


body:
--1527226979.BCf1A6eC5.838
Date: Fri, 25 May 2018 05:42:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1094617
           Summary: devel:languages:nodejs/nodejs10: Bug
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: i-at-marguerite.su
          Reporter: eer-at-iie.xxx
        QA Contact: bnc-team-screening-at-forge.provo.novell.com
                CC: amajer-at-suse.com
          Found By: ---
           Blocker: ---

Hello!
npm10 package breaks building of native suff (e.g. npm install libpq searches
for node9 directory in node-gyp instead of node10.

Files:

file:///usr/lib64/node_modules/npm10/node_modules/node-gyp/addon-rpm.gypi
file:///usr/lib64/node_modules/npm10/node_modules/node-gyp/lib/configure.js

has line "/usr/include/node9/" instead of "/usr/include/node10/" and libpq
errors while install:

gyp: /usr/include/node9/common.gypi not found (cwd:
/home/su/wprojects/cloud-candy-be/node_modules/libpq) while reading includes of
binding.gyp while trying to load binding.gyp

summary: devel:languages:nodejs/nodejs10: Bug