body:
--1507539894.cCF2a7F35.13852
Date: Mon, 9 Oct 2017 09:04:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062237
           Summary: excessive build time for python-Cython
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: jmatejek-at-suse.com
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: amajer-at-suse.com
          Found By: ---
           Blocker: ---

Looking at the rebuild graph of Leap 15 we can see that python-Cython blocks a
lot of packages. It takes 2 hours to build due to the excessive test suite.
Would it be possible to split the tests out to a 2nd spec file?

summary: excessive build time for python-Cython


body:
--1507540955.d1f2ecd15.16447
Date: Mon, 9 Oct 2017 09:22:35 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062244
           Summary: NIS login is broken since Tumbleweed update 20171006
    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: idonmez-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: kukuk-at-suse.com
          Found By: ---
           Blocker: ---

Splitting off from bsc#1059065

Since the latest update I can't login to my machine with my NIS username, says
username is not found.

ypcat passwd works.
getent passwd works.

nscd is running with a probable fatal warning:

Oct 09 11:20:34 havana nscd[944]: rpc: failed to open /etc/netconfig

The file is there and the permissions look correct:

havana ~ # ls -al /etc/netconfig
                                                 -rw-r--r

pkgs: apparmor glibc


body:
--1507551200.aAF50.3046
Date: Mon, 9 Oct 2017 12:13:20 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062303
           Summary: trackerbug: packages do not build reproducibly from randomness
    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: bwiedemann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Development
           Blocker: ---

See also https://reproducible-builds.org/

When packages write random bytes into files that are packaged
it results in binaries that differ on every build.
These thus trigger rebuilds of depending packages
and are published to mirrors and users
when actually nothing really changed.

pkgs: doxygen ipxe kernel-source python-yarl syslinux


--1507626894.8df4EFB40.12350
Date: Tue, 10 Oct 2017 09:14:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062482
           Summary: Problem with autofs ... mount points bail out
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Factory
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: werner-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

It happens that mount points like /mounts/dist become and remain disappeared if
not accessed at all times


body:
--1507638158.cB3d0.29517
Date: Tue, 10 Oct 2017 12:22:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062550
           Summary: Compose Key changes
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Release Notes
          Assignee: sknorr-at-suse.com
          Reporter: sndirsch-at-suse.com
        QA Contact: lnussel-at-suse.com
        Depends on: 1062549
          Found By: ---
           Blocker: ---

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

Could you please add to the release notes, that with sle15/Leap 15 we no longer
have a compose key defined by default? Seems it became impossible for editing
files after more than a decade, if Shift-RCTRL is defined as such a key
(bsc#1059438).

The Compose key still can be defined via /etc/X11/Xmodmap (for the whole
system) ...

/etc/X11/Xmodmap
[...]
!! Third example: Change right Control key to Compose key.
!! To do Compose Character, press this key and afterwards two
!! characters (e.g. `a' and `^' to get 342).
!remove  Control  = Control_R
!keysym Control_R = Multi_key
!add     Control  = Control_R
[...]

... or user specific by using the desktop's keyboard graphical configuration.
Or for the power desktop user via setxkbmap.

  setxkbmap [...] -option compose:<compose_key>

     <compose_key> e.g. ralt, lwin, rwin, menu, rctl, caps, etc.

As alternative the user can also use an appropritate input method (via ibus).

summary: Compose Key changes


body:
--1507646335.0D5e0d0.26781
Date: Tue, 10 Oct 2017 14:38:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062583
           Summary: [TRACKER BUG] Stop using boost-devel
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: amajer-at-suse.com
          Reporter: amajer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Boost package is a large collection of libraries and utilities. As such, most
of them are quite independent of each other. Majority, are header only
variants. A small minority of Boost libraries require compilation. Some of
these compiled libraries depend on complex libraries, like OpenMPI and Python.

100s of various software packages depend on various components of Boost. Most
of these depend only on a small subset of commonly used libraries. Currently
boost provides a boost-devel subpackage that pulls in the entire dependency
tree of boost. This results in many packages waiting for unnecessary libraries
to be built prior to them being buildable. It also results in unnecessary
rebuilds.

To avoid this unnecessary dependency chain, the current plan is to drop
boost-devel entirely and it have provided by libboost_headers-devel. This means
if your package still depends on boost-devel and requires compiled Boost
libraries, it will stop building.

summary: [TRACKER BUG] Stop using boost-devel


body:
--1507662534.bD800.31303
Date: Tue, 10 Oct 2017 19:08:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062631
           Summary: stop mime-info and mimelnk support
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: sbrabec-at-suse.cz
          Reporter: sbrabec-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

mime-info is an ancient MIME type definition format. It was used by GNOME 1
only. Now it is replaced by shared-mime-info. It is obsolete since 2002.

Also mimelnk is an obsolete MIME type definition format. It was used by KDE 1,
2 and 3. Now it is replaced by shared-mime-info. It is obsolete since 2009.

But there are several packages that still provide these files:

mime-info:
compiz-emerald
genius
grisbi
mysql-workbench
gnome-mime-data
libreoffice

These provide it only by upstream:
cherrytree
dia
gramps
homebank

mimelnk:
ambas3
kdebase3
kdebase3-SuSE
kdeedu3
kdegames3
kdelibs3
kdemultimedia3
kdenetwork3
kdepim3
kdesdk3
kdeutils3
kdewebdev3
kde3-basket
kde3-kaffeine
kicad
ksimus
libreoffice
obconf
pcb
qelectrotech
scribus
sonic-visualiser
treeline
xournal
yast2-metapackage-handler

shared-mime-info: Contains supplementary conversion script mime-info-to-mime.

summary: stop mime-info and mimelnk support


--1507674944.1Ed7f20.12643
Date: Tue, 10 Oct 2017 22:35:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062667
           Summary: yast2-apparmor: "view changes" doesn't do anything
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE 42.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: rgoldwyn-at-suse.com
          Reporter: suse-beta-at-cboltz.de
        QA Contact: jsrain-at-suse.com
          Found By: Beta-Customer
           Blocker: ---

After updating some profiles with YaST, you finally get to the sreen showing
the list of changed profiles.

I noticed two issues there:

a)
The profiles are displayed as
    (x) ["/usr/bin/man", true]
instead of just
    (x) /usr/bin/man

b)
Clicking "View Changes" or "View Changes b/w Clean profiles" does nothing.
Well, the window flickers, but I get the same dialog again - without being able
to see the changes.


body:
--1507703298.4004a0.25836
Date: Wed, 11 Oct 2017 06:28:18 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062691
           Summary: No copy and past with vim
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Factory
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: werner-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I'd like to use copy text from an other window and insert this in vim. For this
I do copy text with the mouse, press i for insert in vim and let drop the
current cut buffer with the right mouse button ... and see `v' instead of the
text which is still in the cutt buffer

This break my workflow!

summary: No copy and past with vim


--1507723623.070bC29.30979
Date: Wed, 11 Oct 2017 12:07:03 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062774
           Summary: clFFT: Please stop BuildRequire on boost-devel
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: mpluskal-at-suse.com
          Reporter: amajer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1062583
          Found By: ---
           Blocker: ---

clFFT current BuildRequires boost-devel. This package is going to be dropped
since it pulls in too many unnecessary runtimes. This change will cause your
package to stop building. Please fix.

See Bug 1062583 for rationale.

https://build.opensuse.org/package/show/home:adamm:branches:devel:libraries:c_c++/clFFT


--1507725801.Bd13E74.8124
Date: Wed, 11 Oct 2017 12:43:21 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062799
           Summary: swift-im: Please stop BuildRequire on boost-devel
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: jubalh-at-openmailbox.org
          Reporter: amajer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1062583
          Found By: ---
           Blocker: ---

swift-im current BuildRequires boost-devel. This package is going to be dropped
since it pulls in too many unnecessary runtimes. This change will cause your
package to stop building. Please fix.

See Bug 1062583 for rationale.

https://build.opensuse.org/package/show/home:adamm:branches:devel:libraries:c_c++/swift-im


--1507726487.1f54e00.10476
Date: Wed, 11 Oct 2017 12:54:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062807
           Summary: TuxGuitar doesn't start after the latest update
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: x86-64
                OS: openSUSE Factory
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: 3rd party software
          Assignee: opensuse-communityscreening-at-forge.provo.novell.com
          Reporter: dener.kup-at-gmail.com
        QA Contact: opensuse-communityscreening-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

I have a problem after the last update. TuxGuitar doesn't start as it has
32-bit SWT library inside, but I have 64-bit JVM. But the version I've
installed is x86_64.

To check the stuff I downloaded a tuxguitar package from sourceforge and it
works.

Below outputs of different commands go:

$ tuxguitar
java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM
        at org.eclipse.swt.internal.Library.loadLibrary(Library.java:263)
        at org.eclipse.swt.internal.Library.loadLibrary(Library.java:240)
        at org.eclipse.swt.internal.C.<clinit>(C.java:21)
        at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63)
        at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54)
        at org.eclipse.swt.widgets.Display.<clinit>(Display.java:133)
        at
org.herac.tuxguitar.ui.swt.SWTApplication.<init>(SWTApplication.java:15)
        at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
        at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)
        at java.base/java.lang.Class.newInstance(Class.java:558)
        at
org.herac.tuxguitar.util.TGServiceReader$IteratorImpl.next(TGServiceReader.java:91)
        at
org.herac.tuxguitar.app.ui.TGApplication.lookupApplication(TGApplication.java:32)
        at
org.herac.tuxguitar.app.ui.TGApplication.<init>(TGApplication.java:24)
        at
org.herac.tuxguitar.app.ui.TGApplication$1.createInstance(TGApplication.java:56)
        at
org.herac.tuxguitar.app.ui.TGApplication$1.createInstance(TGApplication.java:54)
        at
org.herac.tuxguitar.util.singleton.TGSingletonUtil.getInstance(TGSingletonUtil.java:12)
        at
org.herac.tuxguitar.app.ui.TGApplication.getInstance(TGApplication.java:54)
        at
org.herac.tuxguitar.app.synchronizer.TGSynchronizerControllerImpl.<init>(TGSynchronizerControllerImpl.java:17)
        at
org.herac.tuxguitar.app.TuxGuitar.createUIContext(TuxGuitar.java:113)
        at
org.herac.tuxguitar.app.TuxGuitar.createApplication(TuxGuitar.java:100)
        at org.herac.tuxguitar.app.TGMain.main(TGMain.java:13)
Exception in thread "main" java.util.NoSuchElementException
        at
org.herac.tuxguitar.util.TGServiceReader$IteratorImpl.next(TGServiceReader.java:98)
        at
org.herac.tuxguitar.app.ui.TGApplication.lookupApplication(TGApplication.java:32)
        at
org.herac.tuxguitar.app.ui.TGApplication.<init>(TGApplication.java:24)
        at
org.herac.tuxguitar.app.ui.TGApplication$1.createInstance(TGApplication.java:56)
        at
org.herac.tuxguitar.app.ui.TGApplication$1.createInstance(TGApplication.java:54)
        at
org.herac.tuxguitar.util.singleton.TGSingletonUtil.getInstance(TGSingletonUtil.java:12)
        at
org.herac.tuxguitar.app.ui.TGApplication.getInstance(TGApplication.java:54)
        at
org.herac.tuxguitar.app.synchronizer.TGSynchronizerControllerImpl.<init>(TGSynchronizerControllerImpl.java:17)
        at
org.herac.tuxguitar.app.TuxGuitar.createUIContext(TuxGuitar.java:113)
        at
org.herac.tuxguitar.app.TuxGuitar.createApplication(TuxGuitar.java:100)
        at org.herac.tuxguitar.app.TGMain.main(TGMain.java:13)

$ java -version
openjdk version "9"
OpenJDK Runtime Environment (build 9+181-suse-2.1-x8664)
OpenJDK 64-Bit Server VM (build 9+181-suse-2.1-x8664, mixed mode)

$ rpm -qa tuxguitar
tuxguitar-1.4-2.1.x86_64

$ zypper se -v tuxguitar
Загрузка данных о репозиториях...
Чтение установленных пакетов...

С  | Имя                   | Тип   | Версия  | Архитектура | Репозиторий
---+-----------------------+-------+---------+-------------+-------------------
v  | tuxguitar             | пакет | 1.4-2.1 | i586        | repo-oss
    name: tuxguitar
i+ | tuxguitar             | пакет | 1.4-2.1 | x86_64      | repo-oss
    name: tuxguitar
i+ | tuxguitar             | пакет | 1.4-2.1 | x86_64      | (Системные пакеты)
    name: tuxguitar
   | tuxguitar-debuginfo   | пакет | 1.4-2.1 | i586        | repo-debug
    name: tuxguitar-debuginfo
   | tuxguitar-debuginfo   | пакет | 1.4-2.1 | x86_64      | repo-debug
    name: tuxguitar-debuginfo
   | tuxguitar-debugsource | пакет | 1.4-2.1 | i586        | repo-debug
    name: tuxguitar-debugsource
   | tuxguitar-debugsource | пакет | 1.4-2.1 | x86_64      | repo-debug
    name: tuxguitar-debugsource


--1507726685.0D3AaC80.11874
Date: Wed, 11 Oct 2017 12:58:05 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1062808
           Summary: gkrellm cpufreq plugin, cpufreqplugin does not start
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: x86-64
                OS: openSUSE 42.3
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: epistemepromeneur-at-free.fr
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

cpufreqplugin does not start

log:

/usr/lib64/gkrellm2/plugins/cpufreq.so
    Error: /usr/lib64/gkrellm2/plugins/cpufreq.so: undefined symbol:
cpufreq_cpu_exists


body:
--1507832167.fA6DB6E0.24483
Date: Thu, 12 Oct 2017 18:16:07 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1063066
           Summary: Base:System/systemd: broken manpage
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: systemd-maintainers-at-suse.de
          Reporter: sebix+novell.com-at-sebix.at
        QA Contact: opensuse-communityscreening-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

On TW 20171010 and systemd package version 234-6.1 the beginning of the manpage
looks like this:

JOURNALCTL(1)
journalctl
JOURNALCTL(1)

    .SH "NAME" journalctl - Query the systemd journal

    .SH "SYNOPSIS"

      .HP 264u

        journalctl
         [OPTIONS...]
         [MATCHES...]

    .SH "DESCRIPTION"

      .PP journalctl may be used to query the contents of the systemd(1)
journal as written by systemd-journald.service(8).

      .PP If called without parameters, it will show the full contents of the
journal, starting with the oldest entry collected.

      .PP If one or more match

summary: Base:System/systemd: broken manpage


--1507886507.c1Dab6a0.30583
Date: Fri, 13 Oct 2017 09:21:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1063172
           Summary: brltty hijacks /dev/ttyUSB0 for CP2102 USB to UART Bridge Controllers
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: gorgoglione-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I'm doing embedded software development and my target boards use CP2102 USB to
UART bridge controllers to provide terminal consoles. brltty is installed by
default, is triggered automatically by udev and hijacks /dev/ttyUSB0 when I
plug the cable. Is there any way to prevent this from happening apart
uninstalling brltty?

Best regards,
Giuseppe.


body:
--1507914868.ed1ADC0.10745
Date: Fri, 13 Oct 2017 17:14:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1063306
           Summary: Conflict lua53-luasocket luasocket
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: tchvatal-at-suse.com
          Reporter: sbrabec-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

While upgrading Tumbleweed, I got following error:

File /usr/lib64/lua/5.3/mime/core.so
  from install of
     lua53-luasocket-3.0~rc1+git20170515.5a17f79-1.1.x86_64
(openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     luasocket-3.0~rc1-5.6.x86_64 (@System)

File /usr/lib64/lua/5.3/socket/core.so
  from install of
     lua53-luasocket-3.0~rc1+git20170515.5a17f79-1.1.x86_64
(openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     luasocket-3.0~rc1-5.6.x86_64 (@System)

File /usr/lib64/lua/5.3/socket/serial.so
  from install of
     lua53-luasocket-3.0~rc1+git20170515.5a17f79-1.1.x86_64
(openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     luasocket-3.0~rc1-5.6.x86_64 (@System)

File /usr/lib64/lua/5.3/socket/unix.so
  from install of
     lua53-luasocket-3.0~rc1+git20170515.5a17f79-1.1.x86_64
(openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     luasocket-3.0~rc1-5.6.x86_64 (@System)

File /usr/share/lua/5.3/ltn12.lua
  from install of
     lua53-luasocket-3.0~rc1+git20170515.5a17f79-1.1.x86_64
(openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     luasocket-3.0~rc1-5.6.x86_64 (@System)

File /usr/share/lua/5.3/socket.lua
  from install of
     lua53-luasocket-3.0~rc1+git20170515.5a17f79-1.1.x86_64
(openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     luasocket-3.0~rc1-5.6.x86_64 (@System)

File /usr/share/lua/5.3/socket/ftp.lua
  from install of
     lua53-luasocket-3.0~rc1+git20170515.5a17f79-1.1.x86_64
(openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     luasocket-3.0~rc1-5.6.x86_64 (@System)

File /usr/share/lua/5.3/socket/http.lua
  from install of
     lua53-luasocket-3.0~rc1+git20170515.5a17f79-1.1.x86_64
(openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     luasocket-3.0~rc1-5.6.x86_64 (@System)

File /usr/share/lua/5.3/socket/tp.lua
  from install of
     lua53-luasocket-3.0~rc1+git20170515.5a17f79-1.1.x86_64
(openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     luasocket-3.0~rc1-5.6.x86_64 (@System)

File /usr/share/lua/5.3/socket/url.lua
  from install of
     lua53-luasocket-3.0~rc1+git20170515.5a17f79-1.1.x86_64
(openSUSE-Tumbleweed-Oss)
  conflicts with file from package
     luasocket-3.0~rc1-5.6.x86_64 (@System)

There is no Conflicts/Obsoletes tag in any of these packages.

summary: Conflict lua53-luasocket luasocket


--1508044296.bfC71d7C0.9867
Date: Sun, 15 Oct 2017 05:11:36 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1063371
           Summary: Possible rpmlint false positive wrt invalid-desktopfile
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: aloisio-at-gmx.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 744420
  --> http://bugzilla.opensuse.org/attachment.cgi?id=744420&action=edit
seemingly faulty .desktop file

rpmlint produces this warning:

   gnome-mpv.x86_64: W: invalid-desktopfile
/usr/share/applications/io.github.GnomeMpv.desktop
   .desktop file is not valid, check with desktop-file-validate

without any other detail for the attached file.
desktop-file-validate doesn't report any problem with it.


--1508186193.4CBc24.23093
Date: Mon, 16 Oct 2017 20:36:33 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1063638
           Summary: btrfs balance renders system unresponsive and eventually even kills WiFi when quota is enabled - review I/O scheduling parameters of btrfsmaintenance
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: okurz-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: Antoine.Saroufim-at-gmail.com, aschnell-at-suse.com,
                    auxsvr-at-gmail.com, dmitry-at-roshchin.org,
                    dsterba-at-suse.com, ecsos-at-schirra.net,
                    enadolski-at-suse.com, fcrozat-at-suse.com, fliu-at-suse.com,
                    friedhelm.stappert-at-web.de, guenther-at-mpanrw.de,
                    gweberbh-at-gmail.com, hannsj_uhl-at-de.ibm.com,
                    harald.achitz-at-gmail.com,
                    ingo.goeppert+suse-at-mailbox.org, jeffm-at-suse.com,
                    kdejaeger-at-gmail.com, lnussel-at-suse.com,
                    lpechacek-at-suse.com, ndcunliffe-at-gmail.com,
                    okurz-at-suse.com, ortsacs-at-yahoo.es, rgoldwyn-at-suse.com,
                    richard-at-nod.at, ronisbr-at-gmail.com,
                    slindomansilla-at-suse.com, suse-at-bugs.jan.ritzerfeld.org,
                    sven.heithecker-at-web.de, t.rother-at-netzwissen.de,
                    tneo-at-gmx.com, ulrich.hobelmann+suse-at-gmail.com
        Depends on: 1017461
          Found By: ---
           Blocker: ---

## Observation

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

The first part of fixes have been done in bug 1017461 but it seems the btrfs
maintenance tasks can still have a significant impact on system responsiveness.
Running the btrfs maintenance jobs, e.g.

* /etc/cron.monthly/btrfs-scrub
* /etc/cron.weekly/btrfs-balance
* /etc/cron.weekly/btrfs-trim

can make the clock with seconds displayed stop for some seconds or the mouse
cursor to get stuck for seconds

## Reproducible

* Somehow cause lot of "dirty" data that needs balancing/scrubbing
* Run the cron jobs
* Observe the system responsiveness is hindered

## Expected result

Interactive use of a machine should not be impacted

## Suggestion

It looks like /usr/share/btrfsmaintenance/btrfs-scrub.sh checks for the
variable "$BTRFS_SCRUB_PRIORITY" equalling "normal" from
/etc/sysconfig/btrfsmaintenance but this is set to "idle" for me in the config
file which causes that no I/O scheduling parameters are forwarded to the call
of scrub at all which does not seem to make sense to me. Should it set `-c 3`
for idle or `-c 2 -n 7` for best-effort prio 7 instead?


--1508231269.E40aC55.7194
Date: Tue, 17 Oct 2017 09:07:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1063716
           Summary: cloud-init broken because wrong distro "suse" specified
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: OpenStack
          Assignee: cloud-bugs-at-suse.de
          Reporter: kuko-at-canarytek.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I downloaded the Leap 42.3 OpenStack Cloud image from this URL

http://download.opensuse.org/repositories/Cloud:/Images:/Leap_42.3/images/openSUSE-Leap-42.3-OpenStack.x86_64.qcow2

Created an image in SOC7 and launched an instance. After the instance starts
running, there is no way to connect to the instance because the ssh key was not
installed

Looking at the cloud-init logs I found that cloud-init died with an error
because it didn't find the "suse" distro.

Looking at the /etc/cloud/cloud.cfg, I found the problem here:

system_info:
   # This will affect which distro class gets used
   distro: suse

Because the installed clod-init doesn't know about "suse" distro (it should be
sles or opensuse)

I fixed it changing it to:

system_info:
   # This will affect which distro class gets used
   distro: opensuse

And now it works perfectly.

Without this fix the cloud image is useless...


body:
--1508240097.3cbD3419.15534
Date: Tue, 17 Oct 2017 11:34:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1063771
           Summary: texlive-newtx missing dependency on texlive-boondox
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: ailin.nemui-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Just stumbled upon this issue, after installing newtx:

> mktexnam: Could not map typeface abbreviation xx for zxxrl7z.

I found this bug on redhat:
https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1169148

manually installing boondox fixed it.

pkgs: texlive-specs-a texlive-specs-b texlive-specs-c texlive-specs-d texlive-specs-e texlive-specs-h texlive-specs-i texlive-specs-j texlive-specs-k texlive-specs-m texlive-specs-o texlive-specs-q texlive-specs-r texlive-specs-s texlive-specs-t texlive-specs-u texlive-specs-x texlive-specs-y texlive-specs-z


--1508241784.3B5d5.7690
Date: Tue, 17 Oct 2017 12:03:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1063781
           Summary: FTBFS: python-zope.component-doc unresolvable
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: OpenStack
          Assignee: cloud-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

python-zope.component-doc has been unresolvable for a while now in
openSUSE:Factory

nothing provides python2-zope.security, nothing provides python3-zope.security


body:
--1508260330.FD8a26.8390
Date: Tue, 17 Oct 2017 17:12:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1063871
           Summary: HDMI causes gnome-shell crash
    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: jc-at-phocean.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Crashes are very easy to reproduce since today's snapshot (zypper dup):

Steps:

1. Open a gnome-shell session (wayland)

2. Open a few windows

3. Plug in/out an HDMI secondary display 2 or 3 times

4. gnome-shell crashes severely to log-in screen

Core dumps here:

https://my.pcloud.com/publink/show?code=VZDHjX7ZUlKhUc7xJGYPI9ayLJzHVyroyvty

summary: HDMI causes gnome-shell crash


--1508332339.f3fF1F0.32632
Date: Wed, 18 Oct 2017 13:12:19 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064068
           Summary: Pasting of commands in vim in command mode is no longer possible
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: haenig-at-cosifan.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Maybe it is not the right way to apply a set of commands to an openend file,
but I am used to simply drop (via X11 paste (middle mouse  click)) multiple
lines of the form:
:1,$s/a/b/g
:1,$s/c/d/g
:1,$s/e/f/g

into vim running within an xterm in command mode. For older versions the pasted
lines/commands where properly executed. And this worked if I remember correctly
even via ssh onto Solaris 7/8/9 Boxes ('real' vi there).

Now however the lines itself will be simply inserted at the position where the
cursor resides.

So far I see no possibility to disable mouse 'awareness' of vim itself.

Everything I tried (':set mouse=' ':set mouse-=a' even emptying
/usr/share/vim/vim80 as well as /etc/vimrc) led to nothing.

Even if this "seemless insert" is an wished for (new) behaviour, I still would
very strong "wish" for this to be configurable (switch off). Until then vi(m)
is nearly unusable for me.


--1508393751.d2Abda1D3.17754
Date: Thu, 19 Oct 2017 06:15:51 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064206
           Summary: Server kernel panick after kernel update patch:openSUSE-2017-1159
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.2
          Hardware: x86-64
                OS: openSUSE 42.2
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: pellice-at-yahoo.fr
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

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

After kernel update from 4.4.87-18.29 to 4.4.90-18.32.1
Servers boot correctly but get kernel panic after 30-60 min.

These crash happen only on server having promise EX16650 raid card and it is
not happening anymore after reinstalling the old kernel.

the logs are filled with error relative to scsi/sg (see attachment)


--1508396316.A31DD0.27280
Date: Thu, 19 Oct 2017 06:58:36 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064212
           Summary: No more partitions for dmraid devices in initrd at all
    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: ---

Martin,

It looks like there's a regression due to this change:

 * Fri Aug 11 2017 mwilck-at-suse.com
 - Dropped 67-kpartx-compat.rules (SUSE legacy).
   * symlinks "/dev/mapper/${UUID}_part${X}" are not created any more,
     only     "/dev/mapper/${UUID}-part${X}" (with "minus")
 - Dropped automatic kpartx invocation on dmraid devices (fate#323743)

This has been spotted in bug #1060551, comment #18.

Could you tell us how dmraid devices are supposed to be handled now ?

Also it seems that you dropped the generation of a couple of symlinks. That
will break the setup of all users that has references to those symlinks...


--1508401806.FA406.10637
Date: Thu, 19 Oct 2017 08:30:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064226
           Summary: Get rid of "bin" and "public_html" in the user's home folder
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: jakob.jakobson13-at-posteo.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Dear developers,

could you get rid of the mandatory "bin" and "public_html" folder in the home
folder of the users.
The "bin" folder could be moved to ~/.local/bin (of course you would have to
adapt the bash config for this change). And may I ask for the purpose of the
"public_html" folder?

As a result of the user's home folder would look less messy and I guess
newcomers won't use those folders anyway.

Regards,

Jakob


--1508424504.Ea8705.5348
Date: Thu, 19 Oct 2017 14:48:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064286
           Summary: libxml2-python segfault when building gtk-doc with itstool 2.0.4
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: pmonrealgonzalez-at-suse.com
          Reporter: jmatejek-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: dimstar-at-opensuse.org, zaitor-at-opensuse.org
          Found By: ---
           Blocker: ---

gtk-doc uses itstool to do, uh, something, during its build process

this works fine with itstool 2.0.2 but leads to random errors or segfaults with
itstool 2.0.4
(sometimes it's not a segfault but an error "NoneType is not subscribable"
somewhere in the libxml2 python library. The fact that a segfault *can* happen
is a problem though.)

itstool is a pure Python script and the segfault traces to libxml2-python
module, function libxml_type.

This is happening both in Python 2 and 3 and can be reproduced in Leap 42.3

see my toy project:
https://build.opensuse.org/package/show/home:matejcik:py3port/gtk-doc

the command that segfaults is:
itstool -m fr/fr.mo C/index.docbook C/fdl-appendix.xml

I'm now working on tracking down which exact change in itstool triggers the
segfault. I can confirm that purely by switching the "itstool" script the
segfault either triggers or not.


--1508430609.6A6025A0.31349
Date: Thu, 19 Oct 2017 16:30:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064298
           Summary: Google Chrome V62 black screen at startup.  Chrome apps fail.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: x86-64
                OS: openSUSE 42.3
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Commercial
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: gjjohnson-at-fwsi.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 745215
  --> http://bugzilla.opensuse.org/attachment.cgi?id=745215&action=edit
Chrome startup

On an existing OpenSuSE Leap 42.3 with Google Chrome V62 installed, Chrome has
suddenly begun to start with a black screen and all Chrome apps are failing.  I
have attached a screenshot.

Other than normal OpenSuSE and Chrome updates pushed out from repositories,
there has been no new software installed recently.

After uninstalling Chrome and removing the $HOME/.cache/google-chrome
directory, I re-installed Chrome and still get the black screen at startup.

I may have shutdown OpenSuSE yesterday with Chrome running.

I am attaching a screenshot of the Chrome desktop with pop-ups from failing
Chrome applications.

Is there a known resolution to this problem?


--1508439813.b5FdDEEf1.22799
Date: Thu, 19 Oct 2017 19:03:33 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064318
           Summary: Kubic install fails since switch from ntp to chrony
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

The Kubic pattern had a change, replacing ntp with chrony:

>+Tue Oct 17 17:23:02 CEST 2017 - kukuk-at-suse.de
>+
>+- ntp was replaced by chrony with sle15

With this, I see openQA failures though during installation:

https://openqa.opensuse.org/tests/508145#

No such file or directory: /mnt/etc/ntp.conf


--1508585948.14d86c0.4588
Date: Sat, 21 Oct 2017 11:39:08 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064522
           Summary: golang: missing timezone database in $GOROOT/lib
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Containers
          Assignee: containers-bugowner-at-suse.de
          Reporter: asarai-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

This issue doesn't manifest on most systems (because Go will use the system's
timezone database if it exists), but in OBS builds the required package isn't
installed. As a result, and code that relies on "time" and tries to do
something related to timezones will fail with errors like this:

  open /usr/lib64/go/1.8/lib/time/zoneinfo.zip: no such file or directory

We noticed this while trying to update Docker to 17.10.0_ce.


body:
--1508591481.bC07C3.29645
Date: Sat, 21 Oct 2017 13:11:21 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064524
           Summary: virtualbox build fail on leap 15 kernel
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: Larry.Finger-at-lwfinger.net
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: kernel-maintainers-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.0:Staging:adi:1/virtualbox/standard/x86_64

[ 2395s]
/home/abuild/rpmbuild/BUILD/VirtualBox-5.1.28/modules_build_dir/default/vboxdrv/r0drv/linux/waitqueue-r0drv-linux.h:207:40:
error: passing argument 2 of 'prepare_to_wait' from incompatible pointer type
[-Werror=incompatible-pointer-types]
[ 2395s]      prepare_to_wait(pWait->pWaitQueue, &pWait->WaitQE,
pWait->iWaitState);
[ 2395s]                                         ^
[ 2395s] In file included from
/usr/src/linux-4.12.14-lp150.1/include/linux/mmzone.h:9:0,
[ 2395s]                  from
/usr/src/linux-4.12.14-lp150.1/include/linux/gfp.h:5,
[ 2395s]                  from
/usr/src/linux-4.12.14-lp150.1/include/linux/slab.h:14,
[ 2395s]                  from
/home/abuild/rpmbuild/BUILD/VirtualBox-5.1.28/modules_build_dir/default/vboxdrv/r0drv/linux/the-linux-kernel.h:82,
[ 2395s]                  from
/home/abuild/rpmbuild/BUILD/VirtualBox-5.1.28/modules_build_dir/default/vboxdrv/r0drv/linux/semevent-r0drv-linux.c:32:
[ 2395s] /usr/src/linux-4.12.14-lp150.1/include/linux/wait.h:946:6: note:
expected 'struct wait_queue_entry *' but argument is of type 'int *'

summary: virtualbox build fail on leap 15 kernel


body:
--1508740661.DaEAfC0.25314
Date: Mon, 23 Oct 2017 06:37:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064571
           Summary: timezone: 2017c maintenance update
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: astieger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Update to time zone database, version 2017c:

* Northern Cyprus switches from +03 to +02/+03 on 2017-10-29.
* Fiji ends DST 2018-01-14, not 2018-01-21.
* Namibia switches from +01/+02 to +02 on 2018-04-01.
* Sudan switches from +03 to +02 on 2017-11-01.
* Tonga likely switches from +13/+14 to +13 on 2017-11-05.
* Turks & Caicos switches from -04 to -05/-04 on 2018-11-04.
* corrections to past DST transitions
* Move oversized Canada/East-Saskatchewan to 'backward' file
* zic and the reference runtime now reject multiple leap seconds
  within 28 days of each other, or leap seconds before the Epoch.

summary: timezone: 2017c maintenance update


--1508845546.AaBffFDC5.27809
Date: Tue, 24 Oct 2017 11:45:46 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064854
           Summary: cloud-init ignores network settings from config-drive in external network
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: OpenStack
          Assignee: cloud-bugs-at-suse.de
          Reporter: eblock-at-nde.ag
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Leap 42.3, OpenStack Ocata

Description:
When trying to build a new base image for our private cloud based on 42.3 we
couldn't use cloud-init-0.7.8 (the first version which worked for us in
provider/external networks) from Tumbleweed as the page says "Resource is no
longer available". So we tried to test cloud-init version 17.1, but this only
works for internal/self-service networks where the network data is provided via
metadata service and not via config-drive, which we need in external networks.

Exptected result:
Successfully launch an instance in external network via config-drive (which
worked in 0.7.8)

Actual result:
Instance is launched without network configuration as is not reachable.
After configuring the network manually to have access to the VM I can see the
network data would be available:
---cut here---
test-ebl:~ # cat /mnt/openstack/latest/network_data.json
{"services": [], "networks": [{"network_id":
"be1a07e0-d998-4a74-847a-d44754055229", "type": "ipv4", "netmask":
"255.255.255.0", "link": "tap699730da-62", "routes": [{"netmask": "0.0.0.0",
"network": "0.0.0.0", "gateway": "192.168.168.1"}], "ip_address":
"192.168.168.29", "id": "network0"}], "links": [{"ethernet_mac_address":
"fa:16:3e:04:b6:0c", "mtu": 1500, "type": "bridge", "id": "tap699730da-62",
"vif_id": "699730da-62c6-4233-b1ff-2a76ec44c8cc"}]}
---cut here---

Steps to reproduce:
Launch instance with cloud-init-17.1 in an external (provider) network via
config-drive.

I'll attach cloud-init log files from the to-be-base-image VM and the newly
launched VM.


body:
--1508852752.fE51ABa0.25531
Date: Tue, 24 Oct 2017 13:45:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064872
           Summary: Printer dialog very slow
    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: marius.kittler-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Description:
The printer dialog of KDE Applications like Okular, Kate, KOrganizer, ... is
very slow. Even on a fresh image
(fopensuse-Tumbleweed-x86_64-20171022-kde@64bit.qcow2) without any printers
installed, it takes a few seconds till the dialog is shown. Selecting a printer
is also very slow and sometimes even freezes the application completely. This
makes the printing feature almost unusable.

While waiting for the dialog to show, the application prints "Begin enumerating
printers" and "End enumerating printers" on the console multiple times. In case
printers are available, the printer names are also printed. When selecting a
printer, not further output is printed.

The same happens when opening the print preview.

Steps to reproduce:
1. Open a PDF in Okular
2. Open the printer dialog or the preview, it should take a few seconds
3. Select another printer, it should also take a few seconds

Further information:
Note that Gtk-based applications like Evince and other applications like
Chromium are not affected. The dialog of LibreOffice is also a bit slow, but
acceptable (not sure whether this is related).

summary: Printer dialog very slow


--1508906095.a7F43Cc10.1107
Date: Wed, 25 Oct 2017 04:34:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064958
           Summary: valgrind reports invalid memory access on epoll_pwait call when invoked via epoll_wait
    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: bliu-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

This issue is found on Ubuntu by Fabbione, here is bug description, the bug is
also in Tumbleweed

SRU acceptance criteria: the package builds and the test case succeeds. This is
an obvious typo.

while testing some code for potential memory leaks (using valgrind) I found out
that the test are failing only on Ubuntu 17.10 and the problem appears to be
somewhere in the Ubuntu toolchain. I honestly can�t be 100% sure it�s a gcc /
glibc or valgrind issue.

I reduce the test case to the attached main.c file.

I have tested that same piece code on the following distributions: fedora26,
fedora-rawhide, rhel7.4, rhel7.5-devel, debian9, debian testing, debian
unstable and debian experimental without any error.

On all the above distros:

# gcc -Wall main.c
# valgrind -q --error-exitcode=127 --track-fds=yes --leak-check=full ./a.out
<hit enter to create an epoll_event>
received event: 1
==1807== FILE DESCRIPTORS: 3 open at exit.
==1807== Open file descriptor 2: /dev/pts/0
==1807== <inherited from parent>
==1807==
==1807== Open file descriptor 1: /dev/pts/0
==1807== <inherited from parent>
==1807==
==1807== Open file descriptor 0: /dev/pts/0
==1807== <inherited from parent>
==1807==
==1807==
# echo $?
0

On ubuntu 17.10 freshly installed and fully updated:

# valgrind -q --error-exitcode=127 --track-fds=yes --leak-check=full ./a.out
==8057== Syscall param epoll_pwait(sigmask) points to unaddressable byte(s)
==8057== at 0x4F50C20: epoll_pwait (epoll_pwait.c:42)
==8057== by 0x108A2B: main (in /home/ubuntu/a.out)
==8057== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==8057==

received event: 1
==8057== FILE DESCRIPTORS: 3 open at exit.
==8057== Open file descriptor 2: /dev/pts/4
==8057== <inherited from parent>
==8057==
==8057== Open file descriptor 1: /dev/pts/4
==8057== <inherited from parent>
==8057==
==8057== Open file descriptor 0: /dev/pts/4
==8057== <inherited from parent>
==8057==
==8057==

# echo $?
127

as you can see from the code, we don�t invoke epoll_pwait directly, we invoke
only epoll_wait.

According to the man page for epoll_(p)wait, sigmask can be NULL but somehow
valgrind is catching that as an error or somehow glibc epoll_wait or
epoll_pwait are not treating that properly.
I don�t see any relevant code difference between glibc in debian unstable
(2.24-17) or ubuntu 17.10 (2.26-0ubuntu2) that could warrant this kind of
behavior.

Due to this bug, you could expect some test suite to fail. Not sure if it can
have some runtime side effects tho.


--1508914114.3F46E0.3002
Date: Wed, 25 Oct 2017 06:48:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1064980
           Summary: VUL-0: CVE-2016-10517: redis: POST and Host: strings lack a check that allows "Cross Protocol Scripting"
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2016-10517

networking.c in Redis before 3.2.7 allows "Cross Protocol Scripting" because it
lacks a check for POST and Host: strings, which are not valid in the Redis
protocol (but commonly occur when an attack triggers an HTTP request to the
Redis TCP port).

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-10517
https://www.reddit.com/r/redis/comments/5r8wxn/redis_327_is_out_important_security_fixes_inside/
https://raw.githubusercontent.com/antirez/redis/3.2/00-RELEASENOTES
https://github.com/antirez/redis/commit/874804da0c014a7d704b3d285aa500098a931f50


--1508938814.BF8EaD0.2150
Date: Wed, 25 Oct 2017 13:40:14 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1065058
           Summary: Incorrect console keyboard layout loaded at boot
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Bootloader
          Assignee: daniel.molkentin-at-suse.com
          Reporter: ptesarik-at-suse.com
        QA Contact: jsrain-at-suse.com
          Found By: L3
           Blocker: ---

Dracut does not store the right keymap file in initrd.

My /etc/vconsole.conf contains:

KEYMAP=cz

With this settings, systemd-vconsole-setup calls 'loadkeys cz', which in turn
loads /usr/share/kbd/keymaps/xkb/cz.map.gz.

However, there are multiple cz.map files installed in the system, namely:

# find /usr/share/kbd/keymaps -name cz.map\*
/usr/share/kbd/keymaps/legacy/i386/qwerty/cz.map.gz
/usr/share/kbd/keymaps/legacy/i386/qwertz/cz.map.gz
/usr/share/kbd/keymaps/xkb/cz.map.gz

Only one of them is copied into the resulting initrd:

# lsinitrd /boot/initrd | grep cz\\.map
-rw-r--r


--1509026369.e50D340.17475
Date: Thu, 26 Oct 2017 13:59:29 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1065270
           Summary: python3-libxml2-python: segfault with malformed UTF8 strings in error messages
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: pmonrealgonzalez-at-suse.com
          Reporter: jmatejek-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

libxml2 error reporting seems to return strings of a fixed byte length, leading
up to the detected error.

for instance, if the error comes from the following string:
---

нно удерживая клавишу key
href="help:gnome-help/keyboard-key-super">Super</key>.

---
the error message reads:
---
Opening and ending tag mismatch: p line 2 and key
�вая клавишу key href="help:gnome-help/keyboard-key-super">Super</key>
---

this message has a byte length 81, and the "и" character from "удерживая" is
split in half.

This works fine in Python 2, where strings are sequences of bytes.
But it poses a problem for the Python 3 binding, because it tries to directly
convert the error string to a PyUnicode character string, which fails the
decoding. Libxml doesn't check this error and passes a NULL object to the
calling Python code.
Which causes a crash.


--1509086028.7f6d0.5793
Date: Fri, 27 Oct 2017 06:33:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1065388
           Summary: apparmor is breaking  tool file in lessopen.sh
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: openSUSE Factory
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: werner-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Tracing lessopen.sh with

  export LESS_ADVANCED_PREPROCESSOR=yes

shows

  [...]
  ++ file -L ./less.1
  + type='./less.1: writable, regular file, no read permission'

but it should be

  noether less/less-487> file -L ./less.1
  ./less.1: troff or preprocessor input, ASCII text

in /etc/apparmor.d/usr.bin.lessopen.sh I found

    /usr/bin/file rix,

but no rule for /usr/bin/file its self!

All tools listed in /etc/apparmor.d/usr.bin.lessopen.sh should be able to
read files as otherwise nothings goes.


--1509092688.DfAe1ac4.23678
Date: Fri, 27 Oct 2017 08:24:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1065405
           Summary: VUL-0: CVE-2017-15396: chromium: Stack overflow in V8
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.2
          Hardware: Other
               URL: https://smash.suse.de/issue/194131/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: tchvatal-at-suse.com
          Reporter: astieger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop_26.html

CVE-2017-15396: Stack overflow in V8
Fixed in 62.0.3202.75

References:
https://crbug.com/770452
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-15396
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15396
https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop_26.html


--1509096257.dA4d14.9326
Date: Fri, 27 Oct 2017 09:24:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1065411
           Summary: Package aaa_base in Tumbleweed for aarch64 lacks standard entries in passwd, group and shadow
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: openSUSE Factory
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: freek-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I tried to use postfix in Tumbleweed on a Raspberry Pi 3B system with aarch64.
I got an error message that account nobody is missing. I inspected some files
delivered by aaa_base to set-up /etc/passwd, /etc/group, and /etc/shadow and
found only root mentioned in the template for /etc/passwd. In Leap 42.3 for the
same system these templates contain a lot more entries.


--1509111004.87ea4E41.27415
Date: Fri, 27 Oct 2017 13:30:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1065464
           Summary: Don't allow multiple OpenCL ICD packages to be installed simultaneously
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Installation
          Assignee: yast2-maintainers-at-suse.de
          Reporter: sonichedgehog_hyperblast00-at-yahoo.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

I considered this important enough to warrant a bug report. The forum thread
where I discovered and further explained the issue can be found here:

https://forums.opensuse.org/showthread.php/527821-Blender-crashes-at-startup-with-LLVM-error

When running the command 'zypper dup' without additional parameters, zypper
wants to install the OpenCL ICD named pocl. However Mesa already uses another
ICD which seems to come in the package libOpenCL1. This is a problem because
from the looks of it, you may only have one ICD installed on your system at
once; More than that will cause a conflict, and every OpenCL application will
crash with the following error:

mesa: CommandLine Error: Option 'enable-value-profiling' registered more than
once!
LLVM ERROR: inconsistency in registered CommandLine options

To test and confirm this, you can install both "libOpenCL1" and "pocl"
simultaneously then attempt to run Blender 3D: The application should crash on
startup with the console output quoted above. After removing the pocl package
however, Blender will start and work properly again.

Until this bug is solved by the X11 developers, it might be a good idea for the
openSUSE repositories to be aware of it and mark multiple OpenCL ICD packages
as incompatible, only recommending that you install one at once. Users may find
that OpenCL applications have suddenly stopped working, and not know what to do
in order to fix the problem. A workaround for the time being is to mark pocl as
"taboo / never install".


--1509288458.b7Dfd0.31644
Date: Sun, 29 Oct 2017 14:47:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1065582
           Summary: tor: 0.3.1.8, 0.3.0.12, 0.2.9.13 stable releases
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Maintenance
          Assignee: astieger-at-suse.com
          Reporter: astieger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Community User
           Blocker: ---

https://blog.torproject.org/new-stable-tor-releases-0318-03012-02913-02816-02515
https://lists.torproject.org/pipermail/tor-announce/2017-October/000143.html

Minor version bumps within the same stable series:

openSUSE:Leap:42.2:Update/tor 0.2.9.12 -> 0.2.9.13
openSUSE:Leap:42.3:Update/tor 0.3.0.11 -> 0.3.0.12
openSUSE:Backports:SLE-12/tor 0.3.1.7 -> 0.3.1.8

* Add "Bastet" as a ninth directory authority to the default list
* The directory authority "Longclaw" has changed its IP address
* Fix a timing-based assertion failure that could occur when the
  circuit out-of-memory handler freed a connection's output buffer


--1509355227.083614.17698
Date: Mon, 30 Oct 2017 09:20:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1065619
           Summary: VUL-0: CVE-2017-15924: In manager.c in ss-manager in shadowsocks-libev 3.1.0, improper parsing allowscommand injection via shell metacharacters in a JSON configuration requestreceived via 127.0.0.1 UDP traffic, related to the add_server,
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: hillwoodroc-at-gmail.com
          Reporter: meissner-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2017-15924

In manager.c in ss-manager in shadowsocks-libev 3.1.0, improper parsing allows
command injection via shell metacharacters in a JSON configuration request
received via 127.0.0.1 UDP traffic, related to the add_server, build_config,
and
construct_command_line functions.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-15924
http://seclists.org/oss-sec/2017/q4/137
http://www.debian.org/security/2017/dsa-4009
http://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-15924.html
https://github.com/shadowsocks/shadowsocks-libev/commit/c67d275803dc6ea22c558d06b1f7ba9f94cd8de3
https://github.com/shadowsocks/shadowsocks-libev/issues/1734
https://www.x41-dsec.de/lab/advisories/x41-2017-010-shadowsocks-libev/
http://openwall.com/lists/oss-security/2017/10/13/2


--1509360777.236cBC280.3818
Date: Mon, 30 Oct 2017 10:52:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1065642
           Summary: Batteries of T470s are not shown in UI of KDE Plasma 5
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: markus.zimmermann-at-nethead.at
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I am using the KDE Live version of Tumbleweed Snapshot 20171028 with a Lenovo
Thinkpad T470s. This problem also occurred with an installed version of
Tumbleweed.

No batteries are shown in the UI of KDE Plasma 5 (“Battery and Brightness” in
the Systray). The metrics of both batteries are displayed using tlp-stat.

Also, the batteries are shown using the latest Kubuntu, Ubuntu and Fedora
versions.

Anything I should test?


--1509361652.F6aaD60.6538
Date: Mon, 30 Oct 2017 11:07:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1065650
           Summary: Keyboard backlight of T470s is not available in UI of KDE Plasma 5
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: markus.zimmermann-at-nethead.at
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I am using the KDE Live version of Tumbleweed Snapshot 20171028 with a Lenovo
Thinkpad T470s. This problem also occurred with an installed version of
Tumbleweed.

The keyboard backlight is not available in the UI of KDE Plasma 5 (“Battery and
Brightness” in the Systray). The metrics of the keyboard backlight are
available through
/sys/devices/platform/thinkpad_acpi/leds/tpacpi::kbd_backlight/* and
interacting with
/sys/devices/platform/thinkpad_acpi/leds/tpacpi::kbd_backlight/brightness
works.

Also, the keyboard backlight works with the latest Kubuntu, Ubuntu and Fedora
versions.

Anything I should test?


body:
--1509461049.AEcf6.4365
Date: Tue, 31 Oct 2017 14:44:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1065864
           Summary: Mounting NFS vir gio fails
    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: tbechtold-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Mounting a nfs share via gio (or nautilus) does not work if the server does not
have the "insecure" option set.

$ gio mount nfs://root@192.168.178.31:/nfs-export/
gio: nfs://root@192.168.178.31:0/nfs-export: Permission denied: Perhaps this
host is disallowed or a privileged port is needed

The reason is that a priv. port is needed for libnfs (see
https://github.com/sahlberg/libnfs "root vs. non-root).

To fix this, /usr/lib/gvfs/gvfsd-nfs needs the cap_net_bind_service cap via:

# setcap 'cap_net_bind_service=+ep' /usr/lib/gvfs/gvfsd-nfs

summary: Mounting NFS vir gio fails


--1509704922.F71cB8520.8708
Date: Fri, 3 Nov 2017 10:28:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1066376
           Summary: multipath-tools: shared library packaging
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: martin.wilck-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

We don't package the *.so symlinks for the libraries of multipath tools. This
causes external tools trying to link against e.g. libmpathcmd.so to fail.

Open question 1: should we ship libmultipath.so? If we do, we'd also need to
ship the header files for libmultipath, which we currently don't (we only ship
header files for libmpathcmd, libmpathpersist, and libdmmp).

Open question 2: for strict compliance with
https://en.opensuse.org/User:Mvyskocil/Shared_library_packaging_policy,
we'd have to create subpackages libpathpersist0, libmpathcmd0. Is that required
or even reasonable?


--1509708175.722eBa8d15.23611
Date: Fri, 3 Nov 2017 11:22:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1066392
           Summary: multipath-tools: Factory package fails to build for SLE_12_SP1
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: martin.wilck-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On SLE-12-SP1 and earlier, dracut did not own the directory
/usr/lib/dracut/dracut.conf.d. Fix in spec file.


--1509728401.b138E0.19452
Date: Fri, 3 Nov 2017 17:00:01 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1066461
           Summary: krb5 requires Python 2 to build documentation
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: hguo-at-suse.com
          Reporter: jmatejek-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

in light of fate#323526 (switching to Python 3 by default), i'm identifying
packages that depend on Python 2.

krb5 itself seems to work fine, but its docs are built on obsolete set of
Python2-based tools. It would be nice to either drop the doc building
completely (and rely on online or pre-rendered documentation), or move them
into a separate spec file, so that the main package doesn't need Python 2


--1509741790.e0fbAB4.32335
Date: Fri, 3 Nov 2017 20:43:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1066488
           Summary: VirtualBox guest kernel modules don't match current Leap 42.3 kernel
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: sb56637-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 747077
  --> http://bugzilla.opensuse.org/attachment.cgi?id=747077&action=edit
trying to modprobe vbox* modules

Hello,

I don't fully understand if the problem lies with openSUSE or with VirtualBox,
but I can't load the VirtualBox guest modules in Leap 42.3 because Leap had a
kernel update to 4.4.92-31 and VirtualBox expects kernel 4.4.87-25. The problem
is described here:

-
https://forums.opensuse.org/showthread.php/525768-Cannot-install-oracle-virtualbox-5-1-5-1-22_115216
- https://www.virtualbox.org/ticket/16966

I am attaching screenshots of what happens when I try to load vboxguest,
vboxsf, and xboxvideo.

Thanks!


body:
--1509903250.D028Fc0.15928
Date: Sun, 5 Nov 2017 17:34:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1066528
           Summary: aws-cli nothing provides python-colorama <= 0.3.8
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: rjschwei-at-suse.com
          Reporter: pgeorgiadis-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

drpaneas@localhost:~/Downloads> sudo zypper in aws-cli
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides python-colorama <= 0.3.8 needed by
aws-cli-1.11.104-1.4.noarch
 Solution 1: do not install aws-cli-1.11.104-1.4.noarch
 Solution 2: break aws-cli-1.11.104-1.4.noarch by ignoring some of its
dependencies

I need aws-cli in order to interact with kops (kubernetes operations). The
current version of python2-colorama in TW is: python2-colorama-0.3.9-1.1.noarch

pkgs: aws-cli python-botocore


--1510040992.B86B3.23950
Date: Tue, 7 Nov 2017 07:49:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1066811
           Summary: [Build 20171104] on kdump start: BUG: unable to handle kernel NULL pointer dereference at           (null)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: http://openqa.opensuse.org/tests/524612/modules/kdump_
                    and_crash/steps/37
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

## Observation

openQA test in scenario
opensuse-Tumbleweed-DVD-x86_64-extra_tests_in_textmode@64bit fails in
[kdump_and_crash](http://openqa.opensuse.org/tests/524612/modules/kdump_and_crash/steps/37)

## Reproducible

Fails since (at least) Build
[20170905](http://openqa.opensuse.org/tests/479254)

## Expected result

Last good: [20170904](http://openqa.opensuse.org/tests/478535) (or more recent)

## Further details

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

## More information

The kdump_and_crash test has been failing for a while already - the serial log
contains:

ov 06 12:48:18 susetest systemd[1]: Starting Load kdump kernel and initrd...
Nov 06 12:48:39 susetest kdump[15804]: Loaded kdump kernel: /sbin/kexec -p
/boot/vmlinuz-4.13.10-1-default --append="video=1024x768-16
plymouth.ignore-serial-consoles console=ttyS0 console=tty elevator=deadline
sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory irqpoll
nr_cpus=1 root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0
  panic=1" --initrd=/boot/initrd-4.13.10-1-default-kdump  -s, Result:
Nov 06 12:48:39 susetest systemd[1]: Started Load kdump kernel and initrd.
SCRIPT_FINISHEDF0ZS5-0-
[   55.997783] sysrq: SysRq : Trigger a crash
[   55.998368] BUG: unable to handle kernel NULL pointer dereference at
  (null)
[   55.999390] IP: sysrq_handle_crash+0x17/0x20
[   55.999938] PGD 0
[   55.999939] P4D 0
[   56.000211]
[   56.000683] Oops: 0002 [#1] PREEMPT SMP
[   56.001177] Modules linked in: af_packet iscsi_ibft iscsi_boot_sysfs ppdev
parport_pc parport snd_intel8x0 joydev snd_ac97_codec virtio_net snd_pcm
snd_timer snd soundcore ac97_bus qemu_fw_cfg i2c_piix4 pcspkr hid_generic
usbhid btrfs xor ata_generic raid6_pq sr_mod cdrom ehci_pci ehci_hcd serio_raw
floppy cirrus drm_kms_helper ata_piix virtio_blk virtio_scsi usbcore button
syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm sg
[   56.004609] CPU: 0 PID: 15708 Comm: bash Not tainted 4.13.10-1-default #1
[   56.005155] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org 04/01/2014
[   56.006096] task: ffff987cf66bc280 task.stack: ffffa53481cc4000
[   56.006580] RIP: 0010:sysrq_handle_crash+0x17/0x20
[   56.006984] RSP: 0018:ffffa53481cc7e20 EFLAGS: 00010246
[   56.007409] RAX: 0000000000000000 RBX: 0000000000000063 RCX:
0000000000000000
[   56.008024] RDX: ffff987cffc16400 RSI: ffff987cffc0e298 RDI:
0000000000000063
[   56.008675] RBP: ffffffffa1ce00c0 R08: 0000000000000000 R09:
00000000000001eb
[   56.009330] R10: 0000000000000001 R11: ffffffffa22b322d R12:
0000000000000001
[   56.009905] R13: 0000000000000000 R14: 00005589b691a020 R15:
0000000000000002
[   56.010486] FS:  00007ff2619c6180(0000) GS:ffff987cffc00000(0000)
knlGS:0000000000000000
[   56.011133] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   56.011597] CR2: 0000000000000000 CR3: 000000003ae01000 CR4:
00000000000006f0
[   56.012173] Call Trace:
[   56.012413]  __handle_sysrq+0x83/0x140
[   56.012724]  write_sysrq_trigger+0x2b/0x30
[   56.013061]  proc_reg_write+0x3d/0x60
[   56.013367]  __vfs_write+0x23/0x150
[   56.013657]  ? common_file_perm+0x4d/0x110
[   56.014005]  ? security_file_permission+0x36/0xb0
[   56.014389]  vfs_write+0xad/0x1a0
[   56.014663]  SyS_write+0x42/0x90
[   56.014931]  entry_SYSCALL_64_fastpath+0x1e/0xa9
[   56.015311] RIP: 0033:0x7ff261090854
[   56.015606] RSP: 002b:00007ffedef96ca8 EFLAGS: 00000246 ORIG_RAX:
0000000000000001
[   56.016216] RAX: ffffffffffffffda RBX: 00007ff26135c720 RCX:
00007ff261090854
[   56.016790] RDX: 0000000000000002 RSI: 00005589b691a020 RDI:
0000000000000001
[   56.017368] RBP: 0000000000000001 R08: 000000000000000a R09:
0000000000000000
[   56.020811] R10: 000000000000000a R11: 0000000000000246 R12:
0000000000000001
[   56.021401] R13: 00005589b68437d1 R14: 0000000000000000 R15:
0000000000000000
[   56.021998] Code: 83 c4 38 c3 48 c7 c7 00 5a a9 a1 e8 7f 0c be ff eb e1 66
90 0f 1f 44 00 00 e8 96 b9 be ff c7 05 50 09 db 00 01 00 00 00 0f ae f8 <c6> 04
25 00 00 00 00 01 c3 0f 1f 44 00 00 fb 66 0f 1f 44 00 00
[   56.023560] RIP: sysrq_handle_crash+0x17/0x20 RSP: ffffa53481cc7e20
[   56.024070] CR2: 0000000000000000
[    0.000000] random: get_random_bytes called from start_kernel+0x2a/0x42c
with crng_init=0
[    0.000000] Linux version 4.13.10-1-default (geeko@buildhost) (gcc version
7.2.1 20171020 [gcc-7-branch revision 253932] (SUSE Linux)) #1 SMP PREEMPT Fri
Oct 27 09:03:09 UTC 2017 (db36cf8)
[    0.000000] Command line: elfcorehdr=0x2d09f000 video=1024x768-16
plymouth.ignore-serial-consoles console=ttyS0 console=tty elevator=deadline
sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory irqpoll
nr_cpus=1 root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0
  panic=1


--1510048242.F53b3dA0.31002
Date: Tue, 7 Nov 2017 09:50:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1066851
           Summary: VUL-0: CVE-2017-15398, CVE-2017-15399: chromium: security updates in 62.0.3202.89
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          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/2017/11/stable-channel-update-for-desktop.html

Chromium 62.0.3202.89

CVE-2017-15398: Stack buffer overflow in QUIC
CVE-2017-15399: Use after free in V8


--1510048508.E7B710.31703
Date: Tue, 7 Nov 2017 09:55:08 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1066854
           Summary: spamd wants to start before mail-transfer-agent.target, but that target doesn't exist
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: manfred.h-at-gmx.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The spamd.service file has the following in its [Unit] section:

  Before=mail-transfer-agent.target

It is my understanding that this should ensure that the spamd.service must be
started before the given target is reached. However, such a target doesn't even
exist. Shouldn't there be the following:

  /usr/lib/systemd/system/mail-transfer-agent.target
  /usr/lib/systemd/system/mail-transfer-agent.target.wants/

where the directory stores links for the MTA service for instance?


--1510136224.86cF0f1.4671
Date: Wed, 8 Nov 2017 10:17:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1067133
           Summary: games:tools/steam: Bug cups-lib-* no longer exists - users unable to resolve dep
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: 3rd party software
          Assignee: matthias-at-mailaender.name
          Reporter: jon-at-moozaad.co.uk
        QA Contact: opensuse-communityscreening-at-forge.provo.novell.com
                CC: opensuse-at-dstoecker.de
          Found By: ---
           Blocker: ---

Spec file needs an update to change "Requires: cups-lib-*" to cupslib2-*. eg.
https://build.opensuse.org/package/rdiff/home:moozaad:branches:games:tools/steam?opackage=steam&oproject=games%3Atools&rev=3
(not tested as I don't have access to a VM at the moment for a clean install so
I didn't want to submit it).

New users are currently up able to install due to the library package name
change.

libcef 64bit seems to be the only lib that requires cups in the either the 32b
or 64b ubuntu runtimes.

```
/home/moozaad/.local/share/Steam/ubuntu12_64/libcef.so:
        libcups.so.2 => /usr/lib64/libcups.so.2 (0x00007fea6e025000).
```

For reference, cups req: https://build.opensuse.org/request/show/537070


--1510142862.D37B01.1132
Date: Wed, 8 Nov 2017 12:07:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1067163
           Summary: VUL-0: CVE-2017-16661: cacti: Cacti 1.1.27 allows remote authenticated administrators to read arbitrary files
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
               URL: https://smash.suse.de/issue/194654/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: aj-at-ajaissle.de
          Reporter: vpereira-at-microfocus.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2017-16661

Cacti 1.1.27 allows remote authenticated administrators to read arbitrary files
by placing the Log Path into a private directory, and then making a
clog.php?filename= request, as demonstrated by filename=passwd (with a Log Path
under /etc) to read /etc/passwd.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-16661


--1510142909.bDbDA1.32396
Date: Wed, 8 Nov 2017 12:08:29 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1067164
           Summary: VUL-0: CVE-2017-16660: cacti: Cacti 1.1.27 allows remote authenticated administrators to conduct Remote CodeExecution attacks by placing the Log Path under the web root, and then making aremote_agent.php request containing PHP code in a Client-i
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
               URL: https://smash.suse.de/issue/194653/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: aj-at-ajaissle.de
          Reporter: vpereira-at-microfocus.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2017-16660

Cacti 1.1.27 allows remote authenticated administrators to conduct Remote Code
Execution attacks by placing the Log Path under the web root, and then making a
remote_agent.php request containing PHP code in a Client-ip header.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-16660
https://github.com/Cacti/cacti/issues/1066


--1510142998.e0cDc1.1326
Date: Wed, 8 Nov 2017 12:09:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1067166
           Summary: VUL-0: CVE-2017-16641: cacti: lib/rrd.php in Cacti 1.1.27 allows remote authenticated administrators to execute arbitrary OS commands
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/194635/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: aj-at-ajaissle.de
          Reporter: vpereira-at-microfocus.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2017-16641

lib/rrd.php in Cacti 1.1.27 allows remote authenticated administrators to
execute arbitrary OS commands via the path_rrdtool parameter in an action=save
request to settings.php.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-16641
https://github.com/Cacti/cacti/issues/1057


--1510155600.fAcE34.26561
Date: Wed, 8 Nov 2017 15:40:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1067213
           Summary: /var/adm/update-scripts scriplets not executed?
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: rbrown-at-suse.com
          Reporter: rbrown-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: kukuk-at-suse.com
        Depends on: 1066187
          Found By: ---
           Blocker: ---

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

On Tumbleweed & SLES15 Beta1 default installations, the following scriplets in
/var/adm/update-scripts are not run

ghostscript-fonts-9.06-1.5-reconfigure-fonts
google-noto-fonts-20161025-1.5-reconfigure-fonts

According to the scripts they should delete themself if they did run, but since
they do still exist, it looks like they were never executed.


--1510195708.e1E55.2275
Date: Thu, 9 Nov 2017 02:48:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1067288
           Summary: gnome-initial-setup should set the Mozc engine as the first position and default selection of input selection page
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: qzhao-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Description of problem:
gnome-initial-setup should set the Mozc engine as the first position and
default selection of input selection page.

Version-Release number of selected component (if applicable):
openSUSE Tumbleweed all release
Gnome 3 all release

How reproducible:
always

Steps to Reproduce:(See attachment)
1, Fresh install openSUSE Tumbleweed;
2, During the installation, set default language as Japanese.
3, After login to desktop, launch gnome-initial-setup.
4, Check the input selection page.

Actual results:
input selection "Japanese" has been selected.

Expected results:
input engine "Mozc" is in the 1st position, and be the default selection.

Additional info:
As the openSUSE community requires, we switch Mozc as default selection for
Japanese, but gnome-initial-setup has not changed.
Bug 1056289 - User's default IBUS input engine should only be "Mozc" under
Japanese language with GNOME desktop


--1510214824.8eCC40.7306
Date: Thu, 9 Nov 2017 08:07:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1067342
           Summary: VUL-0: CVE-2017-16667: backintime (aka Back in Time) before 1.1.24 did improper escaping/quoting offile paths used as arguments to the 'notify-send' command, leading to some partsof file paths being executed as shell commands within an os
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.3
          Hardware: Other
               URL: https://smash.suse.de/issue/194694/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: masterpatricko-at-gmail.com
          Reporter: meissner-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2017-16667

backintime (aka Back in Time) before 1.1.24 did improper escaping/quoting of
file paths used as arguments to the 'notify-send' command, leading to some
parts
of file paths being executed as shell commands within an os.system call in
qt4/plugins/notifyplugin.py. This could allow an attacker to craft an
unreadable
file with a specific name to run arbitrary shell commands.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-16667
http://seclists.org/oss-sec/2017/q4/251
http://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-16667.html
http://www.cvedetails.com/cve/CVE-2017-16667/
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16667
https://github.com/bit-team/backintime/issues/834
https://github.com/bit-team/backintime/releases/tag/v1.1.24
https://github.com/bit-team/backintime/commit/cef81d0da93ff601252607df3db1a48f7f6f01b3


--1510242719.A7125.10506
Date: Thu, 9 Nov 2017 15:51:59 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1067477
           Summary: apparmor-utils recommends libnotify-tools which brings in Gnome & X
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.0
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: idonmez-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Leap 15 base pattern includes apparmor & apparmor-utils. apparmor-utils package
has a Recommends on libnotify-tools package which ends up bringing many gnome
packages and of course X server.

This is very bad because we end up with ~1.2k packages on a text installation
instead of 300 packages.


body:
--1510249699.1b58760.10303
Date: Thu, 9 Nov 2017 17:48:19 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 1067502
           Summary: git-p4 requires Python 2
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: tiwai-at-suse.com
          Reporter: jmatejek-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

git-p4, the tool to interact with Perforce, is written in Python 2. According
to upstream, it's not easy to convert to Python 3.

ISTM this feature is not really essential, but git-p4 is packaged in git-core
and thus pulls in python2 as its dependency.

It would be nice if we could either drop this, or move it to a separate
subpackage, so that standard installation of "git" doesn't pull in python2.
(i can send a SR for either option)

summary: git-p4 requires Python 2