--1542036610.2AdC4c00.7364
Date: Mon, 12 Nov 2018 15:30:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1115640
           Summary: pam (at least /lib64/security/pam_access.so) doesn't properly handle with ip addresses and subnets
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: nettezzaumanaa-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,

I've set this issue to critical because it's security related and there's
regress since 42.x and it's hidden regress that is not obvious after zypper dup
or without explicit verification ...

pam_access.so doesn't properly handle the PAM_RHOST (remote host address)
string Vs action set via /etc/security/access.conf and allows not permitted
clients to connect !!!!!

HOWTO-reproduce:

For reproducing we can use just sshd:

1) modify /etc/pam.d/sshd that it contains

account required pam_access.so debug

2) modify /etc/security/access.conf that it contains (default is empty file /
just comments) some restriction set (for example for root) aka:

# tail -1 /etc/security/access.conf
-:root:ALL EXCEPT 127.0.0.0/8 ::1 172.31.255.0/24

3) test connecting with root (or any other user you've used in step #2) to sshd
from non-permitted subnet .. it will pass saying, that 1.2.3.4 remote matches

APPENDIX:

see attached file, there is full output from pam_access.so in debug from 42.2
and from 15.0, so in here:

1) 42.2 where it works (I've obfuscated my client's address for security
reasons):

2018-11-12T13:20:44.973771+01:00 head22 sshd[9144]: pam_access(sshd:account):
login_access: user=root, from=82.113.x.y, file=/etc/security/access.conf
2018-11-12T13:20:44.974104+01:00 head22 sshd[9144]: pam_access(sshd:account):
line 124: - : root : ALL EXCEPT 127.0.0.0/8 ::1 192.168.60.0/24 172.31.255.0/24
...
2018-11-12T13:20:44.976942+01:00 head22 sshd[9144]: pam_access(sshd:account):
from_match=1, "82.113.x.y"
2018-11-12T13:20:44.977006+01:00 head22 sshd[9144]: pam_access(sshd:account):
access denied for user `root' from `82.113.x.y'
2018-11-12T13:20:44.977089+01:00 head22 sshd[9144]: fatal: Access denied for
user root by PAM account configuration [preauth]

++ fyi also from sshd POV (using sshd -Dd):

Nov 12 12:59:33 head22 sshd[8277]: debug1: userauth-request for user root
service ssh-connection method none [preauth]
Nov 12 12:59:33 head22 sshd[8277]: debug1: attempt 0 failures 0 [preauth]
Nov 12 12:59:33 head22 sshd[8277]: debug1: PAM: initializing for "root"
Nov 12 12:59:33 head22 sshd[8277]: debug1: PAM: setting PAM_RHOST to
"82.113.x.y"
Nov 12 12:59:33 head22 sshd[8277]: debug1: PAM: setting PAM_TTY to "ssh"
...
Nov 12 12:59:33 head22 sshd[8277]: pam_access(sshd:account): access denied for
user `root' from `82.113.53.162'
Nov 12 12:59:33 head22 sshd[8277]: debug1: do_pam_account: called
...
Nov 12 12:59:33 head22 sshd[8277]: Access denied for user root by PAM account
configuration [preauth]
Nov 12 12:59:33 head22 sshd[8277]: debug1: do_cleanup [preauth]
Nov 12 12:59:33 head22 sshd[8277]: debug1: monitor_read_log: child log fd
closed
Nov 12 12:59:33 head22 sshd[8277]: debug1: do_cleanup
Nov 12 12:59:33 head22 sshd[8277]: debug1: PAM: cleanup

2) on 15.0 where it doesn't work

2018-11-12T13:20:51.674121+01:00 head220 sshd[27668]: pam_access(sshd:account):
login_access: user=root, from=82.113.x.y, file=/etc/security/access.conf
2018-11-12T13:20:51.675393+01:00 head220 sshd[27668]: pam_access(sshd:account):
line 123: - : root : ALL EXCEPT 127.0.0.0/8 ::1 172.31.255.0/24
...
2018-11-12T13:20:51.679651+01:00 head220 sshd[27668]: pam_access(sshd:account):
from_match=0, "82.113.x.y"
2018-11-12T13:20:51.688284+01:00 head220 sshd[27668]: pam_unix(sshd:session):
session opened for user root by (uid=0)

regards, dan


--1542038873.e2Cd2770.22576
Date: Mon, 12 Nov 2018 16:07:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1115645
           Summary: Factory/TW requires cargo/rust cbindgen to be able to compile Firefox >= 63
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: wolfgang-at-rosenauer.org
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1112852
          Found By: ---
           Blocker: ---

Firefox 63 also introduced a new mandatory build dependency on the tool
cbindgen.

We need this package included to be able to build and release FF >= 63.

Since Luke indicated he could possibly prepare it for TW I'll assign to him for
the moment.


--1542096206.82d1DFa85.891
Date: Tue, 13 Nov 2018 08:03:26 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1115722
           Summary: VUL-1: CVE-2018-19198: uriparser: UriQuery.c allows an out-of-bounds write via a uriComposeQuery* or uriComposeQueryEx* function because the '&' character is mishandled in certain contexts
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/219062/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: amajer-at-suse.com
          Reporter: kbabioch-at-suse.com
        QA Contact: security-team-at-suse.de
                CC: crrodriguez-at-opensuse.org, jengelh-at-inai.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-19198

An issue was discovered in uriparser before 0.9.0. UriQuery.c allows an
out-of-bounds write via a uriComposeQuery* or uriComposeQueryEx* function
because the '&' character is mishandled in certain contexts.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-19198
https://github.com/uriparser/uriparser/commit/864f5d4c127def386dd5cc926ad96934b297f04e
https://github.com/uriparser/uriparser/blob/uriparser-0.9.0/ChangeLog


--1542096258.56aedbf75.32475
Date: Tue, 13 Nov 2018 08:04:18 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1115723
           Summary: VUL-1: CVE-2018-19199: uriparser: UriQuery.c allows an integer overflow via a uriComposeQuery* or uriComposeQueryEx* function because of an unchecked multiplication
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/219063/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: amajer-at-suse.com
          Reporter: kbabioch-at-suse.com
        QA Contact: security-team-at-suse.de
                CC: crrodriguez-at-opensuse.org, jengelh-at-inai.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-19199

An issue was discovered in uriparser before 0.9.0. UriQuery.c allows an integer
overflow via a uriComposeQuery* or uriComposeQueryEx* function because of an
unchecked multiplication.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-19199
https://github.com/uriparser/uriparser/commit/f76275d4a91b28d687250525d3a0c5509bbd666f


--1542096386.5F0AD5.888
Date: Tue, 13 Nov 2018 08:06:26 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1115724
           Summary: VUL-1: CVE-2018-19200: uriparser: UriCommon.c allows attempted operations on NULL input via a uriResetUri* function
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/219064/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: amajer-at-suse.com
          Reporter: kbabioch-at-suse.com
        QA Contact: security-team-at-suse.de
                CC: crrodriguez-at-opensuse.org, jengelh-at-inai.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-19200

An issue was discovered in uriparser before 0.9.0. UriCommon.c allows attempted
operations on NULL input via a uriResetUri* function.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-19200
https://github.com/uriparser/uriparser/commit/f58c25069cf4a986fe17a80c5b38687e31feb539


--1542112183.Cba0f12.24507
Date: Tue, 13 Nov 2018 12:29:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1115778
           Summary: ibus-libpinyin build failed for openSUSE Leap 15
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: qzhao-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

In M17N project, ibus-libpinyin has been updated to 1.10, but it failed to
compile for openSUSE Leap, Error log as bellow

[   92s] PYPEmojiCandidates.cc:40:16: error: 'strcmp' was not declared in this
scope
[   92s]      return 0 > strcmp (lhs.m_emoji_match, rhs.m_emoji_match);
[   92s]                 ^~~~~~
[   92s]   CXX      ibus_engine_libpinyin-PYEnglishEditor.o
[   92s] PYPEmojiCandidates.cc:40:16: note: suggested alternative: 'strtoq'
[   92s]      return 0 > strcmp (lhs.m_emoji_match, rhs.m_emoji_match);
[   92s]                 ^~~~~~
[   92s]                 strtoq
[   92s] make[3]: *** [Makefile:1090:
ibus_engine_libpinyin-PYPEmojiCandidates.o] Error 1
[   92s] make[3]: *** Waiting for unfinished jobs....
[   93s] PYExtEditor.cc: In function 'const string
PY::translate_to_longform(gint64, const char**, PY::unit_t*, int)':
[   93s] PYExtEditor.cc:97:28: warning: comparison between signed and unsigned
integer expressions [-Wsign-compare]
[   93s]              for ( i = 0; i < units_len; ++i) {
[   93s]                           ~~^~~~~~~~~~~
[   94s] make[3]: Leaving directory
'/home/abuild/rpmbuild/BUILD/ibus-libpinyin-1.10.91/src'
[   94s] make[2]: *** [Makefile:632: all] Error 2
[   94s] make[2]: Leaving directory
'/home/abuild/rpmbuild/BUILD/ibus-libpinyin-1.10.91/src'
[   94s] make[1]: *** [Makefile:518: all-recursive] Error 1
[   94s] make[1]: Leaving directory
'/home/abuild/rpmbuild/BUILD/ibus-libpinyin-1.10.91'
[   94s] make: *** [Makefile:448: all] Error 2
[   94s] error: Bad exit status from /var/tmp/rpm-tmp.7si9pi (%build)
[   94s]
[   94s]
[   94s] RPM build errors:
[   94s]     Bad exit status from /var/tmp/rpm-tmp.7si9pi (%build)
[   94s]
[   94s] lamb60 failed "build ibus-libpinyin.spec" at Sat Nov  3 07:18:23 UTC
2018.
[   94s]
[   94s] ### VM INTERACTION START ###
[   97s] [   87.374278] sysrq: SysRq : Power Off
[   97s] [   87.379567] reboot: Power down
[   97s] ### VM INTERACTION END ###
[   97s]
[   97s] lamb60 failed "build ibus-libpinyin.spec" at Sat Nov  3 07:18:27 UTC
2018.
[   97s]


--1542204477.3d1b0.8846
Date: Wed, 14 Nov 2018 14:07:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1115999
           Summary: Please convert SysV init scripts by cyrus-imapd into native systemd services
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

It would be great if the SysV init scrips shipped by this package could
be converted into systemd native services.

Indeed most packages shipped by openSUSE Factory switched to native
systemd unit files years ago and we plan to drop the obsolete/limited
SysV compat support in the future.

If this appears to be a big task, one quick way to solve it is to copy
and ship (as is) the .service unit wrappers generated automatically by
systemd-sysv-generator at boot. Indeed such wrappers are generated by
systemd in order to support SysV init scripts similarly to native
units.

You can see the content of a wrapper unit with:

 $ systemctl cat <sysvinit-script>.service

As you could see the wrapper unit simply calls the SysV script, which
should be moved out of /etc/init.d, probably in a directory owned by
your package.

In all cases we would be glad to provide any help if needed in this
task.

Thanks in advance.


--1542205542.BdACeF2d0.20940
Date: Wed, 14 Nov 2018 14:25:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116007
           Summary: Please convert SysV init scripts by dkimproxy into native systemd services
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

It would be great if the SysV init scrips shipped by this package could
be converted into systemd native services.

Indeed most packages shipped by openSUSE Factory switched to native
systemd unit files years ago and we plan to drop the obsolete/limited
SysV compat support in the future.

If this appears to be a big task, one quick way to solve it is to copy
and ship (as is) the .service unit wrappers generated automatically by
systemd-sysv-generator at boot. Indeed such wrappers are generated by
systemd in order to support SysV init scripts similarly to native
units.

You can see the content of a wrapper unit with:

 $ systemctl cat <sysvinit-script>.service

As you could see the wrapper unit simply calls the SysV script, which
should be moved out of /etc/init.d, probably in a directory owned by
your package.

In all cases we would be glad to provide any help if needed in this
task.

Thanks in advance.


--1542206289.ad1C6.25670
Date: Wed, 14 Nov 2018 14:38:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116010
           Summary: Please convert SysV init scripts by festival into native systemd services
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

It would be great if the SysV init scrips shipped by this package could
be converted into systemd native services.

Indeed most packages shipped by openSUSE Factory switched to native
systemd unit files years ago and we plan to drop the obsolete/limited
SysV compat support in the future.

If this appears to be a big task, one quick way to solve it is to copy
and ship (as is) the .service unit wrappers generated automatically by
systemd-sysv-generator at boot. Indeed such wrappers are generated by
systemd in order to support SysV init scripts similarly to native
units.

You can see the content of a wrapper unit with:

 $ systemctl cat <sysvinit-script>.service

As you could see the wrapper unit simply calls the SysV script, which
should be moved out of /etc/init.d, probably in a directory owned by
your package.

In all cases we would be glad to provide any help if needed in this
task.

Thanks in advance.


--1542207172.4E667D180.1233
Date: Wed, 14 Nov 2018 14:52:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116014
           Summary: Please convert SysV init scripts by  fwnn into native systemd services
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

It would be great if the SysV init scrips shipped by this package could
be converted into systemd native services.

Indeed most packages shipped by openSUSE Factory switched to native
systemd unit files years ago and we plan to drop the obsolete/limited
SysV compat support in the future.

If this appears to be a big task, one quick way to solve it is to copy
and ship (as is) the .service unit wrappers generated automatically by
systemd-sysv-generator at boot. Indeed such wrappers are generated by
systemd in order to support SysV init scripts similarly to native
units.

You can see the content of a wrapper unit with:

 $ systemctl cat <sysvinit-script>.service

As you could see the wrapper unit simply calls the SysV script, which
should be moved out of /etc/init.d, probably in a directory owned by
your package.

In all cases we would be glad to provide any help if needed in this
task.

Thanks in advance.


--1542207405.bC674350.2253
Date: Wed, 14 Nov 2018 14:56:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116015
           Summary: Please convert SysV init scripts by fonehome into native systemd services
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

It would be great if the SysV init scrips shipped by this package could
be converted into systemd native services.

Indeed most packages shipped by openSUSE Factory switched to native
systemd unit files years ago and we plan to drop the obsolete/limited
SysV compat support in the future.

If this appears to be a big task, one quick way to solve it is to copy
and ship (as is) the .service unit wrappers generated automatically by
systemd-sysv-generator at boot. Indeed such wrappers are generated by
systemd in order to support SysV init scripts similarly to native
units.

You can see the content of a wrapper unit with:

 $ systemctl cat <sysvinit-script>.service

As you could see the wrapper unit simply calls the SysV script, which
should be moved out of /etc/init.d, probably in a directory owned by
your package.

In all cases we would be glad to provide any help if needed in this
task.

Thanks in advance.


--1542207867.Bee12CA6.5424
Date: Wed, 14 Nov 2018 15:04:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116016
           Summary: Please convert SysV init scripts by libinfinity into native systemd services
    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: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

It would be great if the SysV init scrips shipped by this package could
be converted into systemd native services.

Indeed most packages shipped by openSUSE Factory switched to native
systemd unit files years ago and we plan to drop the obsolete/limited
SysV compat support in the future.

If this appears to be a big task, one quick way to solve it is to copy
and ship (as is) the .service unit wrappers generated automatically by
systemd-sysv-generator at boot. Indeed such wrappers are generated by
systemd in order to support SysV init scripts similarly to native
units.

You can see the content of a wrapper unit with:

 $ systemctl cat <sysvinit-script>.service

As you could see the wrapper unit simply calls the SysV script, which
should be moved out of /etc/init.d, probably in a directory owned by
your package.

In all cases we would be glad to provide any help if needed in this
task.

Thanks in advance.


--1542208555.bdFf8ec3.11898
Date: Wed, 14 Nov 2018 15:15:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116021
           Summary: k10temp and iwlwifi sensor output missing
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: malcolmlewis-at-cableone.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

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

Hi
I have two HP Laptops both have lost the iwlwifi temperature sensor with the
update to the 4.19.x kernel, and one is not reporting the cpu temperature;

HP 14-an013nr
CPU - AMD E2-7110

k10temp-pci-00c3 reports temperature
iwlwifi-* sensor gone

HP 15-aw057nr
CPU - AMD A10-9600P

k10temp-pci-00c3 not reporting temperature (wasn't working on 4.18.x either)
iwlwifi-* sensor gone

Latest Tumbleweed release 20181112 Kernel 4.19.1-1-default.


body:
--1542211295.48deCECD0.20775
Date: Wed, 14 Nov 2018 16:01:35 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116043
           Summary: KTP Teleapthy packages should be included in main repo
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: agronick+suse-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Currently the built in KDE instant messenger is excluded from the default
repositories based on the mistaken assumption that it is no longer maintained.
(https://en.opensuse.org/KDE_Telepathy) "The meta package telepathy-kde has
been removed from the official repository as of the release of openSUSE
Tumbleweed snapshot 20170825 [and Leap] because KDE Telepathy is actually not
maintained for a long time."

This is in fact not the case. As you can see in the following Github repos, all
KDE Telepathy packages are being actively maintained:

https://github.com/KDE/ktp-desktop-applets/commits/master
https://github.com/KDE/ktp-common-internals/commits/master
https://github.com/KDE/ktp-contact-runner/commits/master
https://github.com/KDE/ktp-accounts-kcm/commits/master

KDE Telepathy provides excellent desktop integration and is an integral part of
the KDE desktop. Currently users have to move all of their KDE packages to a
different repository
(http://download.opensuse.org/repositories/KDE:/Applications:/18.04/openSUSE_Leap_15.0/)
just to use this program. Even in that repository it is actively maintained
with the last change being on the 9th of November.

Currently if KDE users want to use the protocols that Telepathy provides they
need to install Empathy which provides no desktop integration and a dissimilar
experience since it is made for the Gnome desktop.

There is no reason to exclude the KTP packages from the default repos and they
were removed based off a mistaken assumption.

pkgs: ktp-accounts-kcm ktp-approver ktp-auth-handler ktp-call-ui ktp-common-internals ktp-contact-list ktp-contact-runner ktp-desktop-applets ktp-filetransfer-handler ktp-kded-module ktp-send-file ktp-text-ui patterns-kde telepathy-logger-qt5


--1542212964.2f5661b50.10183
Date: Wed, 14 Nov 2018 16:29:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116050
           Summary: Please convert SysV init scripts by virtualbox into native systemd services
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

It would be great if the SysV init scrips shipped by this package could
be converted into systemd native services.

Indeed most packages shipped by openSUSE Factory switched to native
systemd unit files years ago and we plan to drop the obsolete/limited
SysV compat support in the future.

If this appears to be a big task, one quick way to solve it is to copy
and ship (as is) the .service unit wrappers generated automatically by
systemd-sysv-generator at boot. Indeed such wrappers are generated by
systemd in order to support SysV init scripts similarly to native
units.

You can see the content of a wrapper unit with:

 $ systemctl cat <sysvinit-script>.service

As you could see the wrapper unit simply calls the SysV script, which
should be moved out of /etc/init.d, probably in a directory owned by
your package.

In all cases we would be glad to provide any help if needed in this
task.

Thanks in advance.


--1542214571.31C401.17738
Date: Wed, 14 Nov 2018 16:56:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116053
           Summary: Please convert SysV init scripts by xfs into native systemd services
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: xorg-maintainer-bugs-at-forge.provo.novell.com
          Reporter: fbui-at-suse.com
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

It would be great if the SysV init scrips shipped by this package could
be converted into systemd native services.

Indeed most packages shipped by openSUSE Factory switched to native
systemd unit files years ago and we plan to drop the obsolete/limited
SysV compat support in the future.

If this appears to be a big task, one quick way to solve it is to copy
and ship (as is) the .service unit wrappers generated automatically by
systemd-sysv-generator at boot. Indeed such wrappers are generated by
systemd in order to support SysV init scripts similarly to native
units.

You can see the content of a wrapper unit with:

 $ systemctl cat <sysvinit-script>.service

As you could see the wrapper unit simply calls the SysV script, which
should be moved out of /etc/init.d, probably in a directory owned by
your package.

In all cases we would be glad to provide any help if needed in this
task.

Thanks in advance.


body:
--1542253016.74Da74D1.21418
Date: Thu, 15 Nov 2018 03:36:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116116
           Summary: dex Version: was not built properly
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kubic
          Assignee: kubic-bugs-at-opensuse.org
          Reporter: pgeorgiadis-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Reproducer:
~~~~~~~~~~~~

* In TW:
> zypper -n in caasp-dex; caasp-dex version
> dex Version: was not built properly
> Go Version: go1.10.2
> Go OS/ARCH: linux amd64

* Everywhere, using our container

> drpaneas@ASRock-Intel-Ethernet:~> docker run -it --rm registry.opensuse.org/devel/caasp/kubic-container/container/kubic/caasp-dex:2.7.1
> dex Version: was not built properly
> Go Version: go1.10.2
> Go OS/ARCH: linux amd64

This happens also for the caasp-dex CaaSP container image within our SUSE
Registry.

PS: priority up to P3 (after talking with Flavio).

summary: dex Version: was not built properly


--1542268622.758f6e0.21677
Date: Thu, 15 Nov 2018 07:57:02 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116153
           Summary: Audacity cannot play/record sound via PulseAudio with libasound2-1.1.7
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: qantas94heavy-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When PulseAudio is using the sound devices, Audacity is unable to play/record
any sound.

Audacity is supposed to use the "default" device which uses PulseAudio but this
is not present.

This issue did not occur with libasound2-1.1.6, so this appears to be a
regression.

Also reported by others for Debian Sid:
https://www.mail-archive.com/debian-user-at-lists.debian.org/msg736041.html


body:
--1542272325.0eD72D0.16183
Date: Thu, 15 Nov 2018 08:58:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116161
           Summary: Gajim is missing 'precis-i18n'
    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: ---

Since the update to Tumbleweed 20181112, Gajim won't start anymore. Here's the
output:

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 3123,
in <module>
    @_call_aside
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3107,
in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3136,
in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 578,
in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 895,
in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 781,
in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'precis-i18n>=1.0.0' distribution was
not found and is required by gajim

summary: Gajim is missing 'precis-i18n'


body:
--1542273640.b4b5Af1e3.24425
Date: Thu, 15 Nov 2018 09:20:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

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

New version of fwts (firmware testsuite) bring several interesting
improvements, such as:
+ dmicheck: checks (Extended) Maximum Capacity for type 16
+ snapcraft: add libbsd-dev to build-packages
+ efi_runtime: re-enable the resetsystem runtime interface
+ olog:olog.json: Update OPAL skiboot errors to check on olog scan
+ acpi: button: check fixed hardware & control method power buttons
+ kernelscan: add -k option to specify klog json filename
+ src/lib: add module probing helper functions
+ lib: fwts_efi_module: use the new module loading helper functions
+ lib/fwts_cpu: use new use the new module loading helper functions
+ auto-packager: mkpackage.sh: add disco

summary: Update fwts to version 18.11.00


--1542453531.C1Dc48D0.31998
Date: Sat, 17 Nov 2018 11:18:51 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116431
           Summary: systemd tmpfiles does not clean-up sddm-auth files
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: 64bit
                OS: Other
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: martin@winter-rosenheim.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Over time, the /tmp directory contains a growing number of sddm-auth files. The
systemd tmpfile services makes no attempt to clean them up.

I would suggest to add a rule to /etc/tmpfiles.d to remove these files.


--1542454404.3a650Db0.31783
Date: Sat, 17 Nov 2018 11:33:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116432
           Summary: ipset save -file <filename> produces empty files
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: suse+build@de-korte.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since the update to ipset 7.0, the command

    ipset save -file output.txt

result in an output.txt file with zero length/no content. As a workaround, the
following does work

    ipset save > output.txt

This is a regression from earlier versions.

Steps to reproduce:

    ipset create testlist hash:net family inet
    ipset add testlist 1.2.3.4/32
    ipset save -file output.txt

output.txt exists, but is an empty file

    ipset save > output.txt

output.txt contains

    create testlist hash:net family inet hashsize 1024 maxelem 65536
    add testlist 1.2.3.4


--1542537666.b255dFfa0.11263
Date: Sun, 18 Nov 2018 10:41:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116451
           Summary: LO help find function doesn't find some entrie
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LibreOffice
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: chris-at-twoten.is
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Using find to locate help for some items e.g. "sumif" doesns't return result
for that item. Bugzilla report on LO has returned info that there is a new help
system that resolves the issue that could be used in current version builds

See original LO bug report for more detail

https://bugs.documentfoundation.org/show_bug.cgi?id=120500

and linked info from response on there

https://blog.documentfoundation.org/blog/2018/08/10/taming-libreoffice-6-1s-new-help-system/


body:
--1542569873.fF4dcA53.24758
Date: Sun, 18 Nov 2018 19:37:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116458
           Summary: [HPC, macros] Handle Dependencies properly when providers are available both in the default and HPC Module Path
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: openSUSE Factory
            Status: CONFIRMED
          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: hpc-maintainer-bugs-at-forge.provo.novell.com
          Found By: Development
           Blocker: ---

The HPC dependency generator presently considers a dependency when a provider
(library) is available in the default path - even if a provider is also
available in the HPC module path. This may create unwanted dependencies.

Thus make the dependency generator 'environment module aware'. This requires to
add a macro holding the required modules and a macro to set this. This will
allow us to take advantage of the module list elsewhere, ie in hpc_setup.

pkgs: gnu-compilers-hpc openmpi3 suse-hpc


--1542589280.fd65C52e0.1426
Date: Mon, 19 Nov 2018 01:01:20 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116460
           Summary: Installing zynaddsubfx should install zynaddsubfx-common as a dependency
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: aurelien.murith@net-c.be
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When you install the zynaddsubfx synthesizer, the "zynaddsubfx-common" package
is not installed automatically. However, zynaddsubfx won't run without it, so
it should be added as a dependency.


--1542613412.E34A60.11850
Date: Mon, 19 Nov 2018 07:43:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116485
           Summary: ibus indicator Chinese preference doesn't pop up
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: zgao-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I am using tumbleweed 20181111 snapshot and I kept all packages updated. The
window system is wayland. Chinese input is functioning. Both libpinyin and
ibus-pinyin have this problem.

According to `journalctl -f`. there is a python core dump in
libgtk-3.so.0.2400.1

```
Nov 19 02:41:20 linux-7w3k kernel: python[5833]: segfault at 0 ip
00007face28ca2c9 sp 00007fff22801d70 error 4 in
libgtk-3.so.0.2400.1[7face2669000+352000]
Nov 19 02:41:20 linux-7w3k kernel: Code: 5c 41 5d c3 66 66 2e 0f 1f 84 00 00 00
00 00 66 90 8b 35 82 30 45 00 31 d2 31 c0 e9 b1 18 da ff 90 53 48 89 fb e8 27
fe ff ff <48> 8b 3b 48 89 c6 e8 2c 08 da ff 48 8b 40 18 48 85 c0 74 0b 48 89
Nov 19 02:41:20 linux-7w3k systemd[1]: Started Process Core Dump (PID 5837/UID
0).
Nov 19 02:41:20 linux-7w3k systemd-coredump[5838]: Process 5833 (python) of
user 1000 dumped core.
Nov 19 02:41:40 linux-7w3k kernel: BTRFS info (device sda5): qgroup scan
completed (inconsistency flag cleared)
```

coredumpctl info
```
           PID: 2482 (python)
           UID: 1000 (gao)
           GID: 100 (users)
        Signal: 11 (SEGV)
     Timestamp: Mon 2018-11-19 02:32:06 EST (10min ago)
  Command Line: /usr/bin/python main2.py libpinyin
    Executable: /usr/bin/python2.7
 Control Group: /user.slice/user-1000.slice/user@1000.service/dbus.service
          Unit: user@1           PID: 2482 (python)
           UID: 1000 (gao)
           GID: 100 (users)
        Signal: 11 (SEGV)
     Timestamp: Mon 2018-11-19 02:32:06 EST (10min ago)
  Command Line: /usr/bin/python main2.py libpinyin
    Executable: /usr/bin/python2.7
 Control Group: /user.slice/user-1000.slice/user@1000.service/dbus.service
          Unit: user@1000.service
     User Unit: dbus.service
         Slice: user-1000.slice000.service
     User Unit: dbus.service
         Slice: user-1000.slice
```

Preference for Chinese input on ibus indicator does not pop up.

Reproduction steps
---

- 1. install ibus ibus-pinyin
- 2. add Chinese to the input sources in `Region & Language`
- 3. log out and log in
- 4. click on the ibus indicator on the top right
- 5. select chinese and click on `preference`


body:
--1542632477.eb040.20079
Date: Mon, 19 Nov 2018 13:01:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116567
           Summary: Missing directory /var/cache/cgit
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: x86-64
                OS: SUSE Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Development
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: opensuse@1.opensuse.bgcomp.co.uk
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The RPM for cgit has a missing cache directory, to wit, /var/cache/cgit.

Meaning cgit does not run properly.

Please add it and ensure it is owned by wwwrun/www.

summary: Missing directory /var/cache/cgit


body:
--1542644956.E14Eb38c5.17479
Date: Mon, 19 Nov 2018 16:29:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116596
           Summary: python sepolicy missing
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: jsegitz-at-suse.com
          Reporter: mrueckert-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: varkoly-at-suse.com
          Found By: ---
           Blocker: ---

found while trying to update 389-ds to 1.4.0.19

summary: python sepolicy missing


--1542653927.CBeBF0.3638
Date: Mon, 19 Nov 2018 18:58:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116608
           Summary: VUL-0: CVE-2018-17479: chromium: Use-after-free in GPU
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
               URL: https://smash.suse.de/issue/219446/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: tchvatal-at-suse.com
          Reporter: astieger-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

https://chromereleases.googleblog.com/2018/11/stable-channel-update-for-desktop_19.html

Fixed in 70.0.3538.110:

- CVE-2018-17479: Use-after-free in GPU
https://crbug.com/905336

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-17479
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17479
https://chromereleases.googleblog.com/2018/11/stable-channel-update-for-desktop_19.html


--1542676872.DffF12d82.4960
Date: Tue, 20 Nov 2018 01:21:12 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116625
           Summary: Systemd automount units fail after suspend/resume
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: David@WalkerStreet.info
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Systemd's automount units often fail after a suspend/resume cycle.  I believe
it occurs for units that are not mounted at the time the system is suspended,
but I'm not sure.  I've only tried this with nfs mounts, so it may only apply
to nfs autmounts.

Here's a log from such a failed unit:

  Nov 19 16:22:39 homelap5.WalkerStreet.info systemd[1]:
DWMedia-DWMedia7.automount: Got invalid poll event 16 on pipe (fd=71)
  Nov 19 16:22:39 homelap5.WalkerStreet.info systemd[1]:
DWMedia-DWMedia7.automount: Unit entered failed state.

Restarting the automount unit after the system resumes gets things working
again, so I've put the following script into /etc/NetworkManager/dispatcher.d
as a quick and dirty workaround:

#!/usr/bin/perl
#
# FixAutomount - Query systemctl for failed automount units and restart them.
#                This is needed, as suspend/resume seems to make them fail.
#                It can be invoked from a NetworkManager dispatcher script.
#
if ($ARGV[1] eq "up")
 {
  open (FAILED, "systemctl list-units *.automount --failed |");
  while (<FAILED>)
   {
    if (/\s+(\S+).automount\s+loaded\s/)
     {
      system ("systemctl restart $1.automount");
     };
   };
 };


--1542701756.685b0.23251
Date: Tue, 20 Nov 2018 08:15:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116658
           Summary: Crash of Writer opening any document having "invalid" python file in home directory
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LibreOffice
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: lambhaka-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Steps to reproduce:
1. place file abc.py in the home directory of the current user, containing
something like "hello.world()"
2. start libreoffice and try to open existing or to create new empty writer
file (possibly some of libreoffice file).

Actual results
> LibreOffice crashes.

If you rename a abc.py file into abc.py.bck, libreoffice starts normally.

I've already reported the bug in the LibreOffice Bugtracking system
(https://bugs.documentfoundation.org/show_bug.cgi?id=121384). It was closed as
not an libreoffice bug (packaging bug).

The investigations have shown, that the crash of libreoffice is only possible
with the version from opensuse repository. The TDF-packages are working without
issues.
On kubuntu the libreoffice works also without issues.

Tested Environment:
Newly installed openSuse Leap 15.0. Standard KDE Desktop-Installation x64 with
all updates till 19th of November 2018 applied.
LibreOffice version 6.1.3.2-lp150.2.6.2.x86_64.


--1542706003.b1daaf0.12801
Date: Tue, 20 Nov 2018 09:26:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116675
           Summary: sendmail system service wrongly Aliased to .target unit
    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: nettezzaumanaa-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello Geeko minions ..

sendmail's systemd service (unit) is wrong because enabling that creates
symlink

/etc/systemd/system/mail-transfer-agent.target ->
/usr/lib/systemd/system/sendmail.service

via redundant (non-sense) action:

Alias=mail-transfer-agent.target

resulting to `bad' state of mail-transfer-agent.target in list-service-files:

# systemctl list-unit-files | grep bad
mail-transfer-agent.target                bad

# systemd-analyze verify /etc/systemd/system/mail-transfer-agent.target
mail-transfer-agent.target: Failed to create mail-transfer-agent.target/start:
Unit mail-transfer-agent.target not found.

RATIONALE:

Alias can't/won't transition .service to .target (it's logical error) and vice
versa ..

HOWTO-REPRODUCE:

Install sendmail (it will conflict/deinstall default postfix), will be enabled
by default .. Feel free to disable/re-enable it manually .. Enabling service
creates /etc/systemd/system/mail-transfer-agent.target ->
/usr/lib/systemd/system/sendmail.service symlik ... systemd-analyze won't like
it and in list-unit-files it will have a `bad' status ...

FIX:

Kick away Alias=mail-transfer-agent.target from
/usr/lib/systemd/system/sendmail.service

regards, dan


--1542739057.7e66F0.32387
Date: Tue, 20 Nov 2018 18:37:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116767
           Summary: Cloud:Tools/cloud-init: Bug network not coming up
    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: jon.brightwell-at-zpg.co.uk
        QA Contact: bnc-team-screening-at-forge.provo.novell.com
                CC: rjschwei-at-suse.com
          Found By: ---
           Blocker: ---

Created attachment 790345
  --> http://bugzilla.opensuse.org/attachment.cgi?id=790345&action=edit
screenshot of eth0 down

Trying to diagnose an issue with a L15 openstack image we're building and I
can't find any reason why this has suddenly stopped working apart from
(possibly) the cloud-init update.

If I set off a ping on a building instance, it responds 2 packets before never
working again.
$ ping 51.68.87.137
PING 51.68.87.137 (51.68.87.137) 56(84) bytes of data.
64 bytes from 51.68.87.137: icmp_seq=122 ttl=46 time=670 ms
64 bytes from 51.68.87.137: icmp_seq=123 ttl=46 time=34.1 ms

This is reproducible.

$ ping 51.68.87.137
PING 51.68.87.137 (51.68.87.137) 56(84) bytes of data.
64 bytes from 51.68.87.137: icmp_seq=18 ttl=46 time=607 ms
64 bytes from 51.68.87.137: icmp_seq=19 ttl=46 time=31.5 ms

I can't be 100% sure of the timing (vnc lag) but it seems to respond to pings
shortly after wicked and dhcp is started (approx 8-9s in) but then dies shortly
with the cloud-init meta data crawler - where it shows "ci-info eth0 up false"
in an ascii table showing the NICs.


body:
--1542773722.f7b774.19573
Date: Wed, 21 Nov 2018 04:15:22 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116808
           Summary: festival segfaults
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: mrmazda-at-earthlink.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

bob@localhost:~> festival --tts ttstest.txt
Segmentation fault (core dumped)
# grep RETT /etc/os-release
PRETTY_NAME="openSUSE Leap 15.0"
# rpm -qa | egrep 'festival|bility3-3'
festival-2.4-lp150.31.1.x86_64
kdeaccessibility3-3.5.10-lp150.63.1.x86_64
# journalctl -b | grep festiv | tail -n1
Nov 20 20:27:11 localhost kernel: festival[9030]: segfault at 0 ip
0000557d977f72af sp 00007fff656074a0 error 4 in festival[557d97676000+2c5000]
# journalctl -b | grep festiv | wc -l
46
# dmesg | grep festiv | tail -n1
[18669.876039] festival[9030]: segfault at 0 ip 0000557d977f72af sp
00007fff656074a0 error 4 in festival[557d97676000+2c5000]
# dmesg | grep festiv | wc -l
43
/var/lib/systemd/coredump/ is empty

This was an upgrade from KDE3 42.2 to 42.3 to 15.0 where KTTSmgr and festival
were working on 42.2. On the interim 42.3, attempting 'festival --tts
ttstest.txt' produces multiple "Linux: can't open /dev/dsp messages".

summary: festival segfaults


--1542798028.2aB10.3495
Date: Wed, 21 Nov 2018 11:00:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116867
           Summary: udev rule for printer installation fails due to missing python module
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Printing
          Assignee: jsmeix-at-suse.com
          Reporter: saloution-at-googlemail.com
        QA Contact: jsmeix-at-suse.com
          Found By: ---
           Blocker: ---

Hello,

I use:

NAME="openSUSE Tumbleweed"
# VERSION="20181116"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20181116"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20181116"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"

I connected a printer to my computer and found the following error in my system
journal:

Nov 17 08:47:15 mars udev-configure-printer[4884]: URI contains USB serial
number
Nov 17 08:47:15 mars udev-configure-printer[4884]: URI match:
usb://Brother/HL-2140%20series?serial=F8J644819
Nov 17 08:47:15 mars udev-configure-printer[4884]: About to add queue for
usb://Brother/HL-2140%20series?serial=F8J644819
Nov 17 08:47:16 mars udev-configure-printer[4884]: Traceback (most recent call
last):
Nov 17 08:47:16 mars udev-configure-printer[4884]:   File
"/usr/lib/udev/udev-add-printer", line 23, in <module>
Nov 17 08:47:16 mars udev-configure-printer[4884]:     import cupshelpers
Nov 17 08:47:16 mars udev-configure-printer[4884]:   File
"/usr/lib/python3.6/site-packages/cupshelpers/__init__.py", line 60, in
<module>
Nov 17 08:47:16 mars udev-configure-printer[4884]:     from . import
openprinting
Nov 17 08:47:16 mars udev-configure-printer[4884]:   File
"/usr/lib/python3.6/site-packages/cupshelpers/openprinting.py", line 22, in
<module>
Nov 17 08:47:16 mars udev-configure-printer[4884]:     import requests,
urllib.request, urllib.parse, urllib.error, platform, threading, tempfile,
traceback
Nov 17 08:47:16 mars udev-configure-printer[4884]: ModuleNotFoundError: No
module named 'requests'
Nov 17 08:47:16 mars systemd[1]: configure-printer@usb-001-004.service: Main
process exited, code=exited, status=1/FAILURE
Nov 17 08:47:16 mars systemd[1]: configure-printer@usb-001-004.service: Failed
with result 'exit-code'.

I installed then the python3 package requests using Yast2, which was not
installed initially. I think it should be installed.

After the installation (and a restart which may not be required), installation
and printing works.


--1542803191.3d3a6FE0.23198
Date: Wed, 21 Nov 2018 12:26:31 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116887
           Summary: VUL-1: CVE-2018-19387: tmux: format_cb_pane_tabs in format.c in tmux 2.7 through 2.8 might allow attackers to cause a denial of service
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/219484/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: nemysis@openSUSE.org
          Reporter: kbabioch-at-suse.com
        QA Contact: security-team-at-suse.de
                CC: mimi.vx-at-gmail.com
          Found By: Security Response Team
           Blocker: ---

CVE-2018-19387

format_cb_pane_tabs in format.c in tmux 2.7 through 2.8 might allow attackers
to
cause a denial of service (NULL Pointer Dereference and application crash) by
arranging for a malloc failure.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-19387
http://www.cvedetails.com/cve/CVE-2018-19387/
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19387
https://github.com/tmux/tmux/issues/1547
https://github.com/openbsd/src/commit/b32e1d34e10a0da806823f57f02a4ae6e93d756e


--1542811062.Dd0A770.26456
Date: Wed, 21 Nov 2018 14:37:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116917
           Summary: claws-mail: address and quoted message inconsistent in reply
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Maintenance
          Assignee: msuchanek-at-suse.com
          Reporter: astieger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3889

In split view it is possible that the highlighted message in the folder view is
different from the message shown in the message view. Hitting reply quotes the
message shown to the author of the message selected in folder view. claws-mail
may thus reply to "random" recipients.

https://build.opensuse.org/request/show/650704


--1542812396.322C9.31032
Date: Wed, 21 Nov 2018 14:59:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1116922
           Summary: [rn] amanda - amanda user (and group) should be considered privileged user
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Release Notes
          Assignee: sknorr-at-suse.com
          Reporter: kstreitova-at-suse.com
        QA Contact: lnussel-at-suse.com
          Found By: ---
           Blocker: ---

I would like to add a section to openSUSE:Leap:15.1 release notes about amanda.

Draft
-----
We currently limit the execution of the binaries in this package to the
group amanda. Some of the binaries are setuid root. As the implementation
of these binaries is partially problematic, the user amanda and members
of the group amanda should be considered privileged users with equivalent
permissions to the root user.


body:
Build Identifier:

Several man pages to configuration files are missing.
for example man passwd show only passwd(1) and passwd(1ssl), but there is no
passwd(5). The same problem by several other commandos. For expample man ps
doesn't show ps (1p) anymore.
I have installed all updates, rebooted and afterwards executed manddb. No
change.

Reproducible: Always

Steps to Reproduce:
1.man 5 paswd
2.man 1p ps
3.

pkgs: man-pages man-pages-posix

summary: Several Manpages are missing


--1542961467.fbdd50.22886
Date: Fri, 23 Nov 2018 08:24:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117105
           Summary: VUL-1: CVE-2018-19443: The client tries to make a connection to the bus in cleartext instead of encrypted under certain circumstances
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/219589/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: axel.braun-at-gmx.de
          Reporter: rfrohl-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-19443

The client in Tryton 5.x before 5.0.1 tries to make a connection to the bus in
cleartext instead of encrypted under certain circumstances in bus.py and
jsonrpc.py. This connection attempt fails, but it contains in the header the
current session of the user. This session could then be stolen by a
man-in-the-middle.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-19443
http://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-19443.html
https://discuss.tryton.org/t/security-release-for-issue7792/830
https://bugs.tryton.org/issue7792


body:
--1542965622.0F0BCb30.25366
Date: Fri, 23 Nov 2018 09:33:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117121
           Summary: [METABUG] Update guile to 2.2 on Tumbleweed
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: jbrielmaier-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

This bug is intended to track the progress of updating guile to version 2.2 on
Tumbleweed/Factory.

pkgs: gnutls guile


body:
--1542972494.D14bD0E0.7736
Date: Fri, 23 Nov 2018 11:28:14 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117147
           Summary: chrony environment file does not exist
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: manfred.h-at-gmx.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Installing the chrony package does not generate the /etc/sysconfig/chronyd
file, which is referenced by /usr/lib/systemd/system/chronyd.service

Reason is the RPM postinstall script which looks for
/var/adm/fillup-templates/sysconfig.chrony; here is the excerpt from the
postinstall script:

    PNAME=chrony
    SUBPNAME=
    TEMPLATE_DIR=/var/adm/fillup-templates
    SYSC_TEMPLATE=$TEMPLATE_DIR/sysconfig.$PNAME$SUBPNAME
    SD_NAME=""
    ...
        if [ -f $SYSC_TEMPLATE ] ; then
            echo "Updating /etc/sysconfig/$SD_NAME$PNAME..."
            mkdir -p /etc/sysconfig/$SD_NAME
            touch /etc/sysconfig/$SD_NAME$PNAME
            /bin/fillup -q /etc/sysconfig/$SD_NAME$PNAME $SYSC_TEMPLATE
        fi

Unfortunately, the packaged file is named
/var/adm/fillup-templates/sysconfig.chronyd

The suggested fix would be to set PNAME=chronyd to make it work.

summary: chrony environment file does not exist


body:
--1542979999.e68E0.30529
Date: Fri, 23 Nov 2018 13:33:19 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117169
           Summary: [doc]
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Documentation
          Assignee: fs-at-suse.com
          Reporter: bezdek-at-gmail.com
        QA Contact: fs-at-suse.com
          Found By: ---
           Blocker: ---

12.2.2.1  Adding a Network Bridge

https://doc.opensuse.org/documentation/leap/virtualization/html/book.virt/cha.libvirt.networks.html#libvirt.networks.bridged.add.brctl.add

# is in done
ip link add name VIRBR_TEST

# should be:
ip link add name VIRBR_TEST type bridge

summary: [doc]


body:
--1542996609.eFfbEe0.31420
Date: Fri, 23 Nov 2018 18:10:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117195
           Summary: LibreOfficeKit header file missing
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LibreOffice
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: anoncvs-at-mailinator.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The package libreofficekit-devel is missing the header file LibreOfficeKit.hxx
which is needed to correctly use LibreOfficeKit from C++.

The problem is caused by this part of the spec file

# Libreofficekit headers
mkdir -p %{buildroot}%{_includedir}/LibreOfficeKit/
install -m 0644 include/LibreOfficeKit/*.h
%{buildroot}%{_includedir}/LibreOfficeKit/

which only installs the .h files (for C) and not the .hxx file (for C++).

Simplifying that to

# Libreofficekit headers
mkdir -p %{buildroot}%{_includedir}/LibreOfficeKit/
install -m 0644 include/LibreOfficeKit/*
%{buildroot}%{_includedir}/LibreOfficeKit/

should solve the issue.

There are no files in that directory other than the headers.

summary: LibreOfficeKit header file missing


--1543235341.5163a3312.25202
Date: Mon, 26 Nov 2018 12:29:01 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117316
           Summary: XMLListModel QML support missing from Qt 5.12
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: noeerover-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After the update in unstable repos Plasma/Qt to Qt5.12 on Tumbleweed, all of my
QML apps that use XmlListModel are failing, due to "type not found", basically
XMLListModel 2.0 is not installed.

It appears that the /usr/lib64/qt5/qml/QtQuick/XmlListModel folder is not
installed with the Qt5.12 upgrade.

On the previous Qt 5.11.2 (unstable and stable repos), the QtQuick/XmlListModel
is present and installed properly per folder above.


--1543249595.635CBE0.29256
Date: Mon, 26 Nov 2018 16:26:35 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117355
           Summary: libgcrypt runs selfcheck including hmac based binary verifcation outside fips mode. breaks keepassxc
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: vcizek-at-suse.com
          Reporter: mrueckert-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

(gdb) bt
#0  0x00007ffff6b03110 in _gcry_fips_run_selftests (extended=1) at fips.c:722
#1  0x00007ffff6af8889 in gcry_control (cmd=cmd@entry=GCRYCTL_SELFTEST) at
visibility.c:79
#2  0x00005555555b987b in Crypto::backendSelfTest() () at
/usr/src/debug/keepassxc-2.3.4+git194.a67cac13-38.1.x86_64/src/crypto/Crypto.cpp:78
#3  0x00005555555b987b in Crypto::init() () at
/usr/src/debug/keepassxc-2.3.4+git194.a67cac13-38.1.x86_64/src/crypto/Crypto.cpp:53
#4  0x00005555555ab457 in main(int, char**) (argc=<optimized out>,
argv=<optimized out>) at
/usr/src/debug/keepassxc-2.3.4+git194.a67cac13-38.1.x86_64/src/main.cpp:101

This also affects SLE15/Leap15


--1543328447.E2121.16505
Date: Tue, 27 Nov 2018 14:20:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117483
           Summary: openvswitch: please consider dropping the use of DISABLE_STOP_ON_REMOVAL/DISABLE_RESTART_ON_UPDATE
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hi Jaime,

After a discussion with Markos, it appears that the use of both
DISABLE_STOP_ON_REMOVAL=yes and DISABLE_RESTART_ON_UPDATE=yes in
openvswitch.spec is not needed at all.

Regarding DISABLE_RESTART_ON_UPDATE=yes and according to Markos, OVS services
can now be restarted on package updates because "it's being handled by the
upper layers from crowbar or whatever else management tool they use".

Even if the package would still need to be restarted on updates,
%systemd_postun_with_restart() or %systemd_postun() macros should be used
instead of the env variable.

Regarding DISABLE_STOP_ON_REMOVAL=yes: this was actually an "addon" on the
previous issue but it's not needed at all. It would be nice if it could be
dropped especially since a) leaving a daemon running while all its files
(binaries, libs, config files, etc...) have been deleted may obviously lead to
crashes b) one can expect that the network is going down if a package such as
openvswitch is removed.

Thanks.


--1543330457.6cDC0a0.6160
Date: Tue, 27 Nov 2018 14:54:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117489
           Summary: Consider dropping the use of YAST_IS_RUNNING in systemd rpm macros
    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: fbui-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

In my understanding "YAST_IS_RUNNING" is used by the systemd rpm macros to
prevent (re)starting/stopping services from installation environments.

However systemctl turns most commands into NOPs when it detects that it's run
inside a chroot.

And in cases the logic to detect chroot doesn't work in the installer
environment then exporting SYSTEMD_OFFLINE environment variable can still force
systemctl to assume that it runs inside a chroot.

So it seems that we could simplify systemd rpm macros and drop
"YAST_IS_RUNNING".

YaST team do you think that would be possible ?

Thanks.


body:
--1543332979.257aD2d0.3621
Date: Tue, 27 Nov 2018 15:36:19 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117499
           Summary: checkmedia 4 breaks livecd builds
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Basesystem
          Assignee: snwint-at-suse.com
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Builds fail with
(https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.1:Images/livecd-leap-x11/images/x86_64):

[  694s] [ DEBUG   ]: 21:49:07 | EXEC: [tagmedia --md5 --check --pad 150
/usr/src/packages/KIWI-iso/openSUSE-Leap-15.1-Rescue-CD.x86_64-2.8.0.iso]
[  695s] [ DEBUG   ]: 21:49:08 | EXEC: Failed with stderr:
/usr/src/packages/KIWI-iso/openSUSE-Leap-15.1-Rescue-CD.x86_64-2.8.0.iso: read
error
[  695s] , stdout: (no output on stdout)
[  695s] [ ERROR   ]: 21:49:08 | KiwiCommandError: tagmedia: stderr:
/usr/src/packages/KIWI-iso/openSUSE-Leap-15.1-Rescue-CD.x86_64-2.8.0.iso: read
error

Building against checkmedia from openSUSE:Leap:15.0 works fine.

summary: checkmedia 4 breaks livecd builds


body:
--1543409819.CA4010.30885
Date: Wed, 28 Nov 2018 12:56:59 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117647
           Summary: update-checker is broken out of the box
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Maintenance
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: mstelios-at-cytech.gr
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

hello,

i installed update-checker on tumbleweed and tried to run it with no success.

following is the problem:

# update-checker
Unsuccessful stat on filename containing newline at
/usr/lib/perl5/vendor_perl/5.26.2/XML/Twig.pm line 772.

syntax error at line 1, column 0, byte 0 at
/usr/lib/perl5/vendor_perl/5.26.2/x86_64-linux-thread-multi/XML/Parser.pm line
187.
 at /usr/sbin/update-checker line 147.

summary: update-checker is broken out of the box


body:
--1543490565.ccCFF8258.6948
Date: Thu, 29 Nov 2018 11:22:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117774
           Summary: Update prosody to 0.10.3 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: 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: ---

In Leap 15.0 we have prosody 0.10.2.

Yesterday https://blog.prosody.im/prosody-0-10-3-released/ (and
https://blog.prosody.im/prosody-0-11-1-released/) got released.

We should have use 0.10.3 for Leap 15.0 to have the latest fixes.

summary: Update prosody to 0.10.3 in Leap 15.0


--1543517325.2FB7A3.3937
Date: Thu, 29 Nov 2018 18:48:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1117846
           Summary: virt-manager: Checking for virtualization packages error
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: carnold-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Starting virt-manager on a KVM host shows this message where defined VMs
should be listed:  "Checking for virtualization packages...". The message
never goes away.

This is caused by a broken forward ported of a patch to version 2.0.0.


--1543913594.32C76.24055
Date: Tue, 4 Dec 2018 08:53:14 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1118279
           Summary: os-prober unconditionally pulls btrfsprogs
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Bootloader
          Assignee: mchang-at-suse.com
          Reporter: jdelvare-at-suse.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

If the system does not have any btrfs partition then btrfsprogs is useless.
However, it is required by os-prober and can't be uninstalled due to this hard
dependency.

Can we please downgrade this requirement to a recommendation or suggestion?


--1543920491.15880.8719
Date: Tue, 4 Dec 2018 10:48:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1118301
           Summary: VUL-1: CVE-2018-19797: NULL Pointer Dereference in the function Sass:Selector_List:populate_extends in SharedPtr.hpp may cause a Denial of Service
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/220050/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: rfrohl-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-19797

In LibSass 3.5.5, a NULL Pointer Dereference in the function
Sass::Selector_List::populate_extends in SharedPtr.hpp (used by ast.cpp and
ast_selectors.cpp) may cause a Denial of Service (application crash) via a
crafted sass input file.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-19797
https://github.com/sass/libsass/issues/2779


--1543930574.25dc00.11493
Date: Tue, 4 Dec 2018 13:36:14 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1118327
           Summary: Nextcloud client 100% cpu and crash at exit
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          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: ---

Since 2.5.0 release, I'm seeing that kind of mis-behaviour of nextcloud client

100% cpu used, then crash if exit

Application: nextcloud (nextcloud), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd863df7f80 (LWP 2153))]

Thread 10 (Thread 0x7fd846ffd700 (LWP 12468)):
#0  0x00007fd86ea748c8 in futex_reltimed_wait_cancelable (private=0,
reltime=0x7fd846ffca10, expected=0, futex_word=0x7fd834006e54) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x00007fd86ea748c8 in __pthread_cond_wait_common (abstime=0x7fd846ffcad0,
mutex=0x7fd834006e00, cond=0x7fd834006e28) at pthread_cond_wait.c:533
#2  0x00007fd86ea748c8 in __pthread_cond_timedwait (cond=0x7fd834006e28,
mutex=0x7fd834006e00, abstime=0x7fd846ffcad0) at pthread_cond_wait.c:667
#3  0x00007fd86f6df04c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#4  0x00007fd86f6d6eb2 in  () at /usr/lib64/libQt5Core.so.5
#5  0x00007fd86f6de9b7 in  () at /usr/lib64/libQt5Core.so.5
#6  0x00007fd86ea6e554 in start_thread (arg=<optimized out>) at
pthread_create.c:463
#7  0x00007fd86ee10ccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7fd854fb5700 (LWP 8947)):
#0  0x00007fd86ee122c7 in socket () at ../sysdeps/unix/syscall-template.S:78
#1  0x00007fd8708253fb in  () at /usr/lib64/libQt5Network.so.5
#2  0x00007fd870823b9e in  () at /usr/lib64/libQt5Network.so.5
#3  0x00007fd8708114da in  () at /usr/lib64/libQt5Network.so.5
#4  0x00007fd8708127a2 in  () at /usr/lib64/libQt5Network.so.5
#5  0x00007fd870812ccf in  () at /usr/lib64/libQt5Network.so.5
#6  0x00007fd870813185 in QAbstractSocket::connectToHost(QString const&,
unsigned short, QFlags<QIODevice::OpenModeFlag>,
QAbstractSocket::NetworkLayerProtocol) () at /usr/lib64/libQt5Network.so.5
#7  0x00007fd87084c7a5 in QSslSocket::connectToHost(QString const&, unsigned
short, QFlags<QIODevice::OpenModeFlag>, QAbstractSocket::NetworkLayerProtocol)
() at /usr/lib64/libQt5Network.so.5
#8  0x00007fd87084bfaf in QSslSocket::connectToHostEncrypted(QString const&,
unsigned short, QFlags<QIODevice::OpenModeFlag>,
QAbstractSocket::NetworkLayerProtocol) () at /usr/lib64/libQt5Network.so.5
#9  0x00007fd8707c6ea0 in  () at /usr/lib64/libQt5Network.so.5
#10 0x00007fd8707c1872 in  () at /usr/lib64/libQt5Network.so.5
#11 0x00007fd86f8b0932 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#12 0x00007fd8702274a1 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#13 0x00007fd87022eaf0 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#14 0x00007fd86f886e29 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#15 0x00007fd86f889e1b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#16 0x00007fd86f8d94d3 in  () at /usr/lib64/libQt5Core.so.5
#17 0x00007fd87a554c15 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#18 0x00007fd87a554fd8 in  () at /usr/lib64/libglib-2.0.so.0
#19 0x00007fd87a55506c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#20 0x00007fd86f8d8b03 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#21 0x00007fd86f885afb in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#22 0x00007fd86f6d4de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#23 0x00007fd86f6de9b7 in  () at /usr/lib64/libQt5Core.so.5
#24 0x00007fd86ea6e554 in start_thread (arg=<optimized out>) at
pthread_create.c:463
#25 0x00007fd86ee10ccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7fd8467fc700 (LWP 2764)):
#0  0x00007fd86ea757d0 in __GI___pthread_getspecific (key=13) at
pthread_getspecific.c:30
#1  0x00007fd87a57d950 in g_thread_self () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fd87a55505d in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x00007fd86f8d8b1b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#4  0x00007fd86f885afb in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#5  0x00007fd86f6d4de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007fd86f6de9b7 in  () at /usr/lib64/libQt5Core.so.5
#7  0x00007fd86ea6e554 in start_thread (arg=<optimized out>) at
pthread_create.c:463
#8  0x00007fd86ee10ccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7fd847fff700 (LWP 2565)):
#0  0x00007fd87a59bda4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x00007fd87a554f06 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fd87a5552d2 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#3  0x00007fd87a375b16 in  () at /usr/lib64/libgio-2.0.so.0
#4  0x00007fd87a57d476 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x00007fd86ea6e554 in start_thread (arg=<optimized out>) at
pthread_create.c:463
#6  0x00007fd86ee10ccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7fd8557b6700 (LWP 2563)):
#0  0x00007fd86ee01d34 in __GI___libc_read (fd=28, buf=0x7fd8557b5a90,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x00007fd87a59aa00 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fd87a554a4b in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x00007fd87a554ef0 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x00007fd87a55506c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x00007fd87a5550b1 in  () at /usr/lib64/libglib-2.0.so.0
#6  0x00007fd87a57d476 in  () at /usr/lib64/libglib-2.0.so.0
#7  0x00007fd86ea6e554 in start_thread (arg=<optimized out>) at
pthread_create.c:463
#8  0x00007fd86ee10ccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fd857b3b700 (LWP 2210)):
#0  0x00007fd86ee01d34 in __GI___libc_read (fd=21, buf=0x7fd857b3a930,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x00007fd87a59aa00 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fd87a554a4b in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x00007fd87a554ef0 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x00007fd87a55506c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x00007fd86f8d8b1b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#6  0x00007fd86f885afb in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#7  0x00007fd86f6d4de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x00007fd86f6de9b7 in  () at /usr/lib64/libQt5Core.so.5
#9  0x00007fd86ea6e554 in start_thread (arg=<optimized out>) at
pthread_create.c:463
#10 0x00007fd86ee10ccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fd85833c700 (LWP 2209)):
#0  0x00007fd86ee01d34 in __GI___libc_read (fd=19, buf=0x7fd85833b900,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x00007fd87a59aa00 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fd87a554a4b in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x00007fd87a554ef0 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x00007fd87a55506c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x00007fd86f8d8b1b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#6  0x00007fd86f885afb in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#7  0x00007fd86f6d4de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x00007fd87a00f545 in  () at /usr/lib64/libQt5DBus.so.5
#9  0x00007fd86f6de9b7 in  () at /usr/lib64/libQt5Core.so.5
#10 0x00007fd86ea6e554 in start_thread (arg=<optimized out>) at
pthread_create.c:463
#11 0x00007fd86ee10ccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fd860be9700 (LWP 2201)):
#0  0x00007fd86ee062c9 in __GI___poll (fds=0x7fd860be8a78, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007fd86c96ecc7 in  () at /usr/lib64/libxcb.so.1
#2  0x00007fd86c9708ea in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x00007fd8616ca519 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007fd86f6de9b7 in  () at /usr/lib64/libQt5Core.so.5
#5  0x00007fd86ea6e554 in start_thread (arg=<optimized out>) at
pthread_create.c:463
#6  0x00007fd86ee10ccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fd862400700 (LWP 2199)):
#0  0x00007fd86ea744dc in futex_wait_cancelable (private=0, expected=0,
futex_word=0x7fd8736ddf30) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x00007fd86ea744dc in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55f61cd5f780, cond=0x7fd8736ddf08) at pthread_cond_wait.c:502
#2  0x00007fd86ea744dc in __pthread_cond_wait (cond=0x7fd8736ddf08,
mutex=0x55f61cd5f780) at pthread_cond_wait.c:655
#3  0x00007fd86f54187c in
std::condition_variable::wait(std::unique_lock<std::mutex>&) () at
/usr/lib64/libstdc++.so.6
#4  0x00007fd872c362d2 in  () at /usr/lib64/libQt5WebKit.so.5
#5  0x00007fd872c363eb in  () at /usr/lib64/libQt5WebKit.so.5
#6  0x00007fd86f5470bf in  () at /usr/lib64/libstdc++.so.6
#7  0x00007fd86ea6e554 in start_thread (arg=<optimized out>) at
pthread_create.c:463
#8  0x00007fd86ee10ccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fd863df7f80 (LWP 2153)):
[KCrash Handler]
#6  0x00007fd87a37f2a8 in g_dbus_object_get_object_path () at
/usr/lib64/libgio-2.0.so.0
#7  0x00007fd87a09ac1d in cloud_providers_provider_exporter_remove_account ()
at /usr/lib64/libcloudproviders.so.0
#8  0x000055f61b5bc2b1 in
CloudProviderManager::slotFolderListChanged(QMap<QString, OCC::Folder*> const&)
(this=0x55f61d4f4840, folderMap=...) at
/usr/src/debug/nextcloud-client-2.5.0-1.1.x86_64/src/gui/cloudproviders/cloudprovidermanager.cpp:57
#9  0x00007fd86f8b007b in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#10 0x000055f61b5c4aa5 in OCC::FolderMan::folderListChanged(QMap<QString,
OCC::Folder*> const&) (this=this@entry=0x55f61d220220, _t1=...) at
/usr/src/debug/nextcloud-client-2.5.0-1.1.x86_64/build/src/gui/nextcloud_autogen/EWIEGA46WW/moc_folderman.cpp:286
#11 0x000055f61b4ed591 in OCC::FolderMan::unloadAndDeleteAllFolders()
(this=0x55f61d220220) at
/usr/src/debug/nextcloud-client-2.5.0-1.1.x86_64/src/gui/folderman.cpp:143
#12 0x000055f61b4d1d83 in OCC::Application::slotCleanup() (this=0x7fff0ed48160)
at /usr/src/debug/nextcloud-client-2.5.0-1.1.x86_64/src/gui/application.cpp:308
#13 0x00007fd86f8b01d0 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#14 0x00007fd86f886007 in
QCoreApplication::aboutToQuit(QCoreApplication::QPrivateSignal) () at
/usr/lib64/libQt5Core.so.5
#15 0x00007fd86f88a2a9 in QCoreApplicationPrivate::execCleanup() () at
/usr/lib64/libQt5Core.so.5
#16 0x00007fd86f88dc8b in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#17 0x000055f61b4bc79c in main(int, char**) (argc=<optimized out>,
argv=<optimized out>) at
/usr/src/debug/nextcloud-client-2.5.0-1.1.x86_64/src/gui/main.cpp:167
[Inferior 1 (process 2153) detached]

Running it again doesn't show this crash always.
Mostly happen after suspend and network changes.


--1543935048.dd2Bd0.28267
Date: Tue, 4 Dec 2018 14:50:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1118346
           Summary: VUL-1: CVE-2018-19827: libsass: a use-after-free vulnerability exists in the SharedPtr class in SharedPtr.cpp (or SharedPtr.hpp) that may cause a denial of service or possibly have unspecified other impact
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/220096/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: cbosdonnat-at-suse.com
          Reporter: rfrohl-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-19827

In LibSass 3.5.5, a use-after-free vulnerability exists in the
SharedPtr class in SharedPtr.cpp (or SharedPtr.hpp) that may cause a
denial of service (application crash) or possibly have unspecified
other impact.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-19827
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19827


--1543935126.AdBEF0.28060
Date: Tue, 4 Dec 2018 14:52:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1118348
           Summary: VUL-1: CVE-2018-19837: libsass: Sass:Eval:operator()(Sass:Binary_Expression*) inside eval.cpp allows attackers to cause a denial-of-service resulting from stack consumption via a crafted sass file
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/220099/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: cbosdonnat-at-suse.com
          Reporter: rfrohl-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-19837

In LibSass prior to 3.5.5,
Sass::Eval::operator()(Sass::Binary_Expression*) inside eval.cpp allows
attackers to cause a denial-of-service resulting from stack consumption
via a crafted sass file, because of certain incorrect parsing of '%' as
a modulo operator in parser.cpp.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-19837
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19837


--1543935193.411811.28066
Date: Tue, 4 Dec 2018 14:53:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1118349
           Summary: VUL-1: CVE-2018-19838: libsass: functions inside ast.cpp for IMPLEMENT_AST_OPERATORS expansion allow attackers to cause a denial-of-service resulting from stack consumption via a crafted sass file
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/220100/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: cbosdonnat-at-suse.com
          Reporter: rfrohl-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-19838

In LibSass prior to 3.5.5, functions inside ast.cpp for
IMPLEMENT_AST_OPERATORS expansion allow attackers to cause a
denial-of-service resulting from stack consumption via a crafted sass
file, as demonstrated by recursive calls involving clone(),
cloneChildren(), and copy().

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-19838
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19838


--1543935370.D38250e0.29984
Date: Tue, 4 Dec 2018 14:56:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1118351
           Summary: VUL-1: CVE-2018-19839: libsass: the function handle_error in sass_context.cpp allows attackers to cause a denial-of-service resulting from a heap-based buffer over-read via a crafted sass file
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/220101/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: cbosdonnat-at-suse.com
          Reporter: rfrohl-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2018-19839

In LibSass prior to 3.5.5, the function handle_error in
sass_context.cpp allows attackers to cause a denial-of-service
resulting from a heap-based buffer over-read via a crafted sass file.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-19839
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19839


body:
Build Identifier:

I recently installed Tumbleweed on an external USB drive).  I installed using
"grub2" and booting from the MBR.  But I wanted to also be able to boot this
external drive from a UEFI system.

Here's what I attempted:

# shim-install --no-nvram --removable
copying /usr/lib64/efi/grub.efi to /boot/efi/EFI/boot/grub.efi
Installing for i386-pc platform.
/usr/sbin/grub2-install: error: install device isn't specified.

Evidently, "shim-install" is internally calling "grub2-install".  But it is
calling it the wrong way.  It should be calling with "--target=x86_64-efi"

To work around the problem, I manually did what shim-install should have done:

# grub2-install --target=x86_64-efi --no-nvram --removable
Installing for x86_64-efi platform.
Installation finished. No error reported.

I then repeated the same "shim-install" command as used earlier, with the same
error message.  But the combination seems to have done what I wanted.  I have
successfully booted from that external drive on both a legacy BIOS system and
on a UEFI system.

Reproducible: Always

summary: shim-install is broken