--1466561079.7CBdfE0.11175
Date: Wed, 22 Jun 2016 02:04:39 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 985971
           Summary: TeXLive: Syntax error in "update" script from texlive-filesystem
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: x86-64
                OS: openSUSE 42.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: werner-at-suse.com
          Reporter: andrea.turrini-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I have just updated my TeXLive installation via zypper by using the repository
http://download.opensuse.org/repositories/Publishing:/TeXLive/openSUSE_Leap_42.1/

Everything works as expected but on running the update-scripts at the end of
the installation, I see the following messages:

Running: texlive-kpathsea-2016.109.svn41139-104.1-zypper  (texlive-kpathsea,
/var/adm/update-scripts)
/usr/share/texmf/texconfig/update: line 238: test: `)' expected, found
/usr/share/texmf/texconfig/update: line 536: syntax error near unexpected token
`('
/usr/share/texmf/texconfig/update: line 536: `
?(\*)@(+([0-9])|+([0-9])x+([0-9]))dpi)'
Running: texlive-kpathsea-2016.109.svn41139-104.1-zypper  (texlive-kpathsea,
/var/adm/update-scripts) ..................................[done]

I have also updated TeXLive on my other openSUSE 13.2 installation from the
corresponding repository and also there the errors occur.

It seems that in my system these errors don't affect the functionality of
TeXLive, at least from the files I tested.


--1466592992.3A8d6f7.17468
Date: Wed, 22 Jun 2016 10:56:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 986036
           Summary: crit: ImportError: No module named google.protobuf.internal
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: michal.vyskocil-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After installation of criu package on Leap 42.1 system I got the following
error

crit
Traceback (most recent call last):
  File "/usr/bin/crit", line 6, in <module>
    import pycriu
  File "/usr/lib/python2.7/site-packages/pycriu/__init__.py", line 1, in
<module>
    import rpc
  File "/usr/lib/python2.7/site-packages/pycriu/rpc.py", line 6, in <module>
    from google.protobuf.internal import enum_type_wrapper
ImportError: No module named google.protobuf.internal

python-protobuf package is not listed as a dependency, after zypper in
python-protobuf, crit reports usage line.

BTW: openSUSE:Factory have it fixed, so this is just about Leap.


--1466668314.dd3a71F4.29274
Date: Thu, 23 Jun 2016 07:51:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 986162
           Summary: thunderbird crashes on startup after 20160621 snapshot due to gcc6
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://bugzilla.redhat.com/show_bug.cgi?id=1312635
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Firefox
          Assignee: wolfgang-at-rosenauer.org
          Reporter: vbabka-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: pcerny-at-suse.com
          Found By: ---
           Blocker: ---

After the latest TW snapshot that introduces gcc6, thunderbird crashes on
startup. Safe mode doesn't help, new profile does, but it doesn't look like my
profile is corrupted (see below).

Here's backtrace captured by gdb:

#0  0x00007ffff100fe50 in morkAtom::AliasYarn (this=0x0,
outYarn=outYarn@entry=0x7fffffff9b98) at
/usr/src/debug/thunderbird/db/mork/src/morkAtom.cpp:145
#1  0x00007ffff101bb2b in morkRowObject::AliasCellYarn (this=0x7fffc7e1dca0,
mev=<optimized out>, inColumn=161, outYarn=0x7fffffff9b98)
    at /usr/src/debug/thunderbird/db/mork/src/morkRowObject.cpp:492
#2  0x00007ffff113462b in nsMsgDatabase::RowCellColumnToUInt32 (this=<optimized
out>, hdrRow=<optimized out>, columnToken=<optimized out>,
uint32Result=uint32Result@entry=0x7fffc6b7ad74,
    defaultValue=defaultValue@entry=0) at
/usr/src/debug/thunderbird/mailnews/db/msgdb/src/nsMsgDatabase.cpp:3768
#3  0x00007ffff1134663 in nsMsgDatabase::RowCellColumnToUInt32 (this=<optimized
out>, hdrRow=<optimized out>, columnToken=<optimized out>,
uint32Result=@0x7fffc6b7ad74: 0,
    uint32Result@entry=@0x7fffc6b7ad74: <optimized out>,
defaultValue=defaultValue@entry=0) at
/usr/src/debug/thunderbird/mailnews/db/msgdb/src/nsMsgDatabase.cpp:3756
#4  0x00007ffff112e531 in nsDBFolderInfo::GetInt32PropertyWithToken
(this=this@entry=0x7fffc6b7ad40, aProperty=<optimized out>,
propertyValue=@0x7fffc6b7ad74: 0,
    defaultValue=defaultValue@entry=0) at
/usr/src/debug/thunderbird/mailnews/db/msgdb/src/nsDBFolderInfo.cpp:865
#5  0x00007ffff112e573 in nsDBFolderInfo::LoadMemberVariables
(this=this@entry=0x7fffc6b7ad40) at
/usr/src/debug/thunderbird/mailnews/db/msgdb/src/nsDBFolderInfo.cpp:355
#6  0x00007ffff112e7b5 in nsDBFolderInfo::InitFromExistingDB
(this=0x7fffc6b7ad40) at
/usr/src/debug/thunderbird/mailnews/db/msgdb/src/nsDBFolderInfo.cpp:312
#7  0x00007ffff1136b25 in nsMsgDatabase::InitExistingDB (this=0x7fffc7d51e30)
at /usr/src/debug/thunderbird/mailnews/db/msgdb/src/nsMsgDatabase.cpp:1716
#8  0x00007ffff113357c in nsMsgDatabase::OpenMDB (this=0x7fffc7d51e30,
dbName=<optimized out>, create=<optimized out>, sync=<optimized out>)
    at /usr/src/debug/thunderbird/mailnews/db/msgdb/src/nsMsgDatabase.cpp:1403
#9  0x00007ffff1138f0c in nsMsgDatabase::OpenInternal (this=0x7fffc7d51e30,
aDBService=0x7fffcb5e48b0, summaryFile=0x7fffc6b7a740, aCreate=<optimized out>,
aLeaveInvalidDB=<optimized out>,
    sync=<optimized out>) at
/usr/src/debug/thunderbird/mailnews/db/msgdb/src/nsMsgDatabase.cpp:1210
#10 0x00007ffff1135c81 in nsMsgDBService::OpenFolderDB
(this=this@entry=0x7fffcb5e48b0, aFolder=aFolder@entry=0x7fffc6cb4038,
aLeaveInvalidDB=aLeaveInvalidDB@entry=false,
    _retval=0x7fffc6cb4060) at
/usr/src/debug/thunderbird/mailnews/db/msgdb/src/nsMsgDatabase.cpp:134
#11 0x00007ffff116a26d in nsImapMailFolder::GetDatabase (this=0x7fffc6cb4000)
at /usr/src/debug/thunderbird/mailnews/imap/src/nsImapMailFolder.cpp:606
#12 0x00007ffff1164a54 in nsImapMailFolder::GetDBFolderInfoAndDB
(this=this@entry=0x7fffc6cb4000, folderInfo=0x7fffffffa200,
db=db@entry=0x7fffffffa1f8)
    at /usr/src/debug/thunderbird/mailnews/imap/src/nsImapMailFolder.cpp:2060
#13 0x00007ffff10baf52 in nsMsgDBFolder::OnFlagChange (this=0x7fffc6cb4000,
flag=16384) at
/usr/src/debug/thunderbird/mailnews/base/util/nsMsgDBFolder.cpp:4367
#14 0x00007ffff10b6a4d in nsMsgDBFolder::ClearFlag (this=0x7fffc6cb4000,
flag=16384) at
/usr/src/debug/thunderbird/mailnews/base/util/nsMsgDBFolder.cpp:4342
#15 0x00007ffff106b257 in nsMsgAccountManager::SetSpecialFolders
(this=<optimized out>) at
/usr/src/debug/thunderbird/mailnews/base/src/nsMsgAccountManager.cpp:1444
#16 0x00007ffff12a7bef in NS_InvokeByIndex (that=<optimized out>,
methodIndex=<optimized out>, paramCount=<optimized out>, params=<optimized
out>)
    at
/usr/src/debug/thunderbird/mozilla/xpcom/reflect/xptcall/md/unix/xptcinvoke_x86_64_unix.cpp:176
#17 0x00007ffff16c5329 in CallMethodHelper::Invoke (this=0x7fffffffa578) at
/usr/src/debug/thunderbird/mozilla/js/xpconnect/src/XPCWrappedNative.cpp:2097
#18 CallMethodHelper::Call (this=0x7fffffffa578) at
/usr/src/debug/thunderbird/mozilla/js/xpconnect/src/XPCWrappedNative.cpp:1414
#19 XPCWrappedNative::CallMethod (ccx=...,
mode=mode@entry=XPCWrappedNative::CALL_METHOD) at
/usr/src/debug/thunderbird/mozilla/js/xpconnect/src/XPCWrappedNative.cpp:1381
#20 0x00007ffff16ca603 in XPC_WN_CallMethod (cx=<optimized out>,
cx@entry=0x7fffd0c61c00, argc=0, vp=0x7fffdce57208)
    at
/usr/src/debug/thunderbird/mozilla/js/xpconnect/src/XPCWrappedNativeJSOps.cpp:1115
#21 0x00007ffff3275d58 in js::CallJSNative (args=..., native=<optimized out>,
cx=0x7fffd0c61c00) at
/usr/src/debug/thunderbird/mozilla/js/src/jscntxtinlines.h:235
#22 js::Invoke (cx=0x7fffd0c61c00, args=..., construct=<optimized out>) at
/usr/src/debug/thunderbird/mozilla/js/src/vm/Interpreter.cpp:444
#23 0x00007ffff32715d1 in Interpret (cx=0x7fffd0c61c00, state=...) at
/usr/src/debug/thunderbird/mozilla/js/src/vm/Interpreter.cpp:2766
#24 0x00007ffff3275a11 in js::RunScript (cx=cx@entry=0x7fffd0c61c00, state=...)
at /usr/src/debug/thunderbird/mozilla/js/src/vm/Interpreter.cpp:391
#25 0x00007ffff3275cb7 in js::Invoke (cx=cx@entry=0x7fffd0c61c00, args=...,
construct=construct@entry=js::NO_CONSTRUCT) at
/usr/src/debug/thunderbird/mozilla/js/src/vm/Interpreter.cpp:462
#26 0x00007ffff32764ed in js::Invoke (cx=0x7fffd0c61c00, thisv=..., fval=...,
argc=1, argv=<optimized out>, rval=...) at
/usr/src/debug/thunderbird/mozilla/js/src/vm/Interpreter.cpp:496
#27 0x00007ffff312637a in JS::Call (cx=<optimized out>, thisv=...,
thisv@entry=..., fval=..., fval@entry=..., args=..., rval=..., rval@entry=...)
    at /usr/src/debug/thunderbird/mozilla/js/src/jsapi.cpp:2837
#28 0x00007ffff1ec9779 in mozilla::dom::EventHandlerNonNull::Call
(this=this@entry=0x7fffd0bac6a0, cx=<optimized out>, aThisVal=...,
aThisVal@entry=..., event=..., aRetVal=...,
    aRetVal@entry=..., aRv=...) at
/usr/src/debug/obj/dom/bindings/EventHandlerBinding.cpp:259
#29 0x00007ffff2065ba2 in mozilla::dom::EventHandlerNonNull::Call<nsISupports*>
(aCompartment=0x0,
aExceptionHandling=mozilla::dom::CallbackObject::eReportExceptions,
    aExecutionReason=0x7ffff375fe4a "EventHandlerNonNull", aRv=...,
aRetVal=..., event=..., thisVal=@0x7fffd0bac5f0: 0x7fffd0c62400,
this=0x7fffd0bac6a0)
    at ../../dist/include/mozilla/dom/EventHandlerBinding.h:351
#30 mozilla::JSEventHandler::HandleEvent (this=0x7fffd0bac5e0,
aEvent=<optimized out>) at
/usr/src/debug/thunderbird/mozilla/dom/events/JSEventHandler.cpp:215
#31 0x00007ffff2066f0c in mozilla::EventListenerManager::HandleEventSubType
(this=this@entry=0x7fffd0b5ec50, aListener=<optimized out>,
aListener@entry=0x7fffca584808,
    aDOMEvent=0x7fffc7018740, aCurrentTarget=<optimized out>,
aCurrentTarget@entry=0x7fffd0c62400) at
/usr/src/debug/thunderbird/mozilla/dom/events/EventListenerManager.cpp:1027
#32 0x00007ffff20672ae in mozilla::EventListenerManager::HandleEventInternal
(this=0x7fffd0b5ec50, aPresContext=<optimized out>, aEvent=0x7fffffffb8a0,
aDOMEvent=0x7fffffffb798,
    aCurrentTarget=0x7fffd0c62400, aEventStatus=<optimized out>) at
/usr/src/debug/thunderbird/mozilla/dom/events/EventListenerManager.cpp:1154
#33 0x00007ffff2051f06 in mozilla::EventTargetChainItem::HandleEventTargetChain
(aChain=..., aVisitor=..., aCallback=aCallback@entry=0x0, aCd=...)
    at /usr/src/debug/thunderbird/mozilla/dom/events/EventDispatcher.cpp:315

Googling the first line brought me to the Fedora bug
https://bugzilla.redhat.com/show_bug.cgi?id=1312635 where the workaround is
apparently adding -fno-delete-null-pointer-checks to gcc flags

There's also an upstream bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1251576


--1466678170.E7a00.16291
Date: Thu, 23 Jun 2016 10:36:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 986211
           Summary: man does not work as expected as user root
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: sweet_f_a-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When watching man pages as user root there is no search history in the pager
(less).

The problem is that suse is using a wrapper which changes the uid of the
process, running as user "man". User man has no permissions to access
/root/.lesshst

So man is broken for user root. It couldn't even read it's own config files
/root/.manpath nor potentially any other path specified by all these $LESS* or
$MAN* variables.

BTW what is that wrapper good for? Is man a dangerous command? I guess there
are more dangerous commands like rm or dd. Why these ones doesn't have a
wrapper to make them useless?


body:
--1466690015.40b2cd1.29982
Date: Thu, 23 Jun 2016 13:53:35 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 986251
           Summary: lost+found directory causes mysql_upgrade to fail
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: bjoernv-at-arcor.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

If /var/lib/mysql or a custom datadir is mounted on an EXT2/3/4 filesystem, the
directory lost+found with one or more files inside causes upgrades to fail.

Each MySQL package upgrade causes mysql_upgrade calls.

The full description of this bug can be found upstream:
http://bugs.mysql.com/bug.php?id=81974

The older bug report for the same subject can be found here:
https://bugs.mysql.com/bug.php?id=22615

The solution is to append --ignore-db-dir=lost+found to the mysqld options.

I found this bug on the following distributions:
- SLES 12
- Leap 42.1
- Tumbleweed

pkgs: mariadb mysql-community-server


--1466867749.15DBd0d50.5050
Date: Sat, 25 Jun 2016 15:15:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 986527
           Summary: Connection tracker helper must be setup in SuSEfirewall2 for configuration samba-client
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: suse+build@de-korte.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Now that automatic loading of connection tracker helpers is disabled by default
in /etc/sysctl.conf

    net.netfilter.nf_conntrack_helper = 0

when the following are set in /etc/sysconfig/SuSEfirewall2

    FW_CONFIGURATIONS_EXT/DMZ/INT="samba-client"
    FW_LOAD_MODULES="nf_conntrack_netbios_ns"

NetBIOS browsing no longer works, since replies to the NetBIOS broadcasts are
filtered by the firewall.

The netbios-ns helper should be enabled if 'samba-client' is added to one of
the interfaces for FW_CONFIGRATIONS_EXT/DMZ/INT. Something along the lines of

    iptables -A OUTPUT -p udp -m udp --dport 137 -j CT --helper netbios-ns

should do the trick (possibly with physical interfaces added).


--1466942206.5CEf31.27372
Date: Sun, 26 Jun 2016 11:56:46 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 986541
           Summary: Firefox doesn't start after today's update
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: i686
                OS: SUSE Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Firefox
          Assignee: bnc-team-mozilla-at-forge.provo.novell.com
          Reporter: lpechacek-at-suse.com
        QA Contact: qa-bugs-at-suse.de
        Depends on: 986540
          Found By: ---
           Blocker: ---

lpechacek@fmn:~> firefox
ExceptionHandler::GenerateDump cloned child 4196
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
<and a crash report dialog>
lpechacek@fmn:~> firefox -d gdb
gdb /usr/lib/firefox/firefox -x /tmp/mozargs.pFSenL
GNU gdb (GDB; openSUSE Tumbleweed) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i586-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/firefox/firefox...Reading symbols from
/usr/lib/debug/usr/lib/firefox/firefox.debug...done.
done.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
runDetaching after fork from child process 4228.
[New Thread 0xb0b84b40 (LWP 4229)]
[Thread 0xb0b84b40 (LWP 4229) exited]
Detaching after fork from child process 4230.
[New Thread 0xb0b84b40 (LWP 4231)]
[New Thread 0xaeb65b40 (LWP 4232)]
[New Thread 0xae364b40 (LWP 4233)]
[New Thread 0xad9ffb40 (LWP 4234)]
[New Thread 0xad1feb40 (LWP 4235)]
[New Thread 0xacffdb40 (LWP 4236)]
[New Thread 0xacdfcb40 (LWP 4237)]
[New Thread 0xacbfbb40 (LWP 4238)]
[New Thread 0xac9fab40 (LWP 4239)]
[New Thread 0xac7f9b40 (LWP 4240)]
[New Thread 0xab1ffb40 (LWP 4241)]
[New Thread 0xaa49eb40 (LWP 4242)]
[New Thread 0xaa2ffb40 (LWP 4243)]
[New Thread 0xa9472b40 (LWP 4244)]
[New Thread 0xa8c71b40 (LWP 4245)]
[New Thread 0xa78ffb40 (LWP 4246)]
[New Thread 0xa70feb40 (LWP 4247)]
[New Thread 0xa66ffb40 (LWP 4248)]
[New Thread 0xa5cffb40 (LWP 4249)]
[New Thread 0xa4bffb40 (LWP 4250)]
[New Thread 0xa43feb40 (LWP 4251)]
[New Thread 0xa42fdb40 (LWP 4252)]
[New Thread 0xa38ffb40 (LWP 4253)]
[New Thread 0xa30feb40 (LWP 4254)]
[New Thread 0xa26ffb40 (LWP 4255)]
[Thread 0xa70feb40 (LWP 4247) exited]
[New Thread 0xa1bffb40 (LWP 4256)]
[New Thread 0xa13feb40 (LWP 4257)]
[New Thread 0xa0bfdb40 (LWP 4258)]

Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
0xb4801692 in nsLayoutUtils::GetLastSibling (aFrame=0xe5e5e5e5) at
/usr/src/debug/mozilla/layout/base/nsLayoutUtils.cpp:1797
1797    /usr/src/debug/mozilla/layout/base/nsLayoutUtils.cpp: No such file or
directory.
Missing separate debuginfos, use: zypper install
Mesa-libEGL1-debuginfo-11.2.2-139.2.i586
Mesa-libGL1-debuginfo-11.2.2-139.2.i586
Mesa-libglapi0-debuginfo-11.2.2-139.2.i586 dbus-1-glib-debuginfo-0.104-1.5.i586
fontconfig-debuginfo-2.11.1-6.3.i586 gconf2-debuginfo-3.2.6-10.2.i586
glibc-locale-debuginfo-2.23-4.12.i586
gtk2-theming-engine-adwaita-debuginfo-3.20.2-2.2.i586
gvfs-debuginfo-1.28.2-1.2.i586 libFLAC8-debuginfo-1.3.1-2.5.i586
libICE6-debuginfo-1.0.9-3.6.i586 libSM6-debuginfo-1.2.2-5.6.i586
libX11-6-debuginfo-1.6.3-2.15.i586 libX11-xcb1-debuginfo-1.6.3-2.15.i586
libXau6-debuginfo-1.0.8-6.5.i586 libXcomposite1-debuginfo-0.4.4-10.5.i586
libXcursor1-debuginfo-1.1.14-6.6.i586 libXdamage1-debuginfo-1.1.4-9.5.i586
libXext6-debuginfo-1.3.3-3.17.i586 libXfixes3-debuginfo-5.0.2-1.2.i586
libXi6-debuginfo-1.7.6-1.3.i586 libXinerama1-debuginfo-1.1.3-5.5.i586
libXrandr2-debuginfo-1.5.0-2.3.i586 libXrender1-debuginfo-0.9.9-1.17.i586
libXt6-debuginfo-1.1.5-1.17.i586 libXxf86vm1-debuginfo-1.1.4-1.5.i586
libasound2-debuginfo-1.1.1-3.2.i586 libatk-1_0-0-debuginfo-2.20.0-2.2.i586
libbz2-1-debuginfo-1.0.6-37.77.i586 libcairo2-debuginfo-1.15.2-1.3.i586
libcanberra-gtk0-debuginfo-0.30-12.3.i586
libcanberra-gtk2-module-debuginfo-0.30-12.3.i586
libcanberra0-debuginfo-0.30-12.3.i586 libcap2-debuginfo-2.22-14.99.i586
libdatrie1-debuginfo-0.2.9-1.4.i586 libdbus-1-3-debuginfo-1.10.8-1.3.i586
libdrm2-debuginfo-2.4.68-1.2.i586 libexpat1-debuginfo-2.1.1-3.17.i586
libffi4-debuginfo-5.3.1+r234891-1.22.i586 libfreebl3-debuginfo-3.23-1.2.i586
libfreetype6-debuginfo-2.6.3-1.3.i586 libgbm1-debuginfo-11.2.2-139.2.i586
libgcc_s1-gcc6-debuginfo-6.1.1+r236988-1.1.i586
libgcrypt20-debuginfo-1.6.5-2.2.i586
libgdk_pixbuf-2_0-0-debuginfo-2.34.0-1.3.i586
libgio-2_0-0-debuginfo-2.48.1-1.2.i586 libglib-2_0-0-debuginfo-2.48.1-1.2.i586
libgmodule-2_0-0-debuginfo-2.48.1-1.2.i586
libgobject-2_0-0-debuginfo-2.48.1-1.2.i586
libgpg-error0-debuginfo-1.22-1.2.i586 libgraphite2-3-debuginfo-1.3.8-1.2.i586
libgthread-2_0-0-debuginfo-2.48.1-1.2.i586
libgtk-2_0-0-debuginfo-2.24.30-1.3.i586 libharfbuzz0-debuginfo-1.2.7-2.2.i586
libjson-c2-debuginfo-0.12-1.8.i586 libltdl7-debuginfo-2.4.6-4.66.i586
liblzma5-debuginfo-5.2.2-4.87.i586 libmodman1-debuginfo-2.0.1-17.5.i586
libnsssharedhelper0-debuginfo-1.0.10-9.5.i586 libogg0-debuginfo-1.3.2-1.5.i586
libpango-1_0-0-debuginfo-1.40.1-1.3.i586 libpcre1-debuginfo-8.38-1.71.i586
libpixman-1-0-debuginfo-0.34.0-2.2.i586 libpng16-16-debuginfo-1.6.22-1.2.i586
libproxy1-debuginfo-0.4.13-2.2.i586 libpulse0-debuginfo-8.0-4.2.i586
libselinux1-debuginfo-2.3-5.95.i586 libsndfile1-debuginfo-1.0.26-2.2.i586
libsoftokn3-debuginfo-3.23-1.2.i586 libspeex1-debuginfo-1.2~rc2-2.4.i586
libsqlite3-0-debuginfo-3.13.0-1.2.i586
libstartup-notification-1-0-debuginfo-0.12-14.5.i586
libstdc++6-gcc6-debuginfo-6.1.1+r236988-1.1.i586
libsystemd0-debuginfo-228-8.2.i586 libthai0-debuginfo-0.1.24-1.3.i586
libuuid1-debuginfo-2.28-2.13.i586 libvorbis0-debuginfo-1.3.5-1.7.i586
libvorbisenc2-debuginfo-1.3.5-1.7.i586 libvorbisfile3-debuginfo-1.3.5-1.7.i586
libwayland-client0-debuginfo-1.11.0-1.2.i586
libwayland-server0-debuginfo-1.11.0-1.2.i586
libxcb-dri2-0-debuginfo-1.12-1.2.i586 libxcb-dri3-0-debuginfo-1.12-1.2.i586
libxcb-glx0-debuginfo-1.12-1.2.i586 libxcb-present0-debuginfo-1.12-1.2.i586
libxcb-render0-debuginfo-1.12-1.2.i586 libxcb-shm0-debuginfo-1.12-1.2.i586
libxcb-sync1-debuginfo-1.12-1.2.i586 libxcb-util1-debuginfo-0.4.0-1.6.i586
libxcb-xfixes0-debuginfo-1.12-1.2.i586 libxcb1-debuginfo-1.12-1.2.i586
libxshmfence1-debuginfo-1.2-1.5.i586 libz1-debuginfo-1.2.8-11.74.i586
mozilla-nspr-debuginfo-4.12-1.3.i586 mozilla-nss-certs-debuginfo-3.23-1.2.i586
mozilla-nss-debuginfo-3.23-1.2.i586
(gdb) bt
#0  0xb4801692 in nsLayoutUtils::GetLastSibling (aFrame=0xe5e5e5e5) at
/usr/src/debug/mozilla/layout/base/nsLayoutUtils.cpp:1797
#1  0xb47a12ec in nsFrameItems::AddChild (this=0xbfffcfe4, aChild=0xa1d47498)
    at /usr/src/debug/mozilla/layout/base/nsCSSFrameConstructor.cpp:646
#2  0xb47bd446 in nsFrameConstructorState::AddChild (this=0xbfffd084,
aNewFrame=0xa1d47498, aFrameItems=..., aContent=0xa39ed7e0,
    aStyleContext=0xa1d47298, aParentFrame=0xa4cb5db0, aCanBePositioned=false,
aCanBeFloated=false, aIsOutOfFlowPopup=false,
    aInsertAfter=false, aInsertAfterFrame=0x0) at
/usr/src/debug/mozilla/layout/base/nsCSSFrameConstructor.cpp:1245
#3  0xb47e6877 in nsCSSFrameConstructor::ConstructFrameFromItemInternal
(this=0xa4c7c500, aItem=..., aState=..., aParentFrame=0xa4cb5db0,
    aFrameItems=...) at
/usr/src/debug/mozilla/layout/base/nsCSSFrameConstructor.cpp:3913
#4  0xb47e71b4 in nsCSSFrameConstructor::ConstructFramesFromItem
(this=<optimized out>, aState=..., aIter=...,
    aParentFrame=<optimized out>, aFrameItems=...) at
/usr/src/debug/mozilla/layout/base/nsCSSFrameConstructor.cpp:6049
#5  0xb47e78a1 in nsCSSFrameConstructor::ConstructFramesFromItemList
(this=<optimized out>, aState=..., aItems=...,
    aParentFrame=<optimized out>, aFrameItems=...) at
/usr/src/debug/mozilla/layout/base/nsCSSFrameConstructor.cpp:10411
#6  0xb47e85a1 in nsCSSFrameConstructor::CreateAnonymousFrames
(this=0xa4c7c500, aState=..., aParent=0xa39ee2e0, aParentFrame=0xa4cb5db0,
    aPendingBinding=0x0, aChildItems=...) at
/usr/src/debug/mozilla/layout/base/nsCSSFrameConstructor.cpp:4108
#7  0xb47e8b5d in nsCSSFrameConstructor::BeginBuildingScrollFrame
(this=0xa4c7c500, aState=..., aContent=0xa39ee2e0,
    aContentStyle=0xa4cb50b8, aParentFrame=0xa4cb5618,
aScrolledPseudo=0xab21b8c0, aIsRoot=true, aNewFrame=@0xbfffd074: 0x0)
    at /usr/src/debug/mozilla/layout/base/nsCSSFrameConstructor.cpp:4516
#8  0xb47e8d7a in nsCSSFrameConstructor::SetUpDocElementContainingBlock
(this=0xa4c7c500, aDocElement=0xa39ee2e0)
    at /usr/src/debug/mozilla/layout/base/nsCSSFrameConstructor.cpp:2816
#9  0xb47efa30 in nsCSSFrameConstructor::ConstructDocElementFrame
(this=0xa4c7c500, aDocElement=0xa39ee2e0, aFrameState=0x0)
    at /usr/src/debug/mozilla/layout/base/nsCSSFrameConstructor.cpp:2353
#10 0xb47f0b76 in nsCSSFrameConstructor::ContentRangeInserted (this=0xa4c7c500,
aContainer=0x0, aStartChild=0xa39ee2e0, aEndChild=0x0,
    aFrameState=0x0, aAllowLazyConstruction=false) at
/usr/src/debug/mozilla/layout/base/nsCSSFrameConstructor.cpp:7599
#11 0xb47f1570 in nsCSSFrameConstructor::ContentInserted (this=0xa4c7c500,
aContainer=0x0, aChild=0xa39ee2e0, aFrameState=0x0,
    aAllowLazyConstruction=false) at
/usr/src/debug/mozilla/layout/base/nsCSSFrameConstructor.cpp:7489
#12 0xb483fcf4 in PresShell::Initialize (this=<optimized out>,
aWidth=<optimized out>, aHeight=<optimized out>)
    at /usr/src/debug/mozilla/layout/base/nsPresShell.cpp:1672
#13 0xb347d1f9 in nsContentSink::StartLayout (this=0xa5343480,
aIgnorePendingSheets=false)
    at /usr/src/debug/mozilla/dom/base/nsContentSink.cpp:1216
#14 0xb30d1742 in nsHtml5TreeOpExecutor::StartLayout (this=0xa5343480) at
/usr/src/debug/mozilla/parser/html/nsHtml5TreeOpExecutor.cpp:614
#15 0xb30f24a3 in nsHtml5TreeOperation::Perform (this=0xa4cc5770,
aBuilder=0xa5343480, aScriptElement=0xbfffd918)
    at /usr/src/debug/mozilla/parser/html/nsHtml5TreeOperation.cpp:823
#16 0xb30ef568 in nsHtml5TreeOpExecutor::RunFlushLoop (this=0xa5343480)
    at /usr/src/debug/mozilla/parser/html/nsHtml5TreeOpExecutor.cpp:451
#17 0xb30efa09 in nsHtml5ExecutorFlusher::Run (this=0xa4c269c0) at
/usr/src/debug/mozilla/parser/html/nsHtml5StreamParser.cpp:128
#18 0xb284acac in nsThread::ProcessNextEvent (this=<optimized out>,
aMayWait=<optimized out>, aResult=<optimized out>)
    at /usr/src/debug/mozilla/xpcom/threads/nsThread.cpp:994
#19 0xb2873bed in NS_ProcessNextEvent (aThread=<optimized out>, aMayWait=false)
at /usr/src/debug/mozilla/xpcom/glue/nsThreadUtils.cpp:297
#20 0xb2b5d5c5 in mozilla::ipc::MessagePump::Run (this=0xb0026640,
aDelegate=0xb796f600)
    at /usr/src/debug/mozilla/ipc/glue/MessagePump.cpp:95
#21 0xb2b3e4b6 in MessageLoop::RunInternal (this=0xb796f600) at
/usr/src/debug/mozilla/ipc/chromium/src/base/message_loop.cc:234
#22 MessageLoop::RunHandler (this=0xb796f600) at
/usr/src/debug/mozilla/ipc/chromium/src/base/message_loop.cc:227
#23 MessageLoop::Run (this=0xb796f600) at
/usr/src/debug/mozilla/ipc/chromium/src/base/message_loop.cc:201
#24 0xb4569537 in nsBaseAppShell::Run (this=0xab2fb5b0) at
/usr/src/debug/mozilla/widget/nsBaseAppShell.cpp:156
#25 0xb4e96268 in nsAppStartup::Run (this=0xab2fc4c0) at
/usr/src/debug/mozilla/toolkit/components/startup/nsAppStartup.cpp:281
#26 0xb4ee3d75 in XREMain::XRE_mainRun (this=0xbfffdcbc) at
/usr/src/debug/mozilla/toolkit/xre/nsAppRunner.cpp:4337
#27 0xb4ee48f8 in XREMain::XRE_main (this=0xbfffdcbc, argc=1, argv=0xbffff024,
aAppData=0xbfffde2c)
    at /usr/src/debug/mozilla/toolkit/xre/nsAppRunner.cpp:4434
#28 0xb4ee4bfd in XRE_main (argc=1, argv=0xbffff024, aAppData=0xbfffde2c,
aFlags=0)
    at /usr/src/debug/mozilla/toolkit/xre/nsAppRunner.cpp:4540
#29 0x80005134 in do_main (argc=1, argv=0xbffff024, envp=<optimized out>,
xreDirectory=0xb7966480)
    at /usr/src/debug/mozilla/browser/app/nsBrowserApp.cpp:220
#30 0x800043fc in main (argc=<optimized out>, argv=<optimized out>,
envp=<optimized out>)
    at /usr/src/debug/mozilla/browser/app/nsBrowserApp.cpp:360
(gdb)


--1467024087.4CB4576E1.15126
Date: Mon, 27 Jun 2016 10:41:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 986614
           Summary: VUL-0: CVE-2015-2753, CVE-2015-2754, 2015-2776: freexl: Multiple vulnerabilities
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: mpluskal-at-suse.com
          Reporter: mpluskal-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

FreeXL's shared strings and workbook functions are vulnerable to the
remote execution of arbitrary code and Denial of Service.  This can be
achieved through specially crafted workbooks from attackers.

CVE-2015-2753
   http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2753
CVE-2015-2754
   http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2754
CVE-2015-2776
   http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2776


body:
--1467105609.5d4ea50A0.9759
Date: Tue, 28 Jun 2016 09:20:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 986783
           Summary: caff not working with gpg2
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Other
          Assignee: premysl.janouch-at-suse.com
          Reporter: jsegitz-at-novell.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

gpg doesn't handle a missing trustdb.gpg, that causes caff (part of
signing-party) to fail. Fix is 23191d7851eae2217ecdac6484349849a24fd94a.

I have a fixed version in
https://build.opensuse.org/package/show/home:jsegitz:branches:openSUSE:Leap:42.1:Update/gpg2
and verified that is solves this issue

summary: caff not working with gpg2


--1467128493.6D02E0.25333
Date: Tue, 28 Jun 2016 15:41:33 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 986866
           Summary: virt-builder fails to initialize with guestfs error
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: pgonin-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

### Description of problem:

- Can't use virt-builder on latest Tumbleweed. Disk opening fails with guestfs
error on initialization step

### Version-Release number of affected component/package (if applicable):

openSUSE
VERSION="Tumbleweed"
VERSION_ID="20160625"

### Steps to Reproduce:

1. Install openSUSE Tumbleweed (as KVM Virt host)
2. install virt-builder (zypper in  guestfs-tools)
3. initialize virt-builder
  virt-builder opensuse-42.1

### Actual results:

- Executing of command fails with error message: virt-builder: symbol lookup
error: virt-builder: undefined symbol: guestfs___safe_malloc

full output:
gpg: Signature made Wed May 11 19:12:25 2016 CEST using RSA key ID 72174FC2
gpg: Good signature from "Virtualization OBS Project
<Virtualization-at-build.opensuse.org>" [expired]
gpg: Note: This key has expired!
Primary key fingerprint: 55A0 B34D 4950 1BB7 CA47  4F5A A193 FBB5 7217 4FC2
gpg: Signature made Wed Jun 22 16:54:35 2016 CEST using RSA key ID E1B768A0
gpg: Good signature from "Richard W.M. Jones <rjones-at-redhat.com>" [unknown]
gpg:                 aka "Richard W.M. Jones <rich-at-annexia.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: F777 4FB1 AD07 4A7E 8C87  67EA 9173 8F73 E1B7 68A0
[   4.0] Downloading:
http://download.opensuse.org/repositories/Virtualization:/virt-builder-images/images/openSUSE-Leap-42.1.x86_64-0.0.1-Build1.9.qcow2.xz
[   5.0] Planning how to build this image
[   5.0] Uncompressing
[  15.0] Converting qcow2 to raw
[  19.0] Opening the new disk
virt-builder: symbol lookup error: virt-builder: undefined symbol:
guestfs___safe_malloc


--1467147469.68e60.15031
Date: Tue, 28 Jun 2016 20:57:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 986891
           Summary: nvme-cli: "nvme list" returns error "nvme0 failed to map"
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: jthumshirn-at-suse.com
          Reporter: ken-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Running latest snapshot of Tumbleweed "20160625". I just stumbled across the
nvme cli tools and was playing around and noticed that I see a unexpected
behavior running the "nvme list" command on my setup.

Here's are some details from my system, let me know if there is something else
that would be helpful to see. I'll attach the output of strace'ing the command
also.

ken@klj3:~> ###############################################################
ken@klj3:~> cat /etc/os-release
NAME=openSUSE
VERSION="Tumbleweed"
VERSION_ID="20160625"
PRETTY_NAME="openSUSE Tumbleweed (20160625) (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:20160625"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
ID_LIKE="suse"
ken@klj3:~> ###############################################################
ken@klj3:~> uname -a
Linux klj3 4.6.2-1-default #1 SMP PREEMPT Fri Jun 10 08:12:44 UTC 2016
(2a68ef0) x86_64 x86_64 x86_64 GNU/Linux
ken@klj3:~> ###############################################################
ken@klj3:~> lsmod | grep nvme
nvme                   32768  4
nvme_core              53248  6 nvme
ken@klj3:~> ###############################################################
ken@klj3:~> rpm -qif /usr/sbin/nvme
Name        : nvme-cli
Version     : 0.7
Release     : 1.2
Architecture: x86_64
Install Date: Tue 28 Jun 2016 01:14:30 PM MDT
Group       : Hardware/Other
Size        : 178784
License     : GPL-2.0
Signature   : RSA/SHA256, Wed 15 Jun 2016 04:24:11 PM MDT, Key ID
b88b2fd43dbdc284
Source RPM  : nvme-cli-0.7-1.2.src.rpm
Build Date  : Wed 15 Jun 2016 04:23:58 PM MDT
Build Host  : lamb18
Relocations : (not relocatable)
Packager    : http://bugs.opensuse.org
Vendor      : openSUSE
URL         : https://github.com/linux-nvme/nvme-cli
Summary     : Core nvme tools
Description :
NVMe is a fast, scalable, direct attached storage interface. The nvme
cli rpm installs core management tools with minimal dependencies.
Distribution: openSUSE Tumbleweed
ken@klj3:~> ###############################################################
ken@klj3:~> sudo /usr/sbin/nvme --version
[sudo] password for root:
nvme version 0.7
ken@klj3:~> ###############################################################
ken@klj3:~> sudo /usr/sbin/nvme list
nvme0 failed to map
ken@klj3:~> ###############################################################
ken@klj3:~> sudo /usr/sbin/nvme id-ctrl /dev/nvme0
NVME Identify Controller:
vid     : 0x144d
ssvid   : 0x144d
sn      : S2GMNX0H410619A
mn      : Samsung SSD 950 PRO 512GB
fr      : 1B0QBXX7
rab     : 2
ieee    : 002538
cmic    : 0
mdts    : 5
cntlid  : 1
ver     : 0
rtd3r   : 0
rtd3e   : 0
oaes    : 0
oacs    : 0x7
acl     : 7
aerl    : 3
frmw    : 0x6
lpa     : 0x1
elpe    : 63
npss    : 4
avscc   : 0x1
apsta   : 0x1
wctemp  : 0
cctemp  : 0
mtfa    : 0
hmpre   : 0
hmmin   : 0
tnvmcap : 0
unvmcap : 0
rpmbs   : 0
sqes    : 0x66
cqes    : 0x44
nn      : 1
oncs    : 0x1f
fuses   : 0
fna     : 0x4
vwc     : 0x1
awun    : 255
awupf   : 0
nvscc   : 1
acwu    : 0
sgls    : 0
ps    0 : mp:6.50W operational enlat:5 exlat:5 rrt:0 rrl:0
          rwt:0 rwl:0 idle_power:- active_power:-
ps    1 : mp:5.80W operational enlat:30 exlat:30 rrt:1 rrl:1
          rwt:1 rwl:1 idle_power:- active_power:-
ps    2 : mp:3.60W operational enlat:100 exlat:100 rrt:2 rrl:2
          rwt:2 rwl:2 idle_power:- active_power:-
ps    3 : mp:0.0700W non-operational enlat:500 exlat:5000 rrt:3 rrl:3
          rwt:3 rwl:3 idle_power:- active_power:-
ps    4 : mp:0.0050W non-operational enlat:2000 exlat:22000 rrt:4 rrl:4
          rwt:4 rwl:4 idle_power:- active_power:-
ken@klj3:~> ###############################################################
ken@klj3:~> sudo hwinfo --storage
[sudo] password for root:
13: PCI 17.0: 0106 SATA controller (AHCI 1.0)
  [Created at pci.366]
  Unique ID: abAj.FeTPSrFXjh6
  SysFS ID: /devices/pci0000:00/0000:00:17.0
  SysFS BusID: 0000:00:17.0
  Hardware Class: storage
  Model: "Intel SATA controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0xa102
  SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
  SubDevice: pci 0xb005
  Revision: 0x31
  Driver: "ahci"
  Driver Modules: "ahci"
  Memory Range: 0xdf748000-0xdf749fff (rw,non-prefetchable)
  Memory Range: 0xdf74c000-0xdf74c0ff (rw,non-prefetchable)
  I/O Ports: 0xf050-0xf057 (rw)
  I/O Ports: 0xf040-0xf043 (rw)
  I/O Ports: 0xf020-0xf03f (rw)
  Memory Range: 0xdf74b000-0xdf74b7ff (rw,non-prefetchable)
  IRQ: 127 (359 events)
  Module Alias: "pci:v00008086d0000A102sv00001458sd0000B005bc01sc06i01"
  Config Status: cfg=no, avail=yes, need=no, active=unknown

36: PCI b00.0: 0106 SATA controller (AHCI 1.0)
  [Created at pci.366]
  Unique ID: IluS.md46SIO4oX3
  Parent ID: HnsE.WxDKq3cBDi0
  SysFS ID: /devices/pci0000:00/0000:00:1c.5/0000:0b:00.0
  SysFS BusID: 0000:0b:00.0
  Hardware Class: storage
  Model: "ASMedia ASM1062 Serial ATA Controller"
  Vendor: pci 0x1b21 "ASMedia Technology Inc."
  Device: pci 0x0612 "ASM1062 Serial ATA Controller"
  SubVendor: pci 0x1b21 "ASMedia Technology Inc."
  SubDevice: pci 0x1062
  Revision: 0x02
  Driver: "ahci"
  Driver Modules: "ahci"
  I/O Ports: 0xc050-0xc057 (rw)
  I/O Ports: 0xc040-0xc043 (rw)
  I/O Ports: 0xc030-0xc037 (rw)
  I/O Ports: 0xc020-0xc023 (rw)
  I/O Ports: 0xc000-0xcfff (rw)
  Memory Range: 0xdf310000-0xdf3101ff (rw,non-prefetchable)
  Memory Range: 0xdf300000-0xdf30ffff (ro,non-prefetchable,disabled)
  IRQ: 128 (no events)
  Module Alias: "pci:v00001B21d00000612sv00001B21sd00001062bc01sc06i01"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #18 (PCI bridge)

37: PCI c00.0: 0106 SATA controller (AHCI 1.0)
  [Created at pci.366]
  Unique ID: zb5c.1FoTXauEYC6
  Parent ID: 1GTX.3B3aGjIXoQ0
  SysFS ID: /devices/pci0000:00/0000:00:1d.0/0000:0c:00.0
  SysFS BusID: 0000:0c:00.0
  Hardware Class: storage
  Model: "Samsung Electronics SATA controller"
  Vendor: pci 0x144d "Samsung Electronics Co Ltd"
  Device: pci 0xa801
  SubVendor: pci 0x144d "Samsung Electronics Co Ltd"
  SubDevice: pci 0xa801
  Revision: 0x01
  Driver: "ahci"
  Driver Modules: "ahci"
  Memory Range: 0xdf200000-0xdf201fff (rw,non-prefetchable)
  IRQ: 129 (127 events)
  Module Alias: "pci:v0000144Dd0000A801sv0000144Dsd0000A801bc01sc06i01"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #19 (PCI bridge)

38: PCI d00.0: 0108 Non-Volatile memory controller (NVM Express)
  [Created at pci.366]
  Unique ID: fSIl.bG_CoARfDl8
  Parent ID: VZQt.7rqZB+mLvy1
  SysFS ID: /devices/pci0000:00/0000:00:1d.4/0000:0d:00.0
  SysFS BusID: 0000:0d:00.0
  Hardware Class: storage
  Model: "Samsung Electronics Non-Volatile memory controller"
  Vendor: pci 0x144d "Samsung Electronics Co Ltd"
  Device: pci 0xa802
  SubVendor: pci 0x144d "Samsung Electronics Co Ltd"
  SubDevice: pci 0xa801
  Revision: 0x01
  Driver: "nvme"
  Driver Modules: "nvme"
  Memory Range: 0xdf110000-0xdf113fff (rw,non-prefetchable)
  I/O Ports: 0xb000-0xbfff (rw)
  Memory Range: 0xdf100000-0xdf10ffff (ro,non-prefetchable,disabled)
  IRQ: 16 (no events)
  Module Alias: "pci:v0000144Dd0000A802sv0000144Dsd0000A801bc01sc08i02"
  Driver Info #0:
    Driver Status: nvme is active
    Driver Activation Cmd: "modprobe nvme"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #20 (PCI bridge)
ken@klj3:~> ###############################################################
ken@klj3:~> sudo hwinfo --disk
33: IDE 400.0: 10600 Disk
  [Created at block.245]
  Unique ID: 3OOL.IrwknOm36uA
  Parent ID: abAj.FeTPSrFXjh6
  SysFS ID: /class/block/sda
  SysFS BusID: 4:0:0:0
  SysFS Device Link:
/devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0
  Hardware Class: disk
  Model: "OCZ-VERTEX2"
  Device: "OCZ-VERTEX2"
  Revision: "1.28"
  Serial ID: "OCZ-2E41900K2K02480N"
  Driver: "ahci", "sd"
  Driver Modules: "ahci"
  Device File: /dev/sda
  Device Files: /dev/sda, /dev/disk/by-id/ata-OCZ-VERTEX2_OCZ-2E41900K2K02480N,
/dev/disk/by-id/scsi-0ATA_OCZ-VERTEX2_OCZ-2E41900K2K02480N,
/dev/disk/by-id/scsi-1ATA_OCZ-VERTEX2_OCZ-2E41900K2K02480N,
/dev/disk/by-id/scsi-35e83a97f3738b409,
/dev/disk/by-id/scsi-SATA_OCZ-VERTEX2_OCZ-2E41900K2K02480N,
/dev/disk/by-id/wwn-0x5e83a97f3738b409,
/dev/disk/by-path/pci-0000:00:17.0-ata-5
  Device Number: block 8:0-8:15
  Geometry (Logical): CHS 13985/255/63
  Size: 224674128 sectors a 512 bytes
  Capacity: 107 GB (115033153536 bytes)
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #7 (SATA controller)

34: IDE 500.0: 10600 Disk
  [Created at block.245]
  Unique ID: WZeP.ix0B37fqc49
  Parent ID: abAj.FeTPSrFXjh6
  SysFS ID: /class/block/sdb
  SysFS BusID: 5:0:0:0
  SysFS Device Link:
/devices/pci0000:00/0000:00:17.0/ata6/host5/target5:0:0/5:0:0:0
  Hardware Class: disk
  Model: "WDC WD6001FZWX-0"
  Vendor: "WDC"
  Device: "WD6001FZWX-0"
  Revision: "1A01"
  Serial ID: "WD-WX11D26H47FC"
  Driver: "ahci", "sd"
  Driver Modules: "ahci"
  Device File: /dev/sdb
  Device Files: /dev/sdb,
/dev/disk/by-id/ata-WDC_WD6001FZWX-00A2VA0_WD-WX11D26H47FC,
/dev/disk/by-id/scsi-0ATA_WDC_WD6001FZWX-0_WD-WX11D26H47FC,
/dev/disk/by-id/scsi-1ATA_WDC_WD6001FZWX-00A2VA0_WD-WX11D26H47FC,
/dev/disk/by-id/scsi-350014ee262b84b61,
/dev/disk/by-id/scsi-SATA_WDC_WD6001FZWX-0_WD-WX11D26H47FC,
/dev/disk/by-id/scsi-SATA_WDC_WD6001FZWX-_WD-WX11D26H47FC,
/dev/disk/by-id/wwn-0x50014ee262b84b61,
/dev/disk/by-path/pci-0000:00:17.0-ata-6
  Device Number: block 8:16-8:31
  Geometry (Logical): CHS 729601/255/63
  Size: 11721045168 sectors a 512 bytes
  Capacity: 5589 GB (6001175126016 bytes)
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #7 (SATA controller)

35: IDE 800.0: 10600 Disk
  [Created at block.245]
  Unique ID: _kuT.vb+Gg6fV9O3
  Parent ID: zb5c.1FoTXauEYC6
  SysFS ID: /class/block/sdc
  SysFS BusID: 8:0:0:0
  SysFS Device Link:
/devices/pci0000:00/0000:00:1d.0/0000:0c:00.0/ata9/host8/target8:0:0/8:0:0:0
  Hardware Class: disk
  Model: "SAMSUNG MZHPV256"
  Vendor: "SAMSUNG"
  Device: "MZHPV256"
  Revision: "500Q"
  Serial ID: "S1X2NYAH200990"
  Driver: "ahci", "sd"
  Driver Modules: "ahci"
  Device File: /dev/sdc
  Device Files: /dev/sdc,
/dev/disk/by-id/ata-SAMSUNG_MZHPV256HDGL-00000_S1X2NYAH200990,
/dev/disk/by-id/scsi-0ATA_SAMSUNG_MZHPV256_S1X2NYAH200990,
/dev/disk/by-id/scsi-1ATA_SAMSUNG_MZHPV256HDGL-00000_S1X2NYAH200990,
/dev/disk/by-id/scsi-35002538900050768,
/dev/disk/by-id/scsi-SATA_SAMSUNG_MZHPV256S1X2NYAH200990,
/dev/disk/by-id/scsi-SATA_SAMSUNG_MZHPV256_S1X2NYAH200990,
/dev/disk/by-id/scsi-SATA_SAMSUNG_MZHPV25S1X2NYAH200990,
/dev/disk/by-id/wwn-0x5002538900050768,
/dev/disk/by-path/pci-0000:0c:00.0-ata-1
  Device Number: block 8:32-8:47
  Geometry (Logical): CHS 31130/255/63
  Size: 500118192 sectors a 512 bytes
  Capacity: 238 GB (256060514304 bytes)
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #31 (SATA controller)

36: PCI 00.0: 10600 Disk
  [Created at block.245]
  Unique ID: wLCS.zK5ndPYbgd0
  Parent ID: fSIl.bG_CoARfDl8
  SysFS ID: /class/block/nvme0n1
  SysFS BusID: nvme0
  SysFS Device Link: /devices/pci0000:00/0000:00:1d.4/0000:0d:00.0/nvme/nvme0
  Hardware Class: disk
  Model: "Samsung Electronics Samsung SSD 950"
  Vendor: pci 0x144d "Samsung Electronics Co Ltd"
  Device: pci 0xa802 "Samsung SSD 950"
  SubVendor: pci 0x144d "Samsung Electronics Co Ltd"
  SubDevice: pci 0xa801
  Revision: "BXX7"
  Serial ID: "S2GMNX0H410619A"
  Driver: "nvme"
  Driver Modules: "nvme"
  Device File: /dev/nvme0n1
  Device Number: block 259:0
  Geometry (Logical): CHS 488386/64/32
  Size: 1000215216 sectors a 512 bytes
  Capacity: 476 GB (512110190592 bytes)
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #32 (Non-Volatile memory controller)
ken@klj3:~> ###############################################################


--1467155619.fdC32d0.29776
Date: Tue, 28 Jun 2016 23:13:39 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 986901
           Summary: Steam: Steam controller only works as virtual keyboard not as gamepad
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: SUSE Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: f.thiessen-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

As the title says the steam controller only works as keyboard not as gamepad.
This seems to be related with missing permissions set for /dev/uinput.

On start up steam prints an error message that it could not access / write to
/dev/uinput and so the virtual gamepad will not work (I can confirm this).
Looking at uinput it has the permission 600 and root set as user and group.

Manually chmod it to 666 will work until next reboot, but that is only a dirty
hack.
There should be a command in the udev rule that’s sets the uinput to 660 and
group e.g. games so every user in games can acces the controller.
Something like this:

KERNEL==”uinput”, GROUP="games", MODE:=”0660″


--1467197987.E4c1DFE4.26334
Date: Wed, 29 Jun 2016 10:59:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 986953
           Summary: whois: updated TLD, servers, gTLDs and IPv4 allocations
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          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
                CC: kstreitova-at-suse.com, puzel-at-suse.com
          Found By: Community User
           Blocker: ---

13.2 ships with whois 5.2.0
42.1 ships with whois 5.2.10

There have been a number of compatible updates in the 5.2.x series to 5.2.12
which update various TLD whois servers, gTLD lists, IPv4 allocation. Updating
the version will allow more domains to be queried successfully.


--1467272700.6CadEe0.21712
Date: Thu, 30 Jun 2016 07:45:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 987139
           Summary: gnutls: make test fails after Jun 29 12:35:31 2016 GMT
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

gnutls no longer builds / passes the test suite in Tumbleweed, due to an
expired certificate

>[  871s] FAIL: name-constraints
>[  871s] ======================
>[  871s]
>[  871s] Loaded 3 certificates, 1 CAs and 0 CRLs
>[  871s]
>[  871s] 	Subject: C=US,O=Foo Bar Inc.,CN=Foo Bar Sub CA 1,OU=Public Key Infrastructure
>[  871s] 	Issuer: C=US,O=Foo Bar Inc.,CN=Foo Bar Root CA,OU=Public Key Infrastructure
>[  871s] 	Output: Not verified. The certificate is NOT trusted. The certificate issuer is unknown.
>[  871s]
>[  871s] 	Subject: C=US,O=Foo Bar Inc.,CN=Foo Bar Sub CA 1,OU=Public Key Infrastructure
>[  871s] 	Issuer: C=US,O=Foo Bar Inc.,CN=Foo Bar Root CA,OU=Public Key Infrastructure
>[  871s] 	Checked against: C=US,O=Foo Bar Inc.,CN=Foo Bar Sub CA 1,OU=Public Key Infrastructure
>[  871s] 	Output: Verified. The certificate is trusted.
>[  871s]
>[  871s] 	Subject: C=US,O=Foo Bar Inc.,CN=bazz.foobar.com
>[  871s] 	Issuer: C=US,O=Foo Bar Inc.,CN=Foo Bar Sub CA 1,OU=Public Key Infrastructure
>[  871s] 	Checked against: C=US,O=Foo Bar Inc.,CN=Foo Bar Sub CA 1,OU=Public Key Infrastructure
>[  871s] 	Output: Not verified. The certificate is NOT trusted. The certificate chain uses expired certificate.
>[  871s]
>[  871s] Chain verification output: Not verified. The certificate is NOT trusted. The certificate chain uses expired certificate.

the certificate in question shows (using openssl x509 -in
name-constraints-ip.pem -text):
>    Signature Algorithm: sha1WithRSAEncryption
>        Issuer: C=US, O=Foo Bar Inc., CN=Foo Bar Sub CA 1, OU=Public Key Infrastructure
>        Validity
>            Not Before: Jun 30 12:35:31 2015 GMT
>            Not After : Jun 29 12:35:31 2016 GMT

See for example
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:A/gnutls/standard/x86_64


--1467282092.daa4fE30.16879
Date: Thu, 30 Jun 2016 10:21:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 987170
           Summary: too strict permissions for /sbin/dhclient-script
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: ptoscano-at-redhat.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

/sbin/dhclient-script has way too strict permissions:

  -rwxr-x-


body:
--1467287579.73Fb4.10120
Date: Thu, 30 Jun 2016 11:52:59 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 987182
           Summary: x11vnc crashes
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: X11 Applications
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: marvin24-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 682678
  --> http://bugzilla.opensuse.org/attachment.cgi?id=682678&action=edit
ouput after crash

x11vnc often crashes when using pul-down menus. Output attached. Bug seems to
be similar to redhat bug #1282009.

summary: x11vnc crashes


--1467377637.Eb04b0.18458
Date: Fri, 1 Jul 2016 12:53:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 987358
           Summary: ucode-intel update in TW snapshot 0619 breaks system start-up
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: robby.engelmann@igfs-ev.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I picked the snapshot from openqa and updated the system using zypper dup
(from
http://openqa.opensuse.org/assets/repo/openSUSE-Tumbleweed-oss-i586-x86_64-Snapshot20160629).
I did not see any fails during the upgrade. On the next restart, grub started
normally. Then the screen with "loading kernel..." appears and the startup
stops at "loading initrd...". Nothing happens from there.

Updating all other packages except for ucode-intel leads to a working system.


--1467452761.6Dae63200.22848
Date: Sat, 2 Jul 2016 09:46:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 987462
           Summary: collectd: collectd.conf is in wrong place
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: matwey.kornilov-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,

I am running collectd-5.4.2-1.3.x86_64 at Leap 42.1

collectd.conf is installed into /etc

# rpm -q collectd-5.4.2-1.3.x86_64 --list
/etc/collectd
/etc/collectd.conf
...

at the same time, when I try to start collectd first time, then I see the
following:

# journalctl -u collectd.service


--1467568697.B28c0.24337
Date: Sun, 3 Jul 2016 17:58:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 987483
           Summary: server:monitoring:zabbix/zabbix30
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: x86-64
                OS: openSUSE 42.1
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: syntron-at-web.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The ownership of /var/run/zabbix is set to root.zabbixs if zabbix-java-gateway
is used. The reason is the tmpfile which is created for this zabbix rpm. It
overwrites the setting for zabbix agentd (ownership root.zabbix). As result
zabbix-agentd is not started on boot (wrong ownership of run dir). If this rpm
is removed the system works fine.


body:
--1467700030.5b83e20.18614
Date: Tue, 5 Jul 2016 06:27:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 987607
           Summary: No module named '_LibAppArmor'
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: ushamim-at-linux.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hi,

I get the following error when trying to run the aa-* tools on TW. It seems to
happen after the latest update. Apparmor is installed only from the TW-OSS
repo.

===========================
root# aa-logprof
Traceback (most recent call last):
  File "/usr/lib64/python3.5/site-packages/LibAppArmor/__init__.py", line 18,
in swig_import_helper
    return importlib.import_module(mname)
  File "/usr/lib64/python3.5/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 986, in _gcd_import
  File "<frozen importlib._bootstrap>", line 969, in _find_and_load
  File "<frozen importlib._bootstrap>", line 956, in _find_and_load_unlocked
ImportError: No module named '_LibAppArmor'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/sbin/aa-logprof", line 18, in <module>
    import apparmor.aa as apparmor
  File "/usr/lib/python3.5/site-packages/apparmor/aa.py", line 29, in <module>
    import apparmor.logparser
  File "/usr/lib/python3.5/site-packages/apparmor/logparser.py", line 19, in
<module>
    import LibAppArmor
  File "/usr/lib64/python3.5/site-packages/LibAppArmor/__init__.py", line 21,
in <module>
    _LibAppArmor = swig_import_helper()
  File "/usr/lib64/python3.5/site-packages/LibAppArmor/__init__.py", line 20,
in swig_import_helper
    return importlib.import_module('_LibAppArmor')
  File "/usr/lib64/python3.5/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ImportError: No module named '_LibAppArmor'
===========================

summary: No module named '_LibAppArmor'


body:
--1467724236.FFa344.11180
Date: Tue, 5 Jul 2016 13:10:36 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 987668
           Summary: libvirtd: Failed to notify systemd
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Other
          Assignee: virt-bugs-at-suse.de
          Reporter: ebischoff-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After an upgrade of Leap 12.1, more or less on July 1st, a problem appeared
when trying to restart libvirtd with

  # systemctl restart libvirtd

this commands times out after a while.

In the background, libvirtd daemon is restarted at regular intervals (the PID
keeps changing). In /var/log/messages, one finds every two minutes:

  2016-07-05T14:44:15.376938+02:00 tegan systemd[1]: Starting Virtualization
daemon...
  2016-07-05T14:44:15.425527+02:00 tegan libvirtd[15535]: libvirt version:
2.0.0
  2016-07-05T14:44:15.426024+02:00 tegan libvirtd[15535]: hostname: tegan
  2016-07-05T14:44:15.426555+02:00 tegan libvirtd[15535]: Failed to notify
systemd

Problem is fairly similar, at least in its symptoms, to:

  https://bugzilla.redhat.com/show_bug.cgi?id=1314881

Version info:

  $ rpm -q libvirt
  libvirt-2.0.0-590.1.x86_64

  $ rpm -q systemd
  systemd-210-95.1.x86_64

summary: libvirtd: Failed to notify systemd


--1467725293.BCfbD0.6980
Date: Tue, 5 Jul 2016 13:28:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 987670
           Summary: [mga UMS] Lower Edge of Screen cut off due to Miscalculation of Shadow Buffer Size
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: CONFIRMED
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: eich-at-suse.com
          Reporter: eich-at-suse.com
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
                CC: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: Development
           Blocker: ---

The mga UMS driver uses the screen width for calculation of the shadow buffer
size instead of the stride. The stride in pScrn->displayWidth may however
differ from the screen width.
In this cases the lower edge of the screen will be cut off.


--1467740067.f72Fd8ba2.17600
Date: Tue, 5 Jul 2016 17:34:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 987720
           Summary: Egypt (Africa/Cairo) DST cancelled, 2016f timezone release
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Maintenance
          Assignee: astieger-at-suse.com
          Reporter: astieger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: alnovak-at-suse.com, andreas.taschner-at-suse.com,
                    astieger-at-suse.com, brent.griggs-at-suse.com,
                    jake.norris-at-suse.com, jeff.ray-at-suse.com,
                    ntsbugsiebint-bugs-at-forge.provo.novell.com,
                    roger.whittaker-at-suse.com, rosuna-at-suse.com,
                    wpreston-at-suse.com
            Blocks: 982833
          Found By: ---
           Blocker: ---

http://mm.icann.org/pipermail/tz-announce/2016-July/000040.html

Customers should avoid installing the PTF or the update already released for
SLE 12:

http://mm.icann.org/pipermail/tz-announce/2016-July/000040.html

> The 2016f release of the tz code and data is available. It reflects the
> following changes, which were either circulated on the tz mailing list
> or are relatively minor technical or administrative changes:
>
>    Changes affecting future time stamps
>
>      The Egyptian government changed its mind on short notice, and
>      Africa/Cairo will not introduce DST starting 2016-07-07 after all.


--1467798971.07e380.8897
Date: Wed, 6 Jul 2016 09:56:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 987846
           Summary: VUL-0: CVE-2016-6160: tcpreplay: segfault upon huge frames, missing size check
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: mkubecek-at-suse.com
          Reporter: astieger-at-suse.com
        QA Contact: security-team-at-suse.de
                CC: mkubecek-at-suse.com, security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

the tcprewrite program, part of the tcpreplay suite, does not check the size of
the frames it processes. Huge frames may trigger a segmentation fault, and they
occur on interfaces with an MTU of or close to 65536. For example, the loopback
interface lo of the Linux kernel has such a value.

This has been assigned CVE-2016-6160.

Fix is in the debian bug.

network:utilities/tcpreplay 4.1.1
openSUSE:Factory/tcpreplay 4.1.1

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-6160
http://seclists.org/oss-sec/2016/q3/10
http://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-6160.html
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829350


--1467884262.DFdDFdc4.6935
Date: Thu, 7 Jul 2016 09:37:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 988017
           Summary: Long compile time with -fsanitize=undefined
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Basesystem
          Assignee: matz-at-suse.com
          Reporter: lpechacek-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: mliska-at-suse.cz
          Found By: ---
           Blocker: ---

While working on a Qt5 application I have noticed that a few files compile
extremely slowly with -fsanitize=undefined.  Attached tarball contains example
code which compiles within two seconds without UBSan and takes over twelve
minutes with UBSan on my test system.

lpechacek@tweed:/tmp/long-compile> time bash -x long_compile.sh
+ g++ -c -pipe -fsanitize=undefined -Wextra -g -Wall -W -D_REENTRANT -fPIC
-DQT_QML_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_QML_LIB -DQT_NETWORK_LIB
-DQT_SQL_LIB -DQT_XML_LIB -DQT_CORE_LIB -I../../../quickbox/tools/qsqlmon -I.
-I../../../quickbox/libqf/libqfcore/include
-I../../../quickbox/libqf/libqfqmlwidgets/include
-I../../../quickbox/tools/qsqlmon/src -isystem /usr/include/qt5 -isystem
/usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem
/usr/include/qt5/QtQml -isystem /usr/include/qt5/QtNetwork -isystem
/usr/include/qt5/QtSql -isystem /usr/include/qt5/QtXml -isystem
/usr/include/qt5/QtCore -I. -I. -I/usr/lib64/qt5/mkspecs/linux-g++ -o
dlgcolumndef.o dlgcolumndef.cpp
SOFT ASSERT: "item" in file debuggerkitinformation.cpp, line 346

real    12m6.092s
user    12m5.936s
sys    0m0.208s
lpechacek@tweed:/tmp/long-compile> time g++ -c -pipe -Wextra -g -Wall -W
-D_REENTRANT -fPIC -DQT_QML_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_QML_LIB
-DQT_NETWORK_LIB -DQT_SQL_LIB -DQT_XML_LIB -DQT_CORE_LIB
-I../../../quickbox/tools/qsqlmon -I.
-I../../../quickbox/libqf/libqfcore/include
-I../../../quickbox/libqf/libqfqmlwidgets/include
-I../../../quickbox/tools/qsqlmon/src -isystem /usr/include/qt5 -isystem
/usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem
/usr/include/qt5/QtQml -isystem /usr/include/qt5/QtNetwork -isystem
/usr/include/qt5/QtSql -isystem /usr/include/qt5/QtXml -isystem
/usr/include/qt5/QtCore -I. -I. -I/usr/lib64/qt5/mkspecs/linux-g++ -o
dlgcolumndef.o dlgcolumndef.cpp

real    0m1.889s
user    0m1.792s
sys    0m0.160s


--1467880506.c8F710a4.29379
Date: Thu, 7 Jul 2016 08:35:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 988009
           Summary: linux-vanilla fails to compile because GCC does not support plugins
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: rguenther-at-suse.com
          Reporter: mbrugger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: afaerber-at-suse.com, agraf-at-suse.com, dmueller-at-suse.com,
                    schwab-at-suse.com
          Found By: ---
           Blocker: ---

[  266s] ../scripts/gcc-plugin.sh: line 19: g++: command not found
[  266s]   HOSTCC  scripts/basic/bin2c
[  266s] Cannot use CONFIG_GCC_PLUGINS: your gcc installation does not support
plugins, perhaps the necessary headers are missing?
[  266s] make[1]: *** [scripts/Makefile.gcc-plugins:50: gcc-plugins-check]
Error 1
[  266s] make[1]: *** Waiting for unfinished jobs....

https://build.opensuse.org/package/live_build_log/Kernel:linux-next/kernel-vanilla/ARM/aarch64


body:
--1467874357.684ABe733.5260
Date: Thu, 7 Jul 2016 06:52:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 987990
           Summary: Wrong virtualbox-guest tools installed
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: hkuehnemund-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Leap 42.1 (with the last update from ~April) running on VirtualBox 5.0.24 on a
Windows host. VirtualBox guest tools 5.0.24 from VirtualBox Guest Additions CD
are installed.

Now running "zypper up" throwing errors:

Issue 1:

virtualbox-guest-kmp-default-5.0.22_k4.1.26_21-19.1.x86_64 is being installed
despite the fact that the VM runs on 5.0.24 ...

Issue 2:

There is no check if GuestAdditions are installed from VirtualBox direcly,
leading to this error:

(31/76) Installing: virtualbox-guest-kmp-default-5.0.22_k4.1.26_21-19.1.x86_64
............................................[done]
Additional rpm output:
depmod: WARNING: //lib/modules/4.1.26-21-default/misc/vboxvideo.ko disagrees
about version of symbol VBoxGuest_RTLogBackdoorPrintf
depmod: WARNING: //lib/modules/4.1.26-21-default/misc/vboxvideo.ko disagrees
about version of symbol VBoxGuest_RTErrConvertToErrno
depmod: WARNING: //lib/modules/4.1.26-21-default/misc/vboxvideo.ko disagrees
about version of symbol VBoxGuest_RTAssertShouldPanic
depmod: WARNING: //lib/modules/4.1.26-21-default/misc/vboxvideo.ko disagrees
about version of symbol VBoxGuest_RTAssertMsg1Weak
depmod: WARNING: //lib/modules/4.1.26-21-default/misc/vboxvideo.ko disagrees
about version of symbol VBoxGuest_RTAssertMsg2Weak
Warning: /lib/modules/4.1.26-21-default is inconsistent
Warning: weak-updates symlinks might not be created
Creating initrd: /boot/initrd-4.1.26-21-default
[...]

Expected result for issue 1:

Install guest additions in the correct version

Expected result for issue 2:

Ask, if user wants to install guest tools from Leap if GuestAdditions from
VirtualBox are already installed for the former kernel. User might not like to
use the packages from SUSE ... (e.g. because of issue 1, as we deliver not the
current one)

summary: Wrong virtualbox-guest tools installed


body:
Build Identifier:

Steam crashes immediately after starting due this bug
https://github.com/ValveSoftware/steam-for-linux/issues/4504

Reproducible: Always

Steps to Reproduce:
1. Install steam 1.0.0.52
2. Run it
Actual Results:
Steam crashes with segmentation fault.

Expected Results:
Steam works fine.

There is fix/workaround for this
http://www.gearsongallium.com/?p=3276#utm_source=feedly&utm_medium=rss&utm_campaign=fix-for-segmentation-fault-in-libcrypto-steam-beta
mesa must be compiled with libnettle:
--with-sha1=libnettle

pkgs: Mesa steam

summary: Steam segmentation fault


body:
--1468055236.a6754F2c0.24690
Date: Sat, 9 Jul 2016 09:07:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 988274
           Summary: gij-4.8 is broken for armv7l
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.2
          Hardware: armv7
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Java
          Assignee: bnc-team-java-at-forge.provo.novell.com
          Reporter: matwey.kornilov-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,

While porting Leap 42.2 to armv7l I've found the following.

Initial issue was the failed xml-commons build. The error is the following:

[   76s]
/home/abuild/rpmbuild/BUILD/xml-commons-1.3.04/xml-commons-1_0_b2/build.xml:49:
The following error occurred while executing this line:
[   76s]
/home/abuild/rpmbuild/BUILD/xml-commons-1.3.04/xml-commons-1_0_b2/java/external/build.xml:120:
java.lang.IllegalArgumentException: 16877=40755 will not fit in octal number
buffer of length -1292065064
[   76s]    at
org.apache.tools.tar.TarUtils.formatUnsignedOctalString(TarUtils.java:387)
[   76s]    at
org.apache.tools.tar.TarUtils.formatLongOctalBytes(TarUtils.java:440)
[   76s]    at
org.apache.tools.tar.TarUtils.formatLongOctalOrBinaryBytes(TarUtils.java:470)
[   76s]    at
org.apache.tools.tar.TarEntry.writeEntryHeaderField(TarEntry.java:866)
[   76s]    at
org.apache.tools.tar.TarEntry.writeEntryHeader(TarEntry.java:819)
[   76s]    at
org.apache.tools.tar.TarOutputStream.putNextEntry(TarOutputStream.java:305)
[   76s]    at org.apache.tools.ant.taskdefs.Tar.tarResource(Tar.java:480)
[   76s]    at org.apache.tools.ant.taskdefs.Tar.tarFile(Tar.java:354)
[   76s]    at org.apache.tools.ant.taskdefs.Tar.tar(Tar.java:669)
[   76s]    at org.apache.tools.ant.taskdefs.Tar.execute(Tar.java:314)
[   76s]    at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
[   76s]    at java.lang.reflect.Method.invoke(libgcj.so.14)
[   76s]    at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[   76s]    at org.apache.tools.ant.Task.perform(Task.java:348)
[   76s]    at org.apache.tools.ant.Target.execute(Target.java:435)
[   76s]    at org.apache.tools.ant.Target.performTasks(Target.java:456)
[   76s]    at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
[   76s]    at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
[   76s]    at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
[   76s]    at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441)
[   76s]    at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
[   76s]    at java.lang.reflect.Method.invoke(libgcj.so.14)
[   76s]    at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[   76s]    at org.apache.tools.ant.Task.perform(Task.java:348)
[   76s]    at org.apache.tools.ant.Target.execute(Target.java:435)
[   76s]    at org.apache.tools.ant.Target.performTasks(Target.java:456)
[   76s]    at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
[   76s]    at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
[   76s]    at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[   76s]    at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
[   76s]    at org.apache.tools.ant.Main.runBuild(Main.java:851)
[   76s]    at org.apache.tools.ant.Main.startAnt(Main.java:235)
[   76s]    at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
[   76s]    at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)

Here, -1292065064 randomly changes with every rebuild. Inspecting ant source
code, one may found that length is essentially compile time constant is this
context, so it cannot be -1292065064.
Then I used online Java decompiler to produce the source code from ant.jar in
order to check whether gcc java compiler produces relevant code.
In the decompiled source code, the length variable is also compile time
constant.

When I try to use java-1_8_0-openjdk java-1_8_0-openjdk-devel instead of
java-1_5_0-gcj-compat-devel to build xml-commons package, the build is
successful. The same ant rpm package is used as before.
Here I can conclude that there is an issue in java 1.5.0 gcj compat runtime.
Unfortunately, I have no idea how could I debug it.

summary: gij-4.8 is broken for armv7l


body:
--1468128097.0d3B20.24060
Date: Sun, 10 Jul 2016 05:21:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 988279
           Summary: qemu-bridge-helper not useable by non root user
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: clark.boylan-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When attempting to run virt-install as a non root user that is a member of the
libvirt, kvm, and qemu groups the virt-install process fails to run
qemu-bridge-helper. This appears to happen for two reasons:

1) apparmor is preventing this.
2) qemu-bridge-helper is not setuid.

Command to reproduce:
virt-install -n test-instance -r 2048 --os-type=linux --os-variant=ubuntu15.10
--disk
/home/clark/virt/disks/xenial-server-cloudimg-amd64-disk1.img,device=disk,bus=virtio
--disk /home/clark/virt/disks/init.iso,device=cdrom,bus=virtio -w
bridge=br0,model=virtio --noautoconsole --import

Log from audit.log:
type=AVC msg=audit(1468123876.616:558): apparmor="DENIED" operation="exec"
profile="/usr/sbin/libvirtd" name="/usr/lib/qemu-bridge-helper" pid=19746
comm="libvirtd" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

Error when apparmor prevents this:
ERROR    internal error: /usr/lib/qemu-bridge-helper --use-vnet --br=br0
--fd=22: failed to communicate with bridge helper: Transport endpoint is not
connected
stderr=libvirt:  error : cannot execute binary /usr/lib/qemu-bridge-helper:
Permission denied

Error when not setuid:
ERROR    internal error: /usr/lib/qemu-bridge-helper --use-vnet --br=br0
--fd=22: failed to communicate with bridge helper: Transport endpoint is not
connected
stderr=failed to create tun device: Operation not permitted

I managed to correct the apparmor issue by copy pasting the qemu-bridge-helper
content from /etc/apparmor.d/abstractions/libvirt-qemu and appending it to the
end of the profile in /etc/apparmor.d/usr.sbin.libvirtd. This prevented
apparmor from denying my access but then I ran into the tun device issue.

To correct the tun device issue I had to chmod 4755
/usr/lib/qemu-bridge-helper. With that done virt-install works as expected and
starts the virtual machine on the specified bridge.

I do not know if either of these steps is actually desirable from a security
standpoint but I think that the ability to run virt-install and take advantage
of qemu-bridge-helper is something that a non root user should be able to do.

pkgs: libvirt permissions


body:
Build Identifier:

qgit can be compiled with Qt5, see http://libre.tibirna.org/news/3

Having a Qt5 build will reduce the dependencies to deprecated Qt4.

Reproducible: Always

summary: Build qgit with Qt5


body:
--1468488517.c65FeEc1.29371
Date: Thu, 14 Jul 2016 09:28:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 988908
           Summary: apache2-mod_wsgi-python3 is missing
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: All
                OS: openSUSE 42.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Apache
          Assignee: bnc-team-apache-at-forge.provo.novell.com
          Reporter: vetter-at-physik.uni-wuerzburg.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

apache2-mod_wsgi-python3 is missing in 42.1.
It is a second spec file in the package apache2-mod_wsgi.

summary: apache2-mod_wsgi-python3 is missing


body:
--1468499879.56024f1.12054
Date: Thu, 14 Jul 2016 12:37:59 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

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

New release of mbedtl offers following fixes and improvements:
  * Security
    + Fix missing padding length check in
      mbedtls_rsa_rsaes_pkcs1_v15_decrypt required by PKCS1 v2.2
    + Fix a potential integer underflow to buffer overread in
      mbedtls_rsa_rsaes_oaep_decrypt. It is not triggerable
      remotely in SSL/TLS.
    + Fix potential integer overflow to buffer overflow in
      mbedtls_rsa_rsaes_pkcs1_v15_encrypt and
      mbedtls_rsa_rsaes_oaep_encrypt
  * Bugfix
    + Fix bug in mbedtls_mpi_add_mpi() that caused wrong results
      when the three arguments where the same (in-place doubling).
      Found and fixed by Janos Follath. #309
    + Fix issue in Makefile that prevented building using armar.
    + Fix issue that caused a hang up when generating RSA keys of
      odd bitlength
    + Fix bug in mbedtls_rsa_rsaes_pkcs1_v15_encrypt that made
      null pointer dereference possible.
    + Fix issue that caused a crash if invalid curves were passed
      to mbedtls_ssl_conf_curves. #373
    * Changes
      + On ARM platforms, when compiling with -O0 with GCC, Clang or
        armcc5, don't use the optimized assembly for bignum
        multiplication. This removes the need to pass
        -fomit-frame-pointer to avoid a build error with -O0.
      + Disabled SSLv3 in the default configuration.
      + Fix non-compliance server extension handling. Extensions for
        SSLv3 are now ignored, as required by RFC6101.

summary: mbedtls: Update to version 1.3.17


body:
Build Identifier:

I'm using "ecryptfs" with a private directory (/home/rickert/Private )

I last used this just before the kernel update (to kernel 4.1.27-24-default).
It was working fine.

I tried looking at my private directory a little while ago, and got a weird
message about wrong medium type (using "ls" at the command line).

I rebooted.  Still the same problem.

I then rebooted to the previous kernel, and my private directory is fine with
the previous kernel (4.1.26-21-default).  So this looks like a bug in the
4.1.27 kernel.

I will attach the output from:

journalctl -b -1 | grep ecryptfs

Actually, it will be a "typescript" file, showing similar output for several
boots (-1, -2, -3, -4 and the current boot)

Reproducible: Always

summary: The last kernel update broke "ecryptfs"


--1468769723.1b6aa020.13362
Date: Sun, 17 Jul 2016 15:35:23 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 989281
           Summary: shorewall need update to last bugfix of 4.6 series
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: bruno@ioda-net.ch
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Upstream has a 4.6.13.4 minor bugfix series


--1468774454.7E0bBbea1.19092
Date: Sun, 17 Jul 2016 16:54:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 989284
           Summary: KIWI images broken due to e2fsprogs update for U-Boot based boot, uses "64bit" feature
    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: stefan.bruens@rwth-aachen.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

e2fsprogs-1.43 adds the "64bit" feature for ext4 filesystems.

KIWI uses the default features from /etc/mke2fs.conf

U-Boot does not support ext4 with enabled 64bit feature. Thus this affects any
system using U-Boot which stores kernel and initrd on the root filesystem.
(e.g. rpi3 uses a seperate ext3 /boot partition, Pine64 uses the ext4 / root
filesystem)

The issue can be worked around by e.g.:
"tune2fs -O ^64bit /dev/sdc2; e2fsck -y /dev/sdc2; resize2fs -s /dev/sdc2"

assuming sdc2 is the root filesystem partition on the SD card.

Affected image: e.g.
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Pine64:/Downstream/images/


--1468835519.21F80.31005
Date: Mon, 18 Jul 2016 09:51:59 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 989341
           Summary: [AArch64] KDE broken as QML crashes on startup
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.2
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: X11 Applications
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Anytime I start anything using QML on AArch64, it crashes instantly in
/usr/lib64/libQt5Qml.so.5.
Sample backtrace from kwin_x11:

#0  0x0000ffffb54f20b0 in QV4::Object::defineReadonlyProperty(QV4::String*,
QV4::Value const&) () from /usr/lib64/libQt5Qml.so.5
#1  0x0000ffffb554365c in ?? () from /usr/lib64/libQt5Qml.so.5
#2  0x0000ffffb54b9ad4 in
QV4::ExecutionEngine::ExecutionEngine(QV4::EvalISelFactory*) () from
/usr/lib64/libQt5Qml.so.5
#3  0x0000ffffb55ef5b0 in QV8Engine::QV8Engine(QJSEngine*) () from
/usr/lib64/libQt5Qml.so.5
#4  0x0000ffffb544b600 in QJSEngine::QJSEngine(QJSEnginePrivate&, QObject*) ()
from /usr/lib64/libQt5Qml.so.5
#5  0x0000ffffb555ac44 in QQmlEngine::QQmlEngine(QObject*) () from
/usr/lib64/libQt5Qml.so.5
#6  0x0000ffffb7cddc20 in ?? () from /usr/lib64/libkwin.so.5
#7  0x0000ffffb7cddd14 in ?? () from /usr/lib64/libkwin.so.5
#8  0x0000ffffb7be17c4 in KWin::Workspace::init() () from
/usr/lib64/libkwin.so.5
#9  0x0000ffffb7be2220 in KWin::Workspace::Workspace(QString const&) () from
/usr/lib64/libkwin.so.5
#10 0x0000ffffb7c27454 in KWin::Application::createWorkspace() () from
/usr/lib64/libkwin.so.5
#11 0x0000ffffb7f9e8e0 in ?? () from /usr/lib64/libkdeinit5_kwin_x11.so
#12 0x0000ffffb6c90f78 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#13 0x0000ffffb7aaf65c in KSelectionOwner::Private::claimSucceeded() () from
/usr/lib64/libKF5WindowSystem.so.5
#14 0x0000ffffb7aafea4 in KSelectionOwner::filterEvent(void*) () from
/usr/lib64/libKF5WindowSystem.so.5
#15 0x0000ffffb6c605cc in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) ()
from /usr/lib64/libQt5Core.so.5
#16 0x0000ffffb101edb4 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /usr/lib64/libQt5XcbQpa.so.5
#17 0x0000ffffb101f990 in QXcbConnection::processXcbEvents() () from
/usr/lib64/libQt5XcbQpa.so.5
#18 0x0000ffffb6c91b28 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#19 0x0000ffffb7565284 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#20 0x0000ffffb756cae0 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#21 0x0000ffffb6c637b4 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#22 0x0000ffffb6c66058 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#23 0x0000ffffb6cb6c94 in
QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/libQt5Core.so.5
#24 0x0000ffffb1096dac in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#25 0x0000ffffb6c61564 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQt5Core.so.5
#26 0x0000ffffb6c69d10 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#27 0x0000ffffb7fa00fc in kdemain () from /usr/lib64/libkdeinit5_kwin_x11.so
#28 0x0000ffffb7e1e8a4 in __libc_start_main () from /lib64/libc.so.6
#29 0x0000000000400960 in _start ()

The same issue affects Qt 5.6.0, 5.6.1 and 5.7.0 and I could not find the same
issue anywhere else on the internet and Qt is supposedly used on many aarch64
platforms,
so I assume that this might be an openSUSE-only issue. The nullptr comes from a
function that returns 0 after some bit fiddling with pointers. Any idea what
causes this issue? Is it maybe related to the issue with firefox, which also
crashed in the JS engine?


body:
--1468877480.CaD4EcfB0.5375
Date: Mon, 18 Jul 2016 21:31:20 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 989462
           Summary: Virt-Manager Unable to Create VM
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: aarch64
                OS: openSUSE 42.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: alan-at-softiron.co.uk
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I've had some trouble creating VM's with virt-manager and have identified what
I think is the problem. I am able to work around it, but it requires editing
the VM xml description manually with "virsh edit".

The basic problem is that if you create a VM with virt-manager, it will not get
the firmware line correct. What I think it's trying to generate (because I
can't really verify it, because it fails) is:

 <os>
    <type arch='aarch64' machine='virt'>hvm</type>
    <loader readonly='yes'
type='pflash'>/usr/share/AAVMF/AAVMF_CODE.fd</loader>
    ...
    <boot dev='hd'/>
  </os>

Note the use of "pflash" as the type. Indeed this is what the libvirt
documentation says to do:
    https://libvirt.org/formatdomain.html#elementsOSBIOS
    "For instance, if the loader path points to an UEFI image, type should be
pflash."

However, if pflash is used here, starting the VM will fail with: "virt-manager
Initialization of device cfi.pflash01 failed: failed to read the initial flash
content"

If the type is changed to "rom" (manually), the VM boots up as expected.

Steps to reproduce:

# Install prerequisites:
zypper install virsh virt-install vm-install ca-certificates
libvirt-daemon-driver-qemu qemu qemu-tools

# Download the firmware Image:
wget
http://snapshots.linaro.org/components/kernel/leg-virt-tianocore-edk2-upstream/1127/QEMU-AARCH64/RELEASE_GCC49/QEMU_EFI.fd

# Install the firmware image and space for the variables:
mkdir /usr/share/AAVMF
cp QEMU_EFI.fd /usr/share/AAVMF/AAVMF_CODE.fd
dd if=/dev/zero of=/usr/share/AAVMF/AAVMF_VARS.fd bs=16M count=1

# Download the OS Image
wget
http://download.opensuse.org/ports/aarch64/distribution/leap/42.1/appliances/openSUSE-Leap42.1-ARM-JeOS-devel-efi.aarch64.raw.xz

# Convert the OS Image to qcow2 format for VM use:
unxz openSUSE-Leap42.1*.xz
qemu-img convert -f raw -O qcow2 openSUSE-Leap42.1*.raw leap.qcow2
qemu-img resize leap.qcow2 40G

# Inspect the qcow2 image (see 40G)
qemu-img info leap.qcow2

# Install qcow image:
cp leap.qcow2 /var/lib/libvirt/images/

# Create and start the VM with virt-manager GUI:
virt-manager
    File->New
        "Create new Virtual Machine" - Step 1 of 4
            Select "Import Existing Disk Image"
            Archetecture Options:
                aarch64
                virt
            Click "Forward"
        "Provide the existing Storage Path:"
            Click "Browse"
            Select leap.qcow2
            Click "Select Volume"
            Choose OS Type:
                "Linux"
                "SUSE Enterprise 12 SP1"
            Click "Forward"
        "Choose Memory and CPU settings"
            RAM: 2048 (less than this will fail to load initrd!)
            CPU: 1
            Click "Forward"
        "Ready to begin the Installation"
            Enter "sles12" as the name
            Click Finish
        "Begin Installation" Window
            click "Begin Installation"
            This will fail to create a VM, complaining about inability to find
pflash, as described above.
            Click OK which will take you back to the "Begin Installation"
Window.
            Click "Overview" on the left
            Change "Firmware" to "none"
            Click "Apply"
            Click "Begin Installation"
        This will Create and start a VM. It will not boot.

    To fix this, from the VM window Select:
        Virtual Machine -> Shutdown -> Force Off
From the Shell:
    virsh edit sles12   # sles12 is the name you entered above.
    Under the <os> tag, add the lines:
        <loader readonly='yes'
type='rom'>/usr/share/AAVMF/AAVMF_CODE.fd</loader>
        <nvram
template='/usr/share/AAVMF/AAVMF_VARS.fd'>/tmp/sles12VARS.fd</nvram>
    Close the editor (esc :wq)
From virt-manager:
    Select the VM
    Press "Open"
    Virtual Machine -> Run
    Observe the VM boot SUSE and run.

Thanks for having a look at this and sorry about the verbosity, but I think
it's all necessary to describe and characterize the problem.

Alan.

summary: Virt-Manager Unable to Create VM


--1468911023.F81c0.7358
Date: Tue, 19 Jul 2016 06:50:23 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 989486
           Summary: Publishing:TeXLive: Bug (BibLatex with Biber does not work)
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: werner-at-suse.com
          Reporter: saloution-at-googlemail.com
        QA Contact: opensuse-communityscreening-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

Created attachment 684658
  --> http://bugzilla.opensuse.org/attachment.cgi?id=684658&action=edit
minimal example that does not work for me (no bibliography)

Hello,

My opensuse leap system installed few days ago the new texlive 2016 packages.
Since then, I cannot generate a bibliography with my texfiles anymore.

From the biber log:

> $ biber paper
> INFO - This is Biber 2.4
> INFO - Logfile is 'paper.blg'
> INFO - Reading 'paper.bcf'
> WARN - Warning: Found biblatex control file version 3.1, expected version
> 3.0

Latex reports that the bibliography is empty.

I guess that the issue is due to a version mismatch between biber and
biblatex. There is a similar discussion in the Debian bugzilla:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825163

Attached to this mail you find a minimal example I found in the internet that
has the same effect (no bibliography).

All the best!


--1469009435.16C7a0.26354
Date: Wed, 20 Jul 2016 10:10:35 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 989713
           Summary: built-in wlan on raspberry pi3: no drivers
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: dannvasile-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 684856
  --> http://bugzilla.opensuse.org/attachment.cgi?id=684856&action=edit
Dmesg output

The built-in wlan on the raspberry pi 3 isn't recognized by the OS.


body:
--1469027993.AAA15.12604
Date: Wed, 20 Jul 2016 15:19:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 989799
           Summary: document /var/cache subvolume
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Release Notes
          Assignee: ke-at-suse.com
          Reporter: lnussel-at-suse.com
        QA Contact: coolo-at-suse.com
                CC: dimstar-at-opensuse.org, jsrain-at-suse.com, mlin-at-suse.com
          Found By: ---
           Blocker: ---

/var/cache needs to be turned into a subvolume. that needs to be documented in
the release notes for 13.2 and 42.1 and mentioned as update instructions for
42.2 and TW.

see Fate#320834

summary: document /var/cache subvolume


body:
--1469107271.0F67e0.1174
Date: Thu, 21 Jul 2016 13:21:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 989998
           Summary: Tracker Bug nextcloud upstream release
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: openSUSE 42.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: asemen-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Tracker Bug nextcloud upstream release to version 9.0.53
https://nextcloud.com/

summary: Tracker Bug nextcloud upstream release


body:
--1469192099.F50CC80.21393
Date: Fri, 22 Jul 2016 12:54:59 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 990257
           Summary: KDE wallpaper wrong aspect ratio
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On Alpha3 on a wide screen the wallpaper looks it it was scaled from 4:3
without keeping the aspect ratio, so the light bulb looks "fat".

summary: KDE wallpaper wrong aspect ratio