body:
--1431959089.482BfDe63.7349
Date: Mon, 18 May 2015 14:24:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931288
           Summary: wickedd-nanny[1234]: segfault at 38
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: wicked-maintainers-at-suse.de
          Reporter: mpluskal-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 634608
  --> http://bugzilla.opensuse.org/attachment.cgi?id=634608&action=edit
full backtrace

When using wicked-nanny, and switchin from bridged to non bridged netw
configuration (with one device):
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
group default qlen 1000
    link/ether 00:24:8c:23:72:26 brd ff:ff:ff:ff:ff:ff
    inet 10.100.12.94/18 brd 10.100.63.255 scope global enp3s0
       valid_lft forever preferred_lft forever
    inet6 fd79:5506:3d7a:1:224:8cff:fe23:7226/64 scope global mngtmpaddr
dynamic
       valid_lft 86140sec preferred_lft 14140sec
    inet6 fe80::224:8cff:fe23:7226/64 scope link
       valid_lft forever preferred_lft forever

following occurs:
May 18 16:08:20 medusa kernel: wickedd-nanny[1234]: segfault at 38 ip
00007f42dcd110c1 sp 00007fffacdb9b60 error 4 in
libwicked-0.so.6.18.0[7f42dccad000+f2000]
(gdb) bt
#0  0x00007f42dcd110c1 in ni_fsm_policy_transform_document (node=0x8c4e40,
policies=policies@entry=0x7fffacdb9ba8, count=count@entry=1) at
fsm-policy.c:551
#1  0x00000000004077ef in ni_nanny_create_policy
(policy_object=policy_object@entry=0x7fffacdb9c00, mgr=mgr@entry=0x8bc5d0,
    doc_string=0x8c2e30 "<policy name=\"policy__enp3s0\"
origin=\"compat:/etc/sysconfig/network/ifcfg-enp3s0\"
uuid=\"54f25955-5122-0a00-7909-000002000000\">\n  <match>\n
<link-type>ethernet</link-type>\n    <device>enp3s0</device>"...,
schedule=schedule@entry=0 '\000') at nanny.c:386
#2  0x0000000000407aef in ni_objectmodel_nanny_create_policy (object=0x8bf9d0,
method=0x60cb38 <ni_objectmodel_nanny_methods+56>, argc=1, argv=0x7fffacdb9ca0,
reply=0x8c0330, error=0x7fffacdb9c80) at nanny.c:901
#3  0x00007f42dcd01638 in __ni_dbus_object_message (conn=<optimized out>,
call=call@entry=0x8c0c30, user_data=user_data@entry=0x8bf9d0) at
dbus-server.c:672
#4  0x00007f42dca83d56 in _dbus_object_tree_dispatch_and_unlock (tree=0x8bf750,
message=message@entry=0x8c0c30, found_object=found_object@entry=0x7fffacdba0d4)
at dbus-object-tree.c:1018
#5  0x00007f42dca76681 in dbus_connection_dispatch (connection=0x8c0660) at
dbus-connection.c:4718
#6  0x00007f42dccfbd39 in __ni_dbus_connection_dispatch (connection=0x8bf810,
connection=0x8bf810) at dbus-connection.c:896
#7  __ni_dbus_watch_handle (flags=1, sock=0x8c2140, func=0x7f42dcd67110
<__FUNCTION__.9091> "__ni_dbus_watch_recv") at dbus-connection.c:744
#8  __ni_dbus_watch_recv (sock=0x8c2140) at dbus-connection.c:773
#9  0x00007f42dcd328a4 in ni_socket_array_wait
(array=array@entry=0x7f42dcfb6460 <__ni_sockets>, timeout=<optimized out>) at
socket.c:197
#10 0x00007f42dcd32b9f in ni_socket_wait (timeout=<optimized out>) at
socket.c:243
#11 0x00000000004054f9 in babysit () at main.c:302
#12 main (argc=<optimized out>, argv=<optimized out>) at main.c:190

# cat /etc/sysconfig/network/ifcfg-enp3s0
BOOTPROTO='dhcp+autoip'
STARTMODE='auto'
IPADDR=''
NETMASK=''
PREFIXLEN=''
BROADCAST=''
ETHTOOL_OPTIONS=''
MTU=''
NAME=''
NETWORK=''
REMOTE_IPADDR=''

summary: wickedd-nanny[1234]: segfault at 38


--1431960573.a3d4AA1810.10910
Date: Mon, 18 May 2015 14:49:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931296
           Summary: [plasma5 packaging] cannot unlock locked screen (kcheckpass failure)
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE4 Workspace
          Assignee: kde-maintainers-at-suse.de
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: hrvoje.senjan-at-gmail.com
          Found By: ---
           Blocker: ---

With plasma5 update I cannot unlock the lock screen using my password. This is
perhaps:
https://bugs.kde.org/show_bug.cgi?id=314661

If I do
# chmod 4755 /usr/lib/kde4/libexec/kcheckpass
it works again.

kdebase4-workspace.spec used to have:
%attr(-, root, shadow) %{_kde4_libexecdir}/kcheckpass

plasma5-workspace.spec has only:
%{_kf5_libdir}/libexec/kcheckpass

So running it says:
$ /usr/lib64/libexec/kcheckpass
Password:
Information: Permissions on the password database may be too restrictive.

Hence lock screen cannot check the password.


body:
--1431961389.1FE81e0.14067
Date: Mon, 18 May 2015 15:03:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931300
           Summary: many black lines on the screen
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: CONFIRMED
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: jslaby-at-suse.com
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

This is about:
https://bugs.freedesktop.org/show_bug.cgi?id=80948

This fixes it (-next):
commit 34c83ca0d0c690d76b78897204e5af61ef13ce7d
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Apr 27 13:41:15 2015 +0100

    drm/i915: Ensure cache flushes prior to doing CS flips

summary: many black lines on the screen


body:
--1431963189.0f1cf3BE0.18981
Date: Mon, 18 May 2015 15:33:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931309
           Summary: Occasional Xorg segmentation fault
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: xorg-maintainer-bugs-at-forge.provo.novell.com
          Reporter: mmarinchenko-at-yahoo.com
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

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

See attached Xorg log.

summary: Occasional Xorg segmentation fault


--1432017279.334e9.27595
Date: Tue, 19 May 2015 06:34:39 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931401
           Summary: Request to add upstream kdesvn patch to openSUSE 13.2
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE4 Applications
          Assignee: kde-maintainers-at-suse.de
          Reporter: mmarinchenko-at-yahoo.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Upstream bug reports (fixed):

https://bugs.kde.org/show_bug.cgi?id=325074
https://bugs.kde.org/show_bug.cgi?id=330624


--1432033171.83BEDA43.6224
Date: Tue, 19 May 2015 10:59:31 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931461
           Summary: Virtualbox doesn't work on Haswell or Broadwell - problem with smap
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: noga.dany-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Problem is descripted on https://www.virtualbox.org/ticket/13820 with provided
patch


--1432121134.e70b1.10529
Date: Wed, 20 May 2015 11:25:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931659
           Summary: VUL-0: CVE-2015-1251: chromium-browser: Use-after-free in Speech.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

ZDI-15-236:

This vulnerability allows remote attackers to execute arbitrary code on
vulnerable installations of Google Chrome. User interaction is required to
exploit this vulnerability in that the target must visit a malicious page or
open a malicious file.

The specific flaw exists within SpeechRecognitionClient.   By manipulating a
document's elements, an attacker can force a dangling pointer to be reused
after
it has been freed. An attacker can leverage this vulnerability to execute code
under the context of the current process.

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223258
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1251
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1251
http://www.zerodayinitiative.com/advisories/ZDI-15-236/


--1432121258.8FBcA4D1.10824
Date: Wed, 20 May 2015 11:27:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931660
           Summary: VUL-0: CVE-2015-1265: chromium: Various fixes from internal audits, fuzzing and other initiatives.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223273 / CVE-2015-1265

An unspecified flaws were found in the unspecified component of the Chromium
browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=489518

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223273
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1265
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1265


--1432121324.42e4b1.10755
Date: Wed, 20 May 2015 11:28:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931661
           Summary: VUL-0: CVE-2015-1264 chromium: Cross-site scripting in bookmarks.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223272 / CVE-2015-1264

An unspecified cross-site scripting flaw was found in the bookmarks.  component
of the Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=481015

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223272
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1264
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1264


--1432121391.Ae7A1.11592
Date: Wed, 20 May 2015 11:29:51 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931663
           Summary: VUL-0: CVE-2015-1263: chromium: insecure download of spellcheck dictionary in unspecified component
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223271 / CVE-2015-1263

An unspecified insecure download of spellcheck dictionary flaw was found in the
unspecified component of the Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=479162

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223271
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1263
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1263


--1432121458.5E07bb1.11527
Date: Wed, 20 May 2015 11:30:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931664
           Summary: VUL-0: CVE-2015-1256: chromium: Use-after-free in SVG.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223263 / CVE-2015-1256

An unspecified use-after-free flaw was found in the SVG.  component of the
Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=478549

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223263
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1256
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1256


--1432121522.fa51B1.11933
Date: Wed, 20 May 2015 11:32:02 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931665
           Summary: VUL-0: CVE-2015-1257 chromium-browser: Container-overflow in SVG.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223264 / CVE-2015-1257

An unspecified container-overflow flaw was found in the SVG.  component of the
Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=468519

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223264
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1257
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1257


--1432121591.0Dd5eA7.11311
Date: Wed, 20 May 2015 11:33:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931666
           Summary: VUL-0: CVE-2015-1258: chromium: Negative-size parameter in Libvpx.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223266 / CVE-2015-1258

An unspecified negative-size parameter flaw was found in the Libvpx.  component
of the Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=450939

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223266
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1258
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1258


--1432121641.Eb0C31.11596
Date: Wed, 20 May 2015 11:34:01 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931667
           Summary: VUL-0: CVE-2015-1259: chromium: Uninitialized value in PDFium.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223267 / CVE-2015-1259

An unspecified uninitialized value flaw was found in the PDFium.  component of
the Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=468167

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223267
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1259
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1259


--1432121702.a4051.13170
Date: Wed, 20 May 2015 11:35:02 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931668
           Summary: VUL-0: CVE-2015-1260: chromium: Use-after-free in WebRTC.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223268 / CVE-2015-1260

An unspecified use-after-free flaw was found in the WebRTC.  component of the
Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=474370

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223268
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1260
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1260


--1432121802.3a0Aa1.13134
Date: Wed, 20 May 2015 11:36:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931669
           Summary: VUL-0: CVE-2015-1254: chromium: Cross-origin bypass in Editing.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223261 / CVE-2015-1254

An unspecified cross-origin bypass flaw was found in the Editing.  component of
the Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=444927

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223261
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1254
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1254


--1432121849.3BEb2A7.13134
Date: Wed, 20 May 2015 11:37:29 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931670
           Summary: VUL-0: CVE-2015-1253: chromium: Cross-origin bypass in DOM.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223260 / CVE-2015-1253

An unspecified cross-origin bypass flaw was found in the DOM.  component of the
Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=464552

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223260
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1253
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1253


--1432121915.aff21.13502
Date: Wed, 20 May 2015 11:38:35 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931671
           Summary: VUL-0: CVE-2015-1252: chromium: Sandbox escape in Chrome.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223259 / CVE-2015-1252

An unspecified sandbox escape flaw was found in the Chrome.  component of the
Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=474029

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223259
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1252
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1252


--1432121964.deBDD361.13611
Date: Wed, 20 May 2015 11:39:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931672
           Summary: VUL-0: CVE-2015-1262: chromium: Uninitialized value in Blink.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223270 / CVE-2015-1262

An unspecified uninitialized value flaw was found in the Blink.  component of
the Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=476647

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223270
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1262
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1262


--1432122025.c08cf301.13958
Date: Wed, 20 May 2015 11:40:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931673
           Summary: VUL-0: CVE-2015-1261: chromium: URL bar spoofing in unspecified component
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223269 / CVE-2015-1261

An unspecified url bar spoofing flaw was found in the unspecified component of
the Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=466351

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223269
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1261
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1261


--1432122113.DbC341.13959
Date: Wed, 20 May 2015 11:41:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931674
           Summary: VUL-0: CVE-2015-1255: chromium: Use-after-free in WebAudio.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tittiatcoke-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1223262 / CVE-2015-1255

An unspecified use-after-free flaw was found in the WebAudio.  component of the
Chromium browser.

Upstream bug: https://code.google.com/p/chromium/issues/detail?id=473253

External References:

http://googlechromereleases.blogspot.com/2015/05/stable-channel-update_19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1223262
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1255
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1255


--1432198015.1EAeAd80.2631
Date: Thu, 21 May 2015 08:46:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931792
           Summary: Apparmor is missing profiles and enforcement of it
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: clausreheis-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

when doing a "apparmor_status" on current Tumbleweed, the output is:

apparmor module is loaded.
0 profiles are loaded.
0 profiles are in enforce mode.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.


--1432241727.1cb20.20923
Date: Thu, 21 May 2015 20:55:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931917
           Summary: xf86-video-intel driver needs an update for Kernel 4.0
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: xorg-maintainer-bugs-at-forge.provo.novell.com
          Reporter: bjoernv-at-arcor.de
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

Created attachment 635097
  --> http://bugzilla.opensuse.org/attachment.cgi?id=635097&action=edit
Xorg crashes with segmentation fault with driver package
xf86-video-intel-2.99.917-145.8

After updating the Kernel to 4.0 (tested with Kernel 4.0.4-2.g4f5e0d5-desktop
from Kernel_stable repository), X does not start anymore. /usr/bin/Xorg crashes
with "Segmentation fault at address 0x0" (file /var/log/Xorg.0.log is
attached).

My setup:
- CPU Intel Core i5 4200U
- Kernel 4.0.4-2.g4f5e0d5-desktop
- Xorg packages from X11_XOrg repository:
  - xf86-video-intel-2.99.917-145.8
  - X.Org X Server 1.17.1

After updating the xf86-video-intel driver with intel sources from GIT (see
http://www.x.org/wiki/IntelGraphicsDriver/, tested with GIT snapshot from May
19 12:14:24 2015 +0100) my X server works again.


--1432284325.ac500b0.15483
Date: Fri, 22 May 2015 08:45:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931978
           Summary: VUL-0: CVE-2014-9721: zeromq: protocol downgrade attack on sockets using the ZMTP v3 protocol
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tchvatal-at-suse.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1221666
-------------------------------------
It was discovered that zeromq, a lightweight messaging kernel, is
susceptible to a protocol downgrade attack on sockets using the ZMTP v3
protocol. This could allow remote attackers to bypass ZMTP v3 security
mechanisms by sending ZMTP v2 or earlier headers.

CVE request: http://openwall.com/lists/oss-security/2015/05/07/8
Upstream bug report: https://github.com/zeromq/libzmq/issues/1273
Upstream fix:
https://github.com/zeromq/zeromq4-x/commit/b6e3e0f601e2c1ec1f3aac880ed6a3fe63043e51
-------------------------------------

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1221666
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-9721
http://seclists.org/oss-sec/2015/q2/515
http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-9721.html


--1432286160.CbA48f504.21054
Date: Fri, 22 May 2015 09:16:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 931987
           Summary: VUL-0: CVE-2013-7441: nbd: NBD server terminates on SIGPIPE during negotiation
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: ms-at-suse.com
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

rh#1224074 / CVE-2013-7441
--------------------------------------------
A denial of service flaw was found in nbd:

"The listener/root server process terminates on SIGPIPE during negotiation.
This is hardly the desired behavior, since any malfunctioning client can
brought the listener server down by closing the socket unexpectedly."

Additional information:

http://sourceforge.net/p/nbd/mailman/message/30410146/

Upstream patch:

https://github.com/yoe/nbd/commit/741495cb08503fd32a9d22648e63b64390c601f4
--------------------------------------------

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1224074
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7441
http://seclists.org/oss-sec/2015/q2/516
http://people.canonical.com/~ubuntu-security/cve/2013/CVE-2013-7441.html


--1432406248.58FffF0E4.25966
Date: Sat, 23 May 2015 18:37:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 932142
           Summary: zypper si PACKAGENAME - missing .changes file
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: All
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: libzypp
          Assignee: zypp-maintainers-at-forge.provo.novell.com
          Reporter: bwiedemann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: mls-at-suse.com
          Found By: Development
           Blocker: ---

zypper si PACKAGENAME does not install the .changes file

some relevant code seems to be in
libzypp/zypp/target/TargetImpl.cc TargetImpl::installSrcPackage

The changes files can be produced with rpm -qp --changelog PACKAGENAME.src.rpm
but zypper auto-deleted the src.rpm

Steps To Reproduce:
zypper si MozillaFirefox
rpmbuild -bb /usr/src/packages/SPECS/MozillaFirefox.spec

Actual Results:
build fails, because /usr/src/packages/SOURCES/MozillaFirefox.changes is
missing

Expected Results:
/usr/src/packages/SOURCES/MozillaFirefox.changes should be created


--1432491047.2d5daA0.15663
Date: Sun, 24 May 2015 18:10:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 932158
           Summary: KDE Plasma 5.3 localization (Opensuse Tumbleweed)
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: SUSE Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: medipas-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After the upgrade to KDE Plasma 5.3 on Tumbleweed last week, KDE desktop 5.3 is
shown in English, although set to a different language in 'configure desktop',
'configure KDE 4 applications' and in Yast's 'Language'. The panel, the
application launcher, application menu, witgets, etc. are in English. On the
other hand, Dolphin, Yast, Firefox, Libreoffice and other applications show in
the correct locale.
I have checked if the localization exists for my locale, I mean, that Plasma 5
is translated to it and it is. Kaos Linux, for instance, uses the same Plasma
5.3 and the same version of language packs installed on Tumbleweed (kde-l10n
15.04.1-1.1) and the panel and widgets are ok.
I have seen this with another locale, such as Spanish.
Could it be a configuration issue?
Thanks for your attention.


body:
--1432537847.8bF8eA0.4595
Date: Mon, 25 May 2015 07:10:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 932186
           Summary: yast2-fonts: yast/wfm.rb:197
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: pgajdos-at-suse.com
          Reporter: mpluskal-at-suse.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

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

When entering Rendering details/Embedded bitmaps/Select, following occurs:
2015-05-25 09:06:10 <1> daredevil(8199) [ui] YPushButton.cc(setFunctionKey):202
Guessing button role YCancelButton for YPushButton "Cancel" at 0x7ff304324740
from function key F9
2015-05-25 09:06:12 <3> daredevil(8199) [Ruby] yast/wfm.rb:197 Client call
failed with 'wrong number of arguments (0 for 1)' and backtrace
["/usr/share/YaST2/lib/fonts/fonts-dialog.rb:250:in
`initialize_embeddedbitmaps_widget'", "
/usr/share/YaST2/lib/fonts/fonts-dialog.rb:292:in
`handle_embeddedbitmaps_widget'",
"/usr/lib64/ruby/vendor_ruby/2.2.0/yast/fun_ref.rb:33:in `call'",
"/usr/lib64/ruby/vendor_ruby/2.2.0/yast/fun_ref.rb:33:in `call'",
"/usr/share/Ya
ST2/modules/CWM.rb:364:in `block in handleWidgets'",
"/usr/lib64/ruby/vendor_ruby/2.2.0/yast/builtins.rb:88:in `call'",
"/usr/lib64/ruby/vendor_ruby/2.2.0/yast/builtins.rb:88:in `block in foreach'",
"/usr/lib64/ruby/vendor_ruby/2.
2.0/yast/builtins.rb:87:in `each'",
"/usr/lib64/ruby/vendor_ruby/2.2.0/yast/builtins.rb:87:in `foreach'",
"/usr/share/YaST2/modules/CWM.rb:352:in `handleWidgets'",
"/usr/share/YaST2/modules/CWMTab.rb:125:in `TabHandle'", "/usr/sha
re/YaST2/modules/CWMTab.rb:251:in `Handle'",
"/usr/share/YaST2/modules/CWMTab.rb:316:in `HandleWrapper'",
"/usr/lib64/ruby/vendor_ruby/2.2.0/yast/fun_ref.rb:33:in `call'",
"/usr/lib64/ruby/vendor_ruby/2.2.0/yast/fun_ref.rb:33:in `
call'", "/usr/share/YaST2/modules/CWM.rb:364:in `block in handleWidgets'",
"/usr/lib64/ruby/vendor_ruby/2.2.0/yast/builtins.rb:88:in `call'",
"/usr/lib64/ruby/vendor_ruby/2.2.0/yast/builtins.rb:88:in `block in foreach'",
"/usr/lib
64/ruby/vendor_ruby/2.2.0/yast/builtins.rb:87:in `each'",
"/usr/lib64/ruby/vendor_ruby/2.2.0/yast/builtins.rb:87:in `foreach'",
"/usr/share/YaST2/modules/CWM.rb:352:in `handleWidgets'",
"/usr/share/YaST2/modules/CWM.rb:803:in `Run
'", "/usr/share/YaST2/modules/CWM.rb:938:in `ShowAndRun'",
"/usr/share/YaST2/lib/fonts/fonts-dialog.rb:951:in `run_dialog'",
"/usr/share/YaST2/lib/fonts/fonts-dialog.rb:56:in `run'",
"/usr/share/YaST2/lib/fonts/fonts-dialog.rb:50:
in `run'", "/usr/share/YaST2/clients/fonts.rb:3:in `<top (required)>'",
"/usr/lib64/ruby/vendor_ruby/2.2.0/yast/wfm.rb:184:in `eval'",
"/usr/lib64/ruby/vendor_ruby/2.2.0/yast/wfm.rb:184:in `run_client'"]
2015-05-25 09:06:12 <3> daredevil(8199) [Ruby] yast/wfm.rb:202 Internal error.
Please report a bug report with logs.
Details: wrong number of arguments (0 for 1)
Caller:  /usr/share/YaST2/lib/fonts/fonts-dialog.rb:250:in
`initialize_embeddedbitmaps_widget'
2015-05-25 09:06:12 <1> daredevil(8199) [ui] YPushButton.cc(setFunctionKey):202
Guessing button role YOKButton for YPushButton "OK" at 0x7ff30432ce70 from
function key F10
2015-05-25 09:09:23 <2> daredevil(8199) [qt-ui] YQUI.cc(qMessageHandler):725
<libqt-warning> QObject::killTimer: Timers cannot be stopped from another
thread
2015-05-25 09:09:23 <2> daredevil(8199) [qt-ui] YQUI.cc(qMessageHandler):725
<libqt-warning> QObject::~QObject: Timers cannot be stopped from another thread
2015-05-25 09:09:23 <3> daredevil(8199) [ui] YUI.cc(~YUI):94 1 open dialogs
left over

summary: yast2-fonts: yast/wfm.rb:197


--1432575255.5FFc66.20780
Date: Mon, 25 May 2015 17:34:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 932229
           Summary: Update webkitgtk to stable release 2.4.9 (from 2.4.8)
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: badshah400-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Webkitgtk has a new upstream stable release: 2.4.9. openSUSE 13.2 will be at
version 2.4.8 once
https://build.opensuse.org/project/show/openSUSE:Maintenance:3782
is released. The changes are as follows (from GNOME:Factory/webkitgtk):

- Update to version 2.4.9:
  + Check TLS errors as soon as they are set in the SoupMessage to
    prevent any data from being sent to the server in case of
    invalid certificate.
  + Clear the GObject DOM bindings internal cache when frames are
    destroyed or web view contents are updated.
  + Add HighDPI support for non-accelerated compositing contents.
  + Fix some transfer annotations used in GObject DOM bindings.
  + Use latin1 instead of UTF-8 for HTTP header values.
  + Fix synchronous loads when maximum connection limits are
    reached.
  + Fix a crash ScrollView::contentsToWindow() when GtkPluginWidget
    doesn't have a parent.
  + Fix a memory leak in webkit_web_policy_decision_new.
  + Fix g_closure_unref runtime warning.
  + Fix a crash due to empty drag image during drag and drop.
  + Fix rendering of scrollbars with GTK+ >= 3.16.
  + Fix the build on mingw32/msys.
  + Fix the build with WebKit2 disabled.
  + Fix the build with accelerated compositing disabled.
  + Fix clang version check in configure.
  + Fix the build with recent versions of GLib that have
    GMutexLocker.
  + Fix the build for Linux/MIPS64EL.
- Drop webkitgtk-hidpi.patch,
  webkitgtk-compile-when-WK2-disabled.patch,
  webkitgtk-WTF-GMutexLocker.patch and webkitgtk-gcc5-fixes.patch:
  Fixed upstream.
- Rebase webkitgtk-aarch64.patch.


body:
--1432601707.ff3aE46.13557
Date: Tue, 26 May 2015 00:55:07 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 932230
           Summary: Update gnome-commander to version 1.4.6
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: badshah400-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The current version in openSUSE:13.2 is 1.4.3; since then there have been three
bug fix releases upstream taking the current version to 1.4.6. Suggesting this
for a maintenance release:

-------------------------------------------------------------------
Wed May 20 18:05:09 UTC 2015 - dimstar-at-opensuse.org

- Update to version 1.4.6:
  + Bugs fixed: bgo#653573, bgo#742752, bgo#746003, bgo#747771,
    bgo#748869.
  + Updated translations.
- Drop gnome-commander-appdata-translation.patch: fixed upstream.
- Remove libtool BuildRequires and call to autoreconf, as we no
  longer carry any patches.

-------------------------------------------------------------------
Mon Apr 13 10:10:39 UTC 2015 - dimstar-at-opensuse.org

- Add gnome-commander-appdata-translation.patch: Do not handle
  appdata.xml.in as a config file, but let INTLTOOL_XML_RULE handle
  it.
- Add libtool BuildRequires and call to autoreconf, as above patch
  touches the build system.

-------------------------------------------------------------------
Sun Jan 25 23:29:33 UTC 2015 - zaitor-at-opensuse.org

- Update to version 1.4.5:
  + Fixed appdata missing in POT (bgo#741316).
  + Fixed Option --start-right-dir crashes gnome-commander
    (bgo#742716).
  + Removed python-2.6 support from gentoo ebuild.
  + Updated translations.

-------------------------------------------------------------------
Fri Nov 14 12:57:25 UTC 2014 - zaitor-at-opensuse.org

- Update to version 1.4.4:
  + Migrated from gnome_execute_shell to g_spawn_async
    (bgo#571495).
  + Support for user's terminal different from gnome-terminal
    (bgo#737088).
  + Updated translations.

summary: Update gnome-commander to version 1.4.6


--1432644771.18F31.9260
Date: Tue, 26 May 2015 12:52:51 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 932319
           Summary: OpenSuSE Tumbleweed Network Install: X-Server can't start with "Standard" screen resolution
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: SUSE Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Installation
          Assignee: yast2-maintainers-at-suse.de
          Reporter: Jens_Westemeier-at-web.de
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

Installing Tumbleweed (x86_64, 20150524) network based within VirtualBox.
X-Server can't start, I end in the text console based Yast environment.
Changing screen resolution at startup with "F3" from "Standard" to "1280x1024"
gets the X-Server starting and I can enjoy the graphical Yast.
So something is wrong with the "Standard" screen resolution.


--1432724100.a0aA0.24961
Date: Wed, 27 May 2015 10:55:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 932456
           Summary: "sysconf_addword NTPD_RUN_CHROOTED yes" places a space before "yes"
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Hardware: Other
                OS: openSUSE 13.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: stefan.schaefer-at-fsproductions.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

If I try to change the NTPD_RUN_CHROOTED from no to yes with sysconf_addword,
it places a space before "yes"

To reproduce do:

sysconf_addword -r /etc/sysconfig/ntp NTPD_RUN_CHROOTED no

and

sysconf_addword /etc/sysconfig/ntp NTPD_RUN_CHROOTED yes

This results in:

NTPD_RUN_CHROOTED=" yes"

instead of:

NTPD_RUN_CHROOTED="yes"

With the space-sign, ntpd didn't run chrotted after restart.

Regards

Stefan


--1432948166.F8050.7774
Date: Sat, 30 May 2015 01:09:26 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 932950
           Summary: w truncates usernames and lies about available commands
    Classification: openSUSE
           Product: openSUSE 12.3
           Version: Final
          Hardware: Other
                OS: openSUSE 12.3
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: eimacdude-at-aol.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Typed:
w -n
or
w --no-truncat

Expected output: non-truncated listing, including usernames NOT truncated to 8
characters

Actual output:

Usage:
 w [options]

Options:
 -h, --no-header     do not print header
 -u, --no-current    ignore current process username
 -s, --short         short format
 -n, --no-truncat    non truncated listing (large)
 -f, --from          show remote hostname field
 -o, --old-style     old style output
 -i, --ip-addr       display IP address instead of hostname (if possible)

     --help     display this help and exit
 -V, --version  output version information and exit

Note the line in that: "-n, --no-truncat    non truncated listing (large)"
So it's explicitly saying to use a command that doesn't work. Is this someone's
idea of a joke?
Because I feel more like crying than laughing, when I can't get non-truncated
usernames of graphically-logged in users with w -snf | grep :0 | awk '{print
$1}'


body:
Build Identifier:

The Windows app in question is IBI Trade Plus, which can be downloaded from
http://tradeone.co.il/downloads/ibi/ibitradeplus.exe. It is a .NET 3.5sp1 app;
wine-mono is sufficient to satisfy the installer.

The app installs without problems, but when you attempt to run it using
openSUSE's packaged version of wine-mono-4.5.6.msi, it fails with
"err:mscoree:load_mono Could not load Mono into this process" in the terminal.
With wine-mono-4.5.6.msi downloaded directly from Sourceforge, the login screen
appears as expected.

Reproducible: Always

Steps to Reproduce:
1. Install Wine and wine-mono from
http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_13.1/.
2. Download the app from http://tradeone.co.il/downloads/ibi/ibitradeplus.exe
and install it in a clean 32 bit wineprefix.
3. Try to run it.
Actual Results:
The app does not start; the last line in the terminal is "err:mscoree:load_mono
Could not load Mono into this process."

Expected Results:
The login screen should appear. It does appear when wine-mono-4.5.6.msi
downloaded from Sourceforge is used instead of openSUSE's packaged version.

According to Dolphin, the sizes of the two files are very different:

openSUSE's packaged wine-mono-4.5.6.msi: 40.5 MiB
Sourceforge's wine-mono-4.5.6.msi: 51.2 MiB

summary: App running in Wine fails to start with openSUSE's wine-mono package but works with wine-mono downloaded from Sourceforge


body:
--1433162008.21340.1196
Date: Mon, 1 Jun 2015 12:33:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 933072
           Summary: sensors-detect broke laptop display
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
               URL: http://www.lm-sensors.org/ticket/2392
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: jdelvare-at-suse.com
          Reporter: jdelvare-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

From upstream ticket 2392:

We had a report of sensors-detect breaking the display of a Lenovo g50-80
laptop:

 http://lists.lm-sensors.org/pipermail/lm-sensors/2015-May/043905.html

There is an I2C chip at address 0x4f on the DPDDC-A bus which reacts weirdly to
SMBus Read Byte transactions. Most likely it interprets them as writes,
treating the register address as a value.

Fixed by:
sensors-detect: Detect graphics card in all cases
http://www.lm-sensors.org/changeset/6282

and:
sensors-detect: Skip addresses 0x37 and 0x4f on DDC channels
http://www.lm-sensors.org/changeset/6283

This is somewhat similar to bug #838619, but requires an additional fix.

summary: sensors-detect broke laptop display


--1433168726.1ba74E60.14723
Date: Mon, 1 Jun 2015 14:25:26 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 933092
           Summary: systemd-networkd.service does not alias network.service
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: pwieczorkiewicz-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The systemd-networkd.service file must contain an alias to network.service.
This is the way wicked and NetworkManager work too. Otherwise it is unknown
which service handles the network.

Please add Alias=network.service in the [Install] section.


--1433184701.f2D5aAE0.6881
Date: Mon, 1 Jun 2015 18:51:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 933132
           Summary: Starting a guest from qcow2 with snapshots aborts()
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KVM
          Assignee: kvm-bugs-at-forge.provo.novell.com
          Reporter: dmueller-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

when starting a guest with -hda disk.qcow2, and disk.qcow2 has a snapshot, the
machine boot runs into an abort:

#0  0x00007ffff0ae0660 in abort () at /lib64/libc.so.6
#1  0x000055555592e008 in  ()
#2  0x000055555592ab05 in  ()
#3  0x000055555592b8fe in qcow2_alloc_cluster_offset ()


--1433407662.AD23eEC0.19900
Date: Thu, 4 Jun 2015 08:47:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 933588
           Summary: Heap-based buffer-overflow in tidy/libtidy
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
               URL: https://github.com/htacg/tidy-html5/issues/217
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: gber-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Recently a heap-based buffer overflow in the lexer of tidy5 was discovered
which can be triggered by malformed input [1]. This also affects the latest
version of the original W3C tidy project[2] where tidy5 was forked from and
which is packaged in all supported releases of openSUSE including Factory.

[1] https://github.com/htacg/tidy-html5/issues/217
[2] http://tidy.sourceforge.net/


--1433427781.aDb8fEB81.15732
Date: Thu, 4 Jun 2015 14:23:01 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 933651
           Summary: Yast2 reporting error during boot loader installation, grub2-install error ofpathname not found
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: PowerPC
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: normand-at-linux.vnet.ibm.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

Yast2 reporting error during boot loader installation, grub2-install error
ofpathname not found

* do network install of PowerPC P8 baremetal with
Tumbleweed-BE-DVD-ppc64-Build20150601-Media.iso from
https://openqa.opensuse.org/tests/66009/asset/4141
and adding startshell=1 boot parameter.

* from startshell only do exit to start yast

* select /dev/sda for installation, and minimalX config

* the install stopped with reported error message
  "error during boot loader installation" as per attached
fresh_error_bootloader_installation.png

* select Y push button to switch back to startshell
  do tarball of some of /var/log/* and /tmp/* and attached them in
error_bootloader_install.tgz

I assume the error is related to following lines extracted from y2log present
in tarball:
===
2015-06-04 14:37:20 <3> linux-v88h(3429) [bash]
ShellCommand.cc(shellcommand):78 Perl-Bootloader: 2015-06-04 14:37:20 <3>
pbl-yaml-3997.9 Core::RunCommand.1675: Error: '/usr/sbin/grub2-install
--target=powerpc-ieee1275 --force --skip-fs-probe
"/dev/disk/by-id/scsi-1IBM_IPR-0_6A9E2B0000000060-part1"' failed with exit code
1, output:
2015-06-04 14:37:20 <3> linux-v88h(3429) [bash]
ShellCommand.cc(shellcommand):78 <<<<<<<<<<<<<<<<
2015-06-04 14:37:20 <3> linux-v88h(3429) [bash]
ShellCommand.cc(shellcommand):78 Installing for powerpc-ieee1275 platform.
2015-06-04 14:37:20 <3> linux-v88h(3429) [bash]
ShellCommand.cc(shellcommand):78 /usr/sbin/grub2-install: error: ofpathname:
not found.
2015-06-04 14:37:20 <3> linux-v88h(3429) [bash]
ShellCommand.cc(shellcommand):78
2015-06-04 14:37:20 <3> linux-v88h(3429) [bash]
ShellCommand.cc(shellcommand):78 >>>>>>>>>>>>>>>>
===


--1433430505.CAF70.19169
Date: Thu, 4 Jun 2015 15:08:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 933664
           Summary: kiwi cannot create btrfs subvolumes that include a nested subdirectory in "volume name" within systemdisk
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: BuildService
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: rdannert-at-suse.com
        QA Contact: adrian-at-suse.com
          Found By: ---
           Blocker: ---

Created attachment 636776
  --> http://bugzilla.suse.com/attachment.cgi?id=636776&action=edit
OBS buildlog

Volume path var/lib/pgsql does not exist in unpacked tree
KIWI exited with error(s)

I am trying to build an appliance, that includes default btrfs subvolumes

This is the relevant part of the kiwi config file(attached)

    <systemdisk name="testing">
        <volume name="tmp"/>
        <volume name="opt"/>
        <volume name="srv"/>
        <volume name="var/crash"/>
        <volume name="var/spool"/>
        <volume name="boot/grub2/i386-pc"/>
        <volume name="boot/grub2/x86_64-efi"/>
        <volume name="usr/local"/>
        <volume name="var/lib/mailman"/>
        <volume name="var/lib/named"/>
        <volume name="var/lib/pgsql"/>
        <volume name="var/log"/>
        <volume name="var/opt"/>
        <volume name="var/tmp"/>
    </systemdisk>

the build fails with the following error message:
[  208s] Jun-04 14:55:59 <3> : Volume path var/lib/named does not exist in
unpacked treeJun-04 14:55:59 <3> : KIWI exited with error(s)
[  208s]

see attached buildlog and kiwi config

this is the OBS project/package:
home:rdannert:JeOS-Test  VM-bnc

The build is already using kiwi-7.02.52-1.1
from Virtualization:Appliances


body:
--1433528744.28410.3368
Date: Fri, 5 Jun 2015 18:25:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 933810
           Summary: Pam_ssh.so not working on 13.2
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: david.westfall@red-inc.us
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

A while back I installed pam_ssh on one of my 13.1 computers to test it out,
git it working.  After a in-place upgrad to 13.2 pam_ssh is no longer working.
I installed pam_ssh on another 13.1 computer today to make sure that I was
doing it correctly, and it is still working on 13.1.  pam-config -a --ssh

I turned on debugging for pam_ssh and here is what I see in my log.

2015-06-05T14:05:47.631787-04:00 Havoc pam_ssh[2538]: init authentication
module
2015-06-05T14:05:47.632338-04:00 Havoc pam_ssh[2538]: No SSH login-keys
directory.
2015-06-05T14:05:47.632681-04:00 Havoc pam_ssh[2538]: Grabbing password from
preceding auth module.
2015-06-05T14:05:47.633026-04:00 Havoc pam_ssh[2538]: Trying previous password
for SSH keys.
2015-06-05T14:05:47.633354-04:00 Havoc pam_ssh[2538]: No preceding password.
2015-06-05T14:05:47.644826-04:00 Havoc kdm: :0[2538]: pam_unix(xdm:auth):
authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=  user=root

Dave W

summary: Pam_ssh.so not working on 13.2


body:
--1433644182.7cdb0.4492
Date: Sun, 7 Jun 2015 02:29:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 933854
           Summary: mtr crashes with --xml option
    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: jnelson-suse-at-jamponi.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Subject says it all.
mtr crashes with --xml option

summary: mtr crashes with --xml option


body:
--1433839472.CaA6ca0.11929
Date: Tue, 9 Jun 2015 08:44:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 934056
           Summary: netcfg: do not use .site as default TLD
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: tchvatal-at-suse.com
          Reporter: lnussel-at-suse.com
        QA Contact: jsrain-at-suse.com
            Blocks: 923990
          Found By: ---
           Blocker: ---

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

going forward /etc/hostname should IMO not contain anything by default. Just
mark it %ghost.

summary: netcfg: do not use .site as default TLD


body:
--1433846531.ac254.15735
Date: Tue, 9 Jun 2015 10:42:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 934079
           Summary: qupzilla sometimes fails to start
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: vpelcak-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

qupzilla-qt5-1.8.6-32.4.x86_64

In some 50% of cases I get this failure:

>qupzilla
using qt5ct plugin (QupZilla: 1 extensions loaded
QupZilla: Crashed :( Saving backtrace in
/home/vpelcak/.config/qupzilla/crashlog ...
Backtrace successfuly saved in
/home/vpelcak/.config/qupzilla/crashlog/Crash-2015-06-09T12:36:53.txt
Neúspěšně ukončen (SIGABRT)

> cat /home/vpelcak/.config/qupzilla/crashlog/Crash-2015-06-09T12:36:53.txt
Time: út čvn 9 12:36:53 2015
Qt version: 5.4.2 (compiled with 5.4.2)
QupZilla version: 1.8.6
WebKit version: 538.1

============== BACKTRACE ==============
#0: qupzilla() [0x4036df]
#1: /lib64/libc.so.6(+0x33440) [0x7f396b7ba440]
#2:
/usr/lib64/libQupZilla.so.1(_ZNK6TabBar22comboTabBarPixelMetricEN11ComboTabBar8SizeTypeE+0x6d)
[0x7f396f7c44cd]
#3: /usr/lib64/libQupZilla.so.1(_ZN11ComboTabBar16setMinimumWidthsEv+0x2b)
[0x7f396f7c0bbb]
#4: /usr/lib64/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x816)
[0x7f396c2f7d46]
#5: /usr/lib64/libQt5Widgets.so.5(_ZN15QAbstractSlider12rangeChangedEii+0x3f)
[0x7f396f15e2ff]
#6: /usr/lib64/libQt5Widgets.so.5(_ZN15QAbstractSlider8setRangeEii+0x51)
[0x7f396eed9171]
#7: /usr/lib64/libQt5Widgets.so.5(+0x31ba65) [0x7f396ef9aa65]
#8: /usr/lib64/libQt5Widgets.so.5(_ZN7QWidget5eventEP6QEvent+0x973)
[0x7f396ee20593]
#9: /usr/lib64/libQt5Widgets.so.5(_ZN6QFrame5eventEP6QEvent+0x1e)
[0x7f396ef1746e]
#10:
/usr/lib64/libQt5Core.so.5(_ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent+0xf3)
[0x7f396c2c86f3]
#11:
/usr/lib64/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x6c)
[0x7f396ede0acc]
#12:
/usr/lib64/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x390)
[0x7f396ede5940]
#13:
/usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x65)
[0x7f396c2c84b5]
#14:
/usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate30sendPendingMoveAndResizeEventsEbb+0x1b1)
[0x7f396ee19ee1]
#15: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate11show_helperEv+0x23)
[0x7f396ee1d823]
#16: /usr/lib64/libQt5Widgets.so.5(_ZN7QWidget10setVisibleEb+0x137)
[0x7f396ee1f8b7]
#17: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate12showChildrenEb+0x110)
[0x7f396ee1d7d0]
#18: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate11show_helperEv+0x3f)
[0x7f396ee1d83f]
#19: /usr/lib64/libQt5Widgets.so.5(_ZN7QWidget10setVisibleEb+0x137)
[0x7f396ee1f8b7]
#20: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate12showChildrenEb+0x110)
[0x7f396ee1d7d0]
#21: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate11show_helperEv+0x3f)
[0x7f396ee1d83f]
#22: /usr/lib64/libQt5Widgets.so.5(_ZN7QWidget10setVisibleEb+0x137)
[0x7f396ee1f8b7]
#23: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate12showChildrenEb+0x110)
[0x7f396ee1d7d0]
#24: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate11show_helperEv+0x3f)
[0x7f396ee1d83f]
#25: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate12showChildrenEb+0xfa)
[0x7f396ee1d7ba]
#26: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate11show_helperEv+0x3f)
[0x7f396ee1d83f]
#27: /usr/lib64/libQt5Widgets.so.5(_ZN7QWidget10setVisibleEb+0x137)
[0x7f396ee1f8b7]
#28: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate12showChildrenEb+0x110)
[0x7f396ee1d7d0]
#29: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate11show_helperEv+0x3f)
[0x7f396ee1d83f]
#30: /usr/lib64/libQt5Widgets.so.5(_ZN7QWidget10setVisibleEb+0x137)
[0x7f396ee1f8b7]
#31: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate12showChildrenEb+0x110)
[0x7f396ee1d7d0]
#32: /usr/lib64/libQt5Widgets.so.5(_ZN14QWidgetPrivate11show_helperEv+0x3f)
[0x7f396ee1d83f]
#33: /usr/lib64/libQt5Widgets.so.5(_ZN7QWidget10setVisibleEb+0x137)
[0x7f396ee1f8b7]
#34: /usr/lib64/libQupZilla.so.1(_ZN13BrowserWindow10postLaunchEv+0x16b)
[0x7f396f64ad8b]
#35: /usr/lib64/libQupZilla.so.1(+0x33532d) [0x7f396f82932d]
#36: /usr/lib64/libQt5Core.so.5(_ZN7QObject5eventEP6QEvent+0x276)
[0x7f396c2f8b66]
#37: /usr/lib64/libQt5Widgets.so.5(_ZN7QWidget5eventEP6QEvent+0x3f4)
[0x7f396ee20014]
#38: /usr/lib64/libQt5Widgets.so.5(_ZN11QMainWindow5eventEP6QEvent+0x15b)
[0x7f396ef2cb5b]
#39:
/usr/lib64/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8c)
[0x7f396ede0aec]
#40:
/usr/lib64/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x390)
[0x7f396ede5940]
#41:
/usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x65)
[0x7f396c2c84b5]
#42:
/usr/lib64/libQt5Core.so.5(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1df)
[0x7f396c2ca34f]
#43: /usr/lib64/libQt5Core.so.5(+0x2da383) [0x7f396c320383]
#44: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x254)
[0x7f3968e38c74]
#45: /usr/lib64/libglib-2.0.so.0(+0x4bec8) [0x7f3968e38ec8]
#46: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c)
[0x7f3968e38f6c]
#47:
/usr/lib64/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5c)
[0x7f396c31f7fc]
#48:
/usr/lib64/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x11b)
[0x7f396c2c640b]
#49: /usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication4execEv+0x86)
[0x7f396c2cda96]
#50: qupzilla() [0x402da4]
#51: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f396b7a78c5]
#52: qupzilla() [0x4030e9]

summary: qupzilla sometimes fails to start


--1433916642.3dce1285.5195
Date: Wed, 10 Jun 2015 06:10:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 934175
           Summary: zsh-5.0.8: regression in the printf builtin
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: rneuhauser-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

bug: http://www.zsh.org/mla/users/2015/msg00609.html
fix: http://www.zsh.org/mla/workers/2015/msg01336.html


--1433931986.1D4dD4.4009
Date: Wed, 10 Jun 2015 10:26:26 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 934202
           Summary: NFS: nfs4_handle_delegation_recall_error: unhandled error -13.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: nfbrown-at-suse.com
          Reporter: tchatzimichos-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: mcaj-at-suse.com, mpluskal-at-suse.com, ncutler-at-suse.com
          Found By: ---
           Blocker: ---

This bug was reported first in the internal SUSE ticketing system. I am
copy-pasting all the current comments from that ticket to this one:

**** Nathan Cutler ****:

Ever since the migration from login.suse.cz to nfs.suse.cz that took
place over the weekend 2015-05-30 and 2015-05-31, my workstation's NFS
home (pantograf.suse.cz) in unstable.

The problem manifests approx. once every 3-4 hours of usage. Randomly,
for no apparent reason. First, I/O to /home partition starts to hang.
Load average starts to rise and a mystery process "10.100.2.89-man"
appears in "top" listing. This process is unkillable even with SIGKILL.
Running programs continue to work as long as they do not attempt I/O to
the home partition, then they freeze up. The only fix I know of is to
reboot the machine.

Referring to the log, the problem appears to be apparmor-related:

2015-06-03T10:52:33.390867+02:00 pantograf kernel: [ 1066.488685] audit:
type=1400 audit(1433321553.389:49): apparmor="
DENIED" operation="sendmsg" profile="/usr/bin/lessopen.sh" pid=5183
comm="file" laddr=10.100.12.15 lport=830 faddr=10.1
00.2.89 fport=2049 family="inet" sock_type="stream" protocol=6
2015-06-03T10:52:33.390885+02:00 pantograf kernel: [ 1066.488720] nfs:
RPC call returned error 13
2015-06-03T10:52:33.391849+02:00 pantograf kernel: [ 1066.489192] audit:
type=1400 audit(1433321553.390:50): apparmor="
DENIED" operation="sendmsg" profile="/usr/bin/lessopen.sh" pid=5183
comm="file" laddr=10.100.12.15 lport=830 faddr=10.1
00.2.89 fport=2049 family="inet" sock_type="stream" protocol=6
2015-06-03T10:52:33.391856+02:00 pantograf kernel: [ 1066.489204] nfs:
RPC call returned error 13
2015-06-03T10:52:33.414853+02:00 pantograf kernel: [ 1066.512310] audit:
type=1400 audit(1433321553.413:51): apparmor="
DENIED" operation="sendmsg" profile="/usr/bin/lessopen.sh" pid=5178
comm="lessopen.sh" laddr=10.100.12.15 lport=830 fad
dr=10.100.2.89 fport=2049 family="inet" sock_type="stream" protocol=6
2015-06-03T10:52:33.414863+02:00 pantograf kernel: [ 1066.512326] nfs:
RPC call returned error 13
2015-06-03T10:52:33.415875+02:00 pantograf kernel: [ 1066.513919] audit:
type=1400 audit(1433321553.414:52): apparmor="
DENIED" operation="sendmsg" profile="/usr/bin/lessopen.sh" pid=5185
comm="lessopen.sh" laddr=10.100.12.15 lport=830 fad
dr=10.100.2.89 fport=2049 family="inet" sock_type="stream" protocol=6
2015-06-03T10:52:33.415888+02:00 pantograf kernel: [ 1066.513935] nfs:
RPC call returned error 13
2015-06-03T10:52:33.416857+02:00 pantograf kernel: [ 1066.514853] audit:
type=1400 audit(1433321553.415:53): apparmor="
DENIED" operation="sendmsg" profile="/usr/bin/lessopen.sh" pid=5185
comm="file" laddr=10.100.12.15 lport=830 faddr=10.1
00.2.89 fport=2049 family="inet" sock_type="stream" protocol=6
2015-06-03T10:52:33.416869+02:00 pantograf kernel: [ 1066.514868] nfs:
RPC call returned error 13
2015-06-03T10:52:33.417857+02:00 pantograf kernel: [ 1066.515346] audit:
type=1400 audit(1433321553.416:54): apparmor="
DENIED" operation="sendmsg" profile="/usr/bin/lessopen.sh" pid=5185
comm="file" laddr=10.100.12.15 lport=830 faddr=10.1
00.2.89 fport=2049 family="inet" sock_type="stream" protocol=6
2015-06-03T10:52:33.417867+02:00 pantograf kernel: [ 1066.515358] nfs:
RPC call returned error 13

Please advise.

Update: I disabled AppArmor so those messages are gone

But the I/O lockups continue. After examining the log closer, I believe this is
the relevant message:

2015-06-03T16:52:33.508329+02:00 pantograf kernel: [13191.933894] NFS:
nfs4_handle_delegation_recall_error: unhandled error -13.

**** Neil Brown ****:

I'm pretty sure that I've seen exactly this bug already.  I just need to
remember which one...

I don't think this is related to kerberos at all.  It is purely an NFSv4
state management issue.

It is a bit like 831029, but maybe not exactly the same.

I'll have a more thorough look after the weekend.  Exactly which kernel do
you have on your client?

NeilBrown

**** Nathan Cutler ****:

Linux pantograf 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015
(93c1539) x86_64 x86_64 x86_64 GNU/Linux

**** Theo Chatzimichos ****:

Just for the record, Martin Caj's PC runs KDE with the same kernel version, and
it has mounted the NFS /home since Friday. I just checked its dmesg and didn't
see such error messages reported. The machine is now on low load though since
Martin is away

**** Nathan Cutler ****:

It only happens if you actually use the desktop. I can leave KDE running
all night, all day and as long as I do not use the machine, or use it
only via ssh from home, nothing happens. The I/O freezes only happen
when I am sitting physically at the machine, clicking in Thunderbird,
Pidgin, Firefox, etc.

When Martin gets back I will work with him to reproduce it.

Nathan

**** Martin Pluskal ****:

Hi
I have also encountered those issues (on current TW with kernel
4.1.0-rc6-2.g8f2a4d1-desktop) I have captured dmesg after issuing
"rpcdebug -m nfs -s all" - see
http://users.suse.cz/~mpluskal/bugs/nfs_issues/dmesg.txt.xz - perhaps it
contains something useful.

Kind regards

Martin

**** Neil Brown ****:

I've had a bit more of a look at this and I think it is a new problem.

There have been quite a few different bugs which involve the nn.nn.nn.nn-man
thread spinning, but this doesn't seem to fit the pattern of any of them.

So maybe it would be best to open a bug on bugzilla.

The "unhandled error -13." is an NFS4ERR_ACCES error.

When the client tried to open some file, the Netapp gave it a delegation.  It
presumably then opened the file again without telling the server, on the
strength of that delegation.
At some point the delegation needed to be  returned so the client requested
explicit opens from the server.  One of those failed with "EACCESS" meaning the
user on
the client didn't seem to have permission.  That is very odd.

The state management thread then goes into a spin.  This suggests that it was
the state management thread which decided that the delegation needed to be
returned.
Maybe it got some sort of state error.  I cannot easily find a path through the
code that would make it spin, but it is fairly complex code.

One thing that might help is to capture the content of /proc/PID/stack for the
threads that is using all the CPU time.  Capture that a dozen times or so in
quick succession.
Or maybe capture hundreds and discard the duplicates.

The other thing that could be useful is a tcpdunp trace of NFS (port 2049)
traffic between client and server when the problem occurs.  So if you can
reliably trigger it, that should
be easy to get.


body:
--1433936277.c783B6.13212
Date: Wed, 10 Jun 2015 11:37:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 934214
           Summary: libgio requires dbus-1-x11
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

the fix for bug 678518 introduced a dependency between libgio and dbus-1-x11.
Unfortunately libgio is needed by libsecret which is needed by gpg which is
needed by libzypp. Therefore even most minimal installs draw in X. Would it be
possible to make libgio gracefully fail if dbus-launch is not there and make
the dependency optional?

summary: libgio requires dbus-1-x11


body:
--1434102373.CFe181b10.23311
Date: Fri, 12 Jun 2015 09:46:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 934531
           Summary: sdhci memory corruption
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: CONFIRMED
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: jslaby-at-suse.com
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 637633
  --> http://bugzilla.novell.com/attachment.cgi?id=637633&action=edit
/var/log/messages excerpt

When DMA fails in sdhci, it may corrupt memory in kernels >= 4.0.

summary: sdhci memory corruption


--1434106126.26f2d0450.29693
Date: Fri, 12 Jun 2015 10:48:46 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 934544
           Summary: seccheck: bash function missing () in the declaration
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: vpereira-at-novell.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hi,

I'm receiving errors after the last seccheck update:

/usr/lib/secchk/helper.inc: line 46: guessable_password_email: command not
found
sed: can't read blurbs/guessable_passwd.txt: No such file or directory

/usr/lib/secchk/helper.inc: line 49: syntax error near unexpected token `}'
/usr/lib/secchk/helper.inc: line 49: `}'
/usr/lib/secchk/helper.inc: line 46: guessable_password_email: command not
found
sed: can't read blurbs/guessable_passwd.txt: No such file or directory
/usr/lib/secchk/helper.inc: line 49: syntax error near unexpected token `}'
/usr/lib/secchk/helper.inc: line 49: `}'
/usr/lib/secchk/security-daily.sh: line 64: check_for_globally_exported_fs:
command not found
/usr/lib/secchk/security-daily.sh: line 70: list_loaded_kernel_modules: command
not found
/usr/lib/secchk/security-daily.sh: line 73: nfs_mounted_with_missing_nosuid:
command not found
/usr/lib/secchk/security-daily.sh: line 76:
display_programs_with_bound_sockets: command not found
/usr/lib/secchk/security-control.sh: line 52: send_daily_changes: command not
found

Is anybody aware of this?

Thanks!
Markus


--1434112225.bFe81e5.8096
Date: Fri, 12 Jun 2015 12:30:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 934571
           Summary: Systemd unit file for network:utilities/rsh
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: jkeil-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The network:utilities/rsh package needs a systemd unit file. Please add it.


--1434203510.C6CDd1.11660
Date: Sat, 13 Jun 2015 13:51:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 934640
           Summary: YaST2 crashes in installer on ASUS X205TA
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: kukuk-at-suse.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

Created attachment 637740
  --> http://bugzilla.suse.com/attachment.cgi?id=637740&action=edit
yast2-logs.tgz

I have a netbook with a eMMC disk. YaST2 installer crashes during installation
when creating the installation proposal.


--1434410269.Ae70B40.16770
Date: Mon, 15 Jun 2015 23:17:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 934828
           Summary: iproute2 distribution data packaged in wrong directory
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: nvbugs-at-hhecht.e4ward.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The probability distribution files in the iproute2 package, and used by tc, are
packaged in /usr/share/tc.  This may make sense, as they are ASCII, but tc
looks for them in /usr/lib64/tc.  As a result, things like:
tc qdisc change dev $if root netem delay 100ms 20ms distribution normal
result in
No distribution data for normal (/usr/lib64/tc//normal.dist: No such file or
directory)

So, either the *.dist files need to go in %{_libdir}/tc, or tc needs to be
patched to look in /usr/share.


--1434461663.A1DDd5Be5.9421
Date: Tue, 16 Jun 2015 13:34:23 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 934934
           Summary: VUL-0: CVE-2015-3230: 389-ds: nsSSL3Ciphers preference not enforced server side (regression)
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
               URL: https://smash.suse.de/issue/117744/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: jengelh-at-inai.de
          Reporter: astieger-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

Via RH..

nsSSL3Ciphers preference not enforced server side

https://fedorahosted.org/389/changeset/53c9c4e84e3bcbc40de87b1e7cf7634d14599e1c/

> Description: The fix for ticket 47838 accidentally changed the timing
> of setting default cipher preferences and creating a sslSocket which
> broke setting the default preferences to each sslSocket.

References:
https://fedorahosted.org/389/ticket/48194
https://fedorahosted.org/389/ticket/47838
https://bugzilla.redhat.com/show_bug.cgi?id=1232096
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-3230
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3230


--1434797628.FfBAb0.9437
Date: Sat, 20 Jun 2015 10:53:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 935510
           Summary: p11-kit vs gcc 5 => ffi_prep_cif failed: 2
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

In various build logs (mostly java) it appears as if p11-kit is having issues
with the 'trust' binary.

For example, while installing mozilla-ca-certificates into the buildroot, it
complains:

>[   18s] ca-certificates-1+git20150324.e3ee392-########################################
>[   18s] ffi_prep_cif failed: 2
>[   18s] p11-kit: shouldn't be reached at init_wrapper_funcs
>[   18s] p11-kit: shouldn't be reached at p11_virtual_wrap
>[   18s] p11-kit: '*module != NULL' not true at prepare_module_inlock_reentrant

A local build of p11-kit with make check enabled results in very similar
errors, thus hinting that p11-kit is indeed having an issue:

>[   43s] ok 8 /pin/test_pin_ref_unref
>[   43s] PASS: test-pin
>[   43s] ffi_prep_cif failed: 2
>[   43s] /bin/sh: line 5: 12046 Aborted                 ${dir}$tst
>[   43s] FAIL: test-init
>[   43s] ffi_prep_cif failed: 2
>[   43s] /bin/sh: line 5: 12051 Aborted                 ${dir}$tst
>[   43s] FAIL: test-modules
>[   44s] 1..9

(sadly, make check is not enabled in p11-kit, so stagings did not catch it)


body:
--1434964110.3DaFc10.4949
Date: Mon, 22 Jun 2015 09:08:30 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 935570
           Summary: Upgrade to docker 1.7.0
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Other
          Assignee: fcastelli-at-suse.com
          Reporter: fcastelli-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Upgrade to latest stable version of docker (1.7.0):

* Runtime
  - Experimental feature: support for out-of-process volume plugins
  - The userland proxy can be disabled in favor of hairpin NAT using the
daemon’s `--userland-proxy=false` flag
  - The `exec` command supports the `-u|--user` flag to specify the new process
owner
  - Default gateway for containers can be specified daemon-wide using the
`--default-gateway` and `--default-gateway-v6` flags
  - The CPU CFS (Completely Fair Scheduler) quota can be set in `docker run`
using `--cpu-quota`
  - Container block IO can be controlled in `docker run` using`--blkio-weight`
  - ZFS support
  - The `docker logs` command supports a `--since` argument
  - UTS namespace can be shared with the host with `docker run --uts=host`
* Quality
  - Networking stack was entirely rewritten as part of the libnetwork effort
  - Engine internals refactoring
  - Volumes code was entirely rewritten to support the plugins effort
  - Sending SIGUSR1 to a daemon will dump all goroutines stacks without exiting
* Build
  - Support ${variable:-value} and ${variable:+value} syntax for environment
variables
  - Support resource management flags `--cgroup-parent`, `--cpu-period`,
`--cpu-quota`, `--cpuset-cpus`, `--cpuset-mems`
  - git context changes with branches and directories
  - The .dockerignore file support exclusion rules
* Distribution
  - Client support for v2 mirroring support for the official registry
* Bugfixes
  - Firewalld is now supported and will automatically be used when available
  - mounting --device recursively

pkgs: docker go go-net

summary: Upgrade to docker 1.7.0


--1435049684.bdB7DcE0.19427
Date: Tue, 23 Jun 2015 08:54:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 935716
           Summary: [Patch] missing IPv6 Broadcast support in SuSEfirewall2
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: ivan.topolsky@isb-sib.ch
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 638750
  --> http://bugzilla.opensuse.org/attachment.cgi?id=638750&action=edit
adds missing commands for IPv6 broadcast

SuSEfirewall2 emits only "iptables" (IPv4) commands for broadcast.
"ip6tables" (IPv6) are missing.
Thus it's not possible to use broadcast over IPv6

(e.g.: avahi doesn't work over IPv6).

Attached patch fixes by adding the missing commands.
Tested with avahi over IPv6.

Also submitted upstream as pull request:
https://github.com/openSUSE/susefirewall2/pull/4

(is that the official repository, now that gitorious is closing ?)


body:
--1435059337.dffA047.30181
Date: Tue, 23 Jun 2015 11:35:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 935736
           Summary: screen.xterm unknown terminal type
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: bwiedemann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: astieger-at-suse.com, mls-at-suse.com, posix.ru-at-gmail.com
          Found By: Development
           Blocker: ---

on Factory, I am using screen in xterm
which now has $TERM set to screen.xterm

However, when I ssh to openSUSE-13.2 (or SLE-12) or older hosts
and try to run "top" there, I get
'screen.xterm' unknown terminal type

the workaround is to do there
TERM=xterm

summary: screen.xterm unknown terminal type


body:
--1435132713.BDeCEA4.32424
Date: Wed, 24 Jun 2015 07:58:33 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 935864
           Summary: zlib: package minizip?
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: tchvatal-at-suse.com
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: ---
           Blocker: ---

zlib contains contrib/minizip which at least by judging from the use of unzip.h
is contained as copy in 30 other packages. What about building minizip as
separate sub package?

summary: zlib: package minizip?


--1435214115.DdFB3.23037
Date: Thu, 25 Jun 2015 06:35:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 935993
           Summary: Kernel-desktop x86_64 4.1 freezes at beginning of boot process
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201505*
          Hardware: x86-64
                OS: SUSE Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: w.pelser-at-web.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

At the early beginning of the boot process kernel freezes with "found device
innostor". Next line should be "Found device
/dev/disk/by-uuid/0bcdd615-1001-476e-abd6-89e1f0559259" (here copied from a
normal boot process) , but nothing happens.
Innostor is an USB 3.0 Stick.

I tried to reboot several times, but nothing changes. So I had to delete the
new kernel.. There is no log-file for this event.

System is intel 945 GTP

Self-compiled  kernel from 4.1.tar.xz works fine!


--1435328884.0C4dA0.15716
Date: Fri, 26 Jun 2015 14:28:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 936251
           Summary: bits/time.h misses CLOCK_TAI that is present in linux/time.h
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: i686
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: avsco-at-mail.ru
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Currently, /usr/include/bits/time.h defines these clock types for
`clock_gettime()` function (from /usr/include/time.h):

> #   define CLOCK_REALTIME               0
> #   define CLOCK_MONOTONIC              1
> #   define CLOCK_PROCESS_CPUTIME_ID     2
> #   define CLOCK_THREAD_CPUTIME_ID      3
> #   define CLOCK_MONOTONIC_RAW          4
> #   define CLOCK_REALTIME_COARSE        5
> #   define CLOCK_MONOTONIC_COARSE       6
> #   define CLOCK_BOOTTIME               7
> #   define CLOCK_REALTIME_ALARM         8
> #   define CLOCK_BOOTTIME_ALARM         9

However, in /usr/include/linux/time.h we have more options:

> #define CLOCK_REALTIME                  0
> #define CLOCK_MONOTONIC                 1
> #define CLOCK_PROCESS_CPUTIME_ID        2
> #define CLOCK_THREAD_CPUTIME_ID         3
> #define CLOCK_MONOTONIC_RAW             4
> #define CLOCK_REALTIME_COARSE           5
> #define CLOCK_MONOTONIC_COARSE          6
> #define CLOCK_BOOTTIME                  7
> #define CLOCK_REALTIME_ALARM            8
> #define CLOCK_BOOTTIME_ALARM            9
> #define CLOCK_SGI_CYCLE                 10
> #define CLOCK_TAI                       11

When called with hardcoded value 11 for CLOCK_TAI, clock_gettime() succeeds and
indeed returns a value that differs from REALTIME by a configured TAI offset,
so I confidently conclude that openSUSE's kernel really supports CLOCK_TAI.
Thus /usr/include/bits/time.h should be updated to reflect such capability.

As a workaround, I tried to include <linux/time.h> instead of or in addition to
<time.h>, but they (and other header files included by them) turned out to be
highly incompatible due to competing declarations, some of which cannot be
prevented by include guards. (The progress of my vain workarounds is covered in
more detail at http://stackoverflow.com/q/31056979) Anyway, I suppose that
including anything from <linux/...> should be generally avoided in userland
programs, unless they are doing something very system-specific, for which
`clock_gettime()` does not qualify at all.


--1435329225.BDC70.18547
Date: Fri, 26 Jun 2015 14:33:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 936254
           Summary: VirtualBox guest time skew - virtualbox-guest-tools fails to enable VBoxService
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Hardware: All
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: hohmuth-at-os.inf.tu-dresden.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

An OpenSUSE system running as a guest in a VirtualBox VM quickly accumulates a
lot of clock skew (multiple minutes per day).

The reason is that the guest additions in package virtualbox-guest-tools do not
enable the VBoxService daemon shipped in that same package.  The corresponding
startup script is not included in the package
(src/VBox/Additions/linux/installer/vboxadd-service.sh in the virtualbox source
tree).

Tested with OpenSUSE 13.1 as both guest and host systems.  (Without ntpd
running in the guest, of course.)


--1435416736.eF3ca0.18180
Date: Sat, 27 Jun 2015 14:52:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 936309
           Summary: cupsd hangs when DefaultPolicy is switched to "allowallforanybody"
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Printing
          Assignee: jsmeix-at-suse.com
          Reporter: reinhard.hennig-at-freenet.de
        QA Contact: jsmeix-at-suse.com
          Found By: ---
           Blocker: ---

If you set DefaultPolicy from default to allowallforanybody, which is risky but
quite popular, all requests like lpstat -v or lpq hang and must be interrupted
by ctrl-c. Prnting is not possible.
no problems occur on older versions of opensuse (e.g. 12.2).


--1435418114.68a0F10.22142
Date: Sat, 27 Jun 2015 15:15:14 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 936311
           Summary: python3-sqlalchemy broken due to sa2to3.py script in build
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: All
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: os-dev-at-jacraig.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The Python 3 version of SQLAlchemy (0.8.3) that ships with OpenSUSE 13.2 is
broken. The error

ImportError: cannot import name 'deque'

can be seen if you try

>>> from sqlalchemy.ext.declarative import declarative_base

There are likely a lot of other use cases which cause the error, but this is
just one. The error is caused by the "sa2to3.py" script being run during build
which erroneously changes some code to use a relative import (see
https://partner-bugzilla.redhat.com/show_bug.cgi?id=957868 for when Fedora ran
into this).

In versions >= 0.9.0 of SQLAlchemy the sa2to3.py script is not used at all any
more, and the Fedora bug link above suggests that it may not be necessary even
in the 0.8.x builds. The current Factory version, 1.0.5, would fix this
problem.