body:
Build Identifier:

my card reader who use RTS5229 chipset is not able to read sdxc card under
linux

Reproducible: Always

Steps to Reproduce:
1.put a sdxc card in the card reader
2.
3.
Actual Results:
000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
[487522.891191] mmc0: card 5449 removed
[488918.362015] mmc0: cannot verify signal voltage switch
[488918.461027] mmc0: new ultra high speed SDR104 SDXC card at address 0007
[488918.461273] mmcblk0: mmc0:0007 SD64G 59.7 GiB
[488918.461793]  mmcblk0: p1
[489003.696764]  mmcblk0: p1
[489217.331670] mmc0: card 0007 removed

Expected Results:
be able to read card

/sbin/lspci -nnk|grep -A2 5229
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI
Express Card Reader [10ec:5229] (rev 01)
        Subsystem: Lenovo Device [17aa:21fc]
        Kernel driver in use: rtsx_pci

summary: sdxc card not able to read


--1417991338.dBafD0fd0.24225
Date: Sun, 7 Dec 2014 22:28:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 908744
           Summary: gnuradio start error on tumbleweed 20141206
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: dmitry-at-roshchin.org
          Reporter: dmitry-at-roshchin.org
        QA Contact: opensuse-communityscreening-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

gnuradio start error on tumbleweed 20141206.

Logs:

dmitry@main:~> gnuradio-companion
linux; GNU C++ version 4.8.3 20140627 [gcc-4_8-branch revision 212064];
Boost_105600; UHD_003.007.003-0-unknown

<<< Welcome to GNU Radio Companion 3.7.5.1 >>>

Preferences file: /home/dmitry/.grc
Block paths:
        /usr/share/gnuradio/grc/blocks
        /home/dmitry/.grc_gnuradio
Error: 'options'
>>> Failure
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/gnuradio/grc/gui/MainWindow.py",
line 179, in new_page
    flow_graph = self._platform.get_new_flow_graph()
  File "/usr/lib64/python2.7/site-packages/gnuradio/grc/base/Platform.py", line
188, in get_new_flow_graph
    def get_new_flow_graph(self): return self.FlowGraph(platform=self)
  File "/usr/lib64/python2.7/site-packages/gnuradio/grc/python/FlowGraph.py",
line 37, in __init__
    _FlowGraph.__init__(self, **kwargs)
  File "/usr/lib64/python2.7/site-packages/gnuradio/grc/base/FlowGraph.py",
line 40, in __init__
    self.import_data()
  File "/usr/lib64/python2.7/site-packages/gnuradio/grc/base/FlowGraph.py",
line 279, in import_data
    self._options_block = self.get_parent().get_new_block(self, 'options')
  File "/usr/lib64/python2.7/site-packages/gnuradio/grc/base/Platform.py", line
198, in get_new_block
    def get_new_block(self, flow_graph, key): return self.Block(flow_graph,
n=self._blocks_n[key])
  File "/usr/lib64/python2.7/site-packages/gnuradio/grc/base/odict.py", line
34, in __getitem__
    return self._data[key]
KeyError: 'options'

Unfortunately I don't know when this problem began. Last gnuradio-related
update was boost library 1.54 -> 1.56 update.


--1418049436.d068fc50.15108
Date: Mon, 8 Dec 2014 14:37:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 908846
           Summary: Failed to set quota: Integer overflow while interpreting decimal unit
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: wolf-at-parallels.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Failed to set quota: Integer overflow while interpreting decimal unit:

---
localhost:~ # rpm -q quota
quota-4.01_git201405011753-2.1.2.x86_64
localhost:~ # setquota -a -u testuser 1000 2000 100 200
setquota: Bad inode softlimit: 100: Integer overflow while interpreting decimal
unit.
setquota: Usage:
  setquota [-u|-g] [-F quotaformat] <user|group>
        <block-softlimit> <block-hardlimit> <inode-softlimit> <inode-hardlimit>
-a|<filesystem>...
  setquota [-u|-g] [-F quotaformat] <-p protouser|protogroup> <user|group>
-a|<filesystem>...
  setquota [-u|-g] [-F quotaformat] -b [-c] -a|<filesystem>...
  setquota [-u|-g] [-F quotaformat] -t <blockgrace> <inodegrace>
-a|<filesystem>...
  setquota [-u|-g] [-F quotaformat] <user|group> -T <blockgrace> <inodegrace>
-a|<filesystem>...

-u, --user                 set limits for user
-g, --group                set limits for group
-a, --all                  set limits for all filesystems
    --always-resolve       always try to resolve name, even if is
                           composed only of digits
-F, --format=formatname    operate on specific quota format
-p, --prototype=protoname  copy limits from user/group
-b, --batch                read limits from standard input
-c, --continue-batch       continue in input processing in case of an error
-t, --edit-period          edit grace period
-T, --edit-times           edit grace times for user/group
-h, --help                 display this help text and exit
-V, --version              display version information and exit

Bugs to: jack-at-suse.cz
---

Note that it's already fixed by commit
http://sourceforge.net/p/linuxquota/code/ci/663ac451b045b4823d6d633893a5d748c09f42f2/
.

Please, apply the patch and place quota package to updates.


--1418059606.FBb337d0.13241
Date: Mon, 8 Dec 2014 17:26:46 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 908875
           Summary: crash in libnetfilter_cthelper.so:nfct_free_helper
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201412*
          Hardware: All
                OS: Linux
            Status: CONFIRMED
          Severity: Major
          Priority: P5 - None
         Component: Network
          Assignee: jengelh-at-inai.de
          Reporter: jengelh-at-inai.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

A use after free bug is present in libnetfilter_cthelper, which has shown up
with an openSUSE user. As libnetfilter_cthelper is used by conntrack-tools,
conntrackd can also hit the problem.


body:
--1418062433.C4a60.15978
Date: Mon, 8 Dec 2014 18:13:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 908883
           Summary: cyrus-sasl-scram refers to wrong RFC
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          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: hdk-at-dkluenter.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The documentation f�r cyrus-sasl-scram referes to RFC 2222, which is obsolete,
The valid documentation for SASL is now RFC 4422, The SASL Mechanism SCRAM is
described in RFC 5802 and for LDAP RFC5803.

summary: cyrus-sasl-scram refers to wrong RFC


body:
--1418118170.5A61B660.25458
Date: Tue, 9 Dec 2014 09:42:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 908992
           Summary: 2 security fixes in pwgen 2.07
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: All
                OS: All
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: vetter-at-physik.uni-wuerzburg.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

See also
https://portal.cert.dfn.de/adv/DFN-CERT-2014-1605/

There is a new version of pwgen in sourceforge, it is said to fix the problems.

summary: 2 security fixes in pwgen 2.07


body:
--1418198454.b16c5e0.27422
Date: Wed, 10 Dec 2014 08:00:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 909189
           Summary: [regression] dhclient crashes
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201412*
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After the recent update, dhclient is constantly crashing.

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f2209aff4cc in get_hw_addr (info=info@entry=0x7f220b07efa0) at
lpf.c:608
608                     if (ifa->ifa_addr->sa_family != AF_PACKET)
(gdb) where
#0  0x00007f2209aff4cc in get_hw_addr (info=info@entry=0x7f220b07efa0) at
lpf.c:608
#1  0x00007f2209aff657 in if_register_lpf (info=info@entry=0x7f220b07efa0) at
lpf.c:104
#2  0x00007f2209aff840 in if_register_receive (info=0x7f220b07efa0) at
lpf.c:223
#3  0x00007f2209af911a in discover_interfaces (state=4) at discover.c:1264
#4  0x00007f2209add0d8 in main (argc=<optimized out>, argv=0x7fffb87c06d8) at
dhclient.c:646
(gdb) p ifa->ifa_addr
$1 = (struct sockaddr *) 0x0

And indeed ifa->ifa_addr can be NULL according to the manpage of getifaddrs.

summary: [regression] dhclient crashes


--1418222970.defBdab52.13533
Date: Wed, 10 Dec 2014 14:49:30 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 909280
           Summary: yast2-schema fails to build in openSUSE:Factory
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201412*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

With the latest update of kiwi, the schema was changed to version 6.2
(bootloader specific settings, if not specified, grub2 is being used)

yast2-schema currently requires kiwi-schema = 6.1, which is no longer provided,
resulting in a 'unresolvable' package.


body:
--1418230997.Eb3F8b78.8489
Date: Wed, 10 Dec 2014 17:03:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 909307
           Summary: wicked.service can't configure user-class id
    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: asaf.magen-at-sap.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

wicked does not handle DHCLIENT_USER_CLASS ifcfg setting properly.

pkgs: sysconfig wicked


--1418250933.Da88b80.22295
Date: Wed, 10 Dec 2014 22:35:33 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 909359
           Summary: snapper delete command does not completely delete snapshot folders
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: rb03884-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The "snapper delete snapshot id" and "Yast's Snapper" do not completely delete
the numbered snapshot folders in /.snapshots/.

Every snapshot id folder contains a single grub-snapshot.cfg file referring to
the snapshot id number.

Is this deliberate or a limitation of snapper? Can you please add an extra
cleanup command to remove the folders completely?


--1418287303.eAA40.4650
Date: Thu, 11 Dec 2014 08:41:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 909418
           Summary: when ejecting DVD using hardware button, system thinks DVD is still mounted
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: Ulrich.Windl-at-rz.uni-regensburg.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When I used a mounted DVD (in a BluRay writer) and press eject-button on the
drive, the media ejects, and I close the tray. In GNOME (at least) the system
still thinks the media is mounted, even if I inserted another DVD into the
drive in the meantime.


--1418388059.0DA654e60.3102
Date: Fri, 12 Dec 2014 12:40:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 909695
           Summary: segmentation fault after pack & ioctl & unpack
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Ruby
          Assignee: ruby-devel-at-suse.de
          Reporter: bkutil-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

This snippet (requires sudo due to ioctl call) produces a segmentation fault on
the 13.2 ruby [1], affecting current ruby2.0 and ruby2.1 packages. The bug is
currently tracked upstream [2], but not yet fixed, however, a patch is known to
work as a fix when backported [3].

require 'socket'
SIOCETHTOOL = 0x8946
i = ["lo", "\n"].pack("a16p")
s = Socket.new(Socket::AF_INET, Socket::SOCK_DGRAM, 0)
s.ioctl(SIOCETHTOOL, i)
i.unpack("a16p")[1]

[1] ruby 2.1.3p242 (2014-09-19 revision 47630) [x86_64-linux-gnu]
[2] https://bugs.ruby-lang.org/issues/10568
[3]
https://github.com/ruby/ruby/commit/4b146b25333c52ca4503dfc3c4215b583e8e9963


--1418606261.1264e0.15415
Date: Mon, 15 Dec 2014 01:17:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 909864
           Summary: [Hyper-v] Failed online backup when the guest mount udf/squashfs type
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: SLES 12
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: kyliel-at-microsoft.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

RHEL7.0 reports below issue and this should be a common issue.
https://bugzilla.redhat.com/show_bug.cgi?id=1160584

And 2 patches are accepted by community. Could you please include those patches
in
 OL7? Thank you.


body:
--1418665684.EABaE0.16150
Date: Mon, 15 Dec 2014 17:48:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 910109
           Summary: X11:XOrg/Mesa: Build with --enable-nine
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: 3rd party software
          Assignee: sndirsch-at-suse.com
          Reporter: johannesobermayr-at-gmx.de
        QA Contact: opensuse-communityscreening-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

Please build Mesa with --enable-nine ...

summary: X11:XOrg/Mesa: Build with --enable-nine


--1418667174.2aB82.17053
Date: Mon, 15 Dec 2014 18:12:54 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 910111
           Summary: istgt uses incorrect systemd service file
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: CONFIRMED
          Severity: Minor
          Priority: P5 - None
         Component: Other
          Assignee: ddiss-at-suse.com
          Reporter: ddiss-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

There are a couple of minor issues with the existing istgt.service file:
- It uses an incorrect PIDFile path.
- It's shipped with execute permissions.


--1418668186.5dFBe42.18694
Date: Mon, 15 Dec 2014 18:29:46 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 910112
           Summary: istgt documentation and config files refer to incorrect paths
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: CONFIRMED
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: ddiss-at-suse.com
          Reporter: ddiss-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

istgt generates documentation and sample configuration files at buildtime,
based on the paths specified via configure.

There is currently a mismatch between the installation paths, and the paths
specified in the documentation and sample config files. This is mostly due to
the fact that the %%CONFIGDIR%% placeholder is incorrectly specified instead of
 %%SYSCONFDIR%%.


--1418674609.eBAc030.24075
Date: Mon, 15 Dec 2014 20:16:49 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 910128
           Summary: vsftpd says 500 OOPS child died when downloading a file
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Hardware: x86-64
                OS: openSUSE 13.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: jimc-at-math.ucla.edu
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 617253
  --> http://bugzilla.opensuse.org/attachment.cgi?id=617253&action=edit
vsftpd configuration file

This is vsftpd-3.0.2-10.1.2.x86_64 with kernel-desktop-3.11.10-21.1.x86_64,
socket activated (unit files attached, probably irrelevant).  The client is
tnftp-20100108-2.4.1.x86_64 (probably irrelevant).  All from OpenSuSE-13.1.

When I create ~ftp/testfile.txt and do:
ftp -a -o /tmp/outfile.txt -q 5 -V xena.example.com:testfile.txt
It reports:
500 OOPS: child died
ftp: Can't connect or login to host `xena:?'
strace reveals that the child is being killed by SIGSYS (invalid argument to
syscall); the syscall just before the signal is:
socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3
(looks unexceptional, looks like it worked.)

This bug is closely related; see comment 29 with exactly my symptom and a fix:
https://bugzilla.redhat.com/show_bug.cgi?id=845980
Several users report relief by adding to /etc/vsftpd.conf
seccomp_sandbox=NO
and it made my symptom go away; the file is downloaded in perfect shape.

While one possible "fix" is to make seccomp_sandbox=NO the default for vsftpd,
several Red Hat users believe that the problems began with a kernel upgrade,
suggesting that the real problem is to be found there.  I can't report a
particular kernel upgrade that may have set off this behavior.


--1418724821.DF1Bedd0.29218
Date: Tue, 16 Dec 2014 10:13:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 910265
           Summary: config.postfix does not upgrade the chroot
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: d.kuhn@heinlein-support.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 617413
  --> http://bugzilla.opensuse.org/attachment.cgi?id=617413&action=edit
fix update chroot

The bash script config.postfix doesnt upgrade the chroot  if the variables
"POSTFIX_CHROOT" and "POSTFIX_UPDATE_CHROOT_JAIL" are set to "yes" in
/etc/sysconfig/postfix.

There is a nested double check in config.postfix in the function mkchroot in
line 98 and 103 if $POSTFIX_CHROOT != "yes"
The else clause in line 122, which would upgrade the chroot, will never be
executed.

The script worked in OpenSuse 13.1.

A quick and dirty workaround is the attached patch.


body:
--1418739715.AbBDED80.22682
Date: Tue, 16 Dec 2014 14:21:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 910323
           Summary: wicked fails to set hostname
    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: hare-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I've configured a static hostname via 'yast2 lan'. Upon startup I'm seeing
these messages in the journal:

Dec 11 17:22:11 linux-gj39 wickedd[739]: ni_process_reap: process 769 has not
ex
[ .. ]
Dec 11 17:22:17 c236 wickedd[739]: subprocesses exited with error
Dec 11 17:22:17 c236 wickedd[739]: failed to install hostname settings

and the hostname is not set.

summary: wicked fails to set hostname


--1418806904.E7Cb8D583.23854
Date: Wed, 17 Dec 2014 09:01:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 910440
           Summary: "soft lockup CPU#0 stuck..." with bache devices
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: seife-at-novell.slipkontur.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

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

After updating my home server to 13.2 I got "soft lockup" messages in "
bcache_gc" about once per week, often rendering the bcache device unusable
(nothing would read or write to it anymore) and in the end requiring a hard
reboot.

I have the following hardware setup:
* Abit IP35-E(Intel P35+ICH9R) mainboard
* core2 duo E6750 CPU
* 8GB memory
* 2TB 2.5" laptop disk as main system disk
* 240GB Crucial CT240M5 SSD to use as bcache device
* 2TB WD Red (uncached) for "big data"
* 1TB WD Green (uncached) for "backup data"

bcache-backed devices are:
30GB /home (very low "workout" overall, I'm the only active user on the box and
do not really do anything in $HOME)
750GB /space1 (local data, lots of files, kernel development, embedded build
system, git repos,... "high workout" filesystem)
4GB /var/log/journal (since 13.2, because the journal sucks on rotating rust)

So the errors I see:
Nov  9 21:56:31 server kernel: NMI watchdog: BUG: soft lockup - CPU#0 stuck for
23s! [bcache_gc:944]
Nov  9 21:56:31 server kernel: Modules linked in: binfmt_misc tcp_diag
inet_diag tun nfsd auth_rpcgss oid_registry nfs_acl lockd sunrpc iscsi_ibft
iscsi_bo
ot_sysfs af_packet w83627ehf hwmon_vid ts2020 ds3000 bcache coretemp gpio_ich
pl2303 iTCO_wdt usbserial kvm_intel dvb_usb_dw2102 kvm xfs iTCO_vendor_suppor
t dvb_usb libcrc32c serio_raw i2c_i801 pcspkr sky2 lpc_ich mfd_core shpchp
acpi_cpufreq button ppdev hid_generic ehci_pci uhci_hcd ehci_hcd sr_mod cdrom
us
bhid usbcore usb_common parport_serial parport_pc parport edd fan ata_piix
ata_generic pata_jmicron sg fuse thermal processor dm_mirror dm_region_hash
dm_l
og dm_mod stv0299 budget_ci rc_core budget_core ttpci_eeprom saa7146 dvb_core
bridge stp llc
Nov  9 21:56:31 server kernel: CPU: 0 PID: 944 Comm: bcache_gc Tainted: G
 W      3.17.2-3.gbf63174-default #1
Nov  9 21:56:31 server kernel: Hardware name: .   .  /IP35-E(Intel P35+ICH9R),
BIOS 6.00 PG 05/30/2008
Nov  9 21:56:31 server kernel: task: ffff8800daeca650 ti: ffff8800d7528000
task.ti: ffff8800d7528000
Nov  9 21:56:31 server kernel: RIP: 0010:[<ffffffffa03c86fd>]
[<ffffffffa03c86fd>] bch_btree_iter_next_filter+0x2dd/0x350 [bcache]
Nov  9 21:56:31 server kernel: RSP: 0018:ffff8800d752bc40  EFLAGS: 00000282
Nov  9 21:56:31 server kernel: RAX: 0000000000000005 RBX: ffff880200000001 RCX:
0000000000000002
Nov  9 21:56:31 server kernel: RDX: 0000000000000001 RSI: ffff88020ea21020 RDI:
0000000000000005
Nov  9 21:56:31 server kernel: RBP: ffff8800d752bc70 R08: ffff8800d752bca0 R09:
ffff8800d752bc90
Nov  9 21:56:31 server kernel: R10: ffffffffffee89f8 R11: 0000000000000000 R12:
ffff8800d752be38
Nov  9 21:56:31 server kernel: R13: ffffffffa03d0dc5 R14: ffff8800dbb40000 R15:
ffff88020ea114e0
Nov  9 21:56:31 server kernel: FS:  0000000000000000(0000)
GS:ffff88021fc00000(0000) knlGS:0000000000000000
Nov  9 21:56:31 server kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
000000008005003b
Nov  9 21:56:31 server kernel: CR2: 00007fc9cba2a000 CR3: 00000000d60b9000 CR4:
00000000000007f0
Nov  9 21:56:31 server kernel: Stack:
Nov  9 21:56:31 server kernel:  ffff880213cea4d0 000000000000229b
ffff8800d752be38 ffff8800d752bde0
Nov  9 21:56:31 server kernel:  ffff8800daecc8d0 ffff8800d752bfd8
ffff880213cea4d0 ffffffffa03c8e98
Nov  9 21:56:31 server kernel:  0000000000000004 0000000000000003
ffff88020ea11510 ffff88020ea20870
Nov  9 21:56:31 server kernel: Call Trace:
Nov  9 21:56:31 server kernel:  [<ffffffffa03c8e98>]
btree_gc_count_keys+0x48/0x60 [bcache]
Nov  9 21:56:31 server kernel:  [<ffffffffa03cde4d>]
btree_gc_recurse+0x19d/0x300 [bcache]
Nov  9 21:56:31 server kernel:  [<ffffffffa03ce527>] bch_btree_gc+0x3d7/0x560
[bcache]
Nov  9 21:56:31 server kernel:  [<ffffffffa03ce6e8>] bch_gc_thread+0x38/0x120
[bcache]
Nov  9 21:56:31 server kernel:  [<ffffffff81078a4d>] kthread+0xbd/0xe0
Nov  9 21:56:31 server kernel:  [<ffffffff815e14bc>] ret_from_fork+0x7c/0xb0
Nov  9 21:56:31 server kernel: Code: 06 49 8b 3e 25 ff ff 0f 00 81 e7 ff ff 0f
00 48 39 f8 75 3a 4c 8b 56 08 4d 2b 56 08 4d 85 d2 48 0f 4e f8 49 0f 4f f6 4d
0f 4e c7 <48> 0f 4e ca e9 34 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 45 31
Nov  9 21:56:55 server kernel: NMI watchdog: BUG: soft lockup - CPU#0 stuck for
21s! [bcache_gc:944]
Nov  9 21:56:55 server kernel: Modules linked in: binfmt_misc tcp_diag
inet_diag tun nfsd auth_rpcgss oid_registry nfs_acl lockd sunrpc iscsi_ibft
iscsi_boot_sysfs af_packet w83627ehf hwmon_vid ts2020 ds3000 bcache coretemp
gpio_ich pl2303 iTCO_wdt usbserial kvm_intel dvb_usb_dw2102 kvm xfs
iTCO_vendor_support dvb_usb libcrc32c serio_raw i2c_i801 pcspkr sky2 lpc_ich
mfd_core shpchp acpi_cpufreq button ppdev hid_generic ehci_pci uhci_hcd
ehci_hcd sr_mod cdrom usbhid usbcore usb_common parport_serial parport_pc
parport edd fan ata_piix ata_generic pata_jmicron sg fuse thermal processor
dm_mirror dm_region_hash dm_log dm_mod stv0299 budget_ci rc_core budget_core
ttpci_eeprom saa7146 dvb_core bridge stp llc
Nov  9 21:56:55 server kernel: CPU: 0 PID: 944 Comm: bcache_gc Tainted: G
 W    L 3.17.2-3.gbf63174-default #1
Nov  9 21:56:55 server kernel: Hardware name: .   .  /IP35-E(Intel P35+ICH9R),
BIOS 6.00 PG 05/30/2008
Nov  9 21:56:55 server kernel: task: ffff8800daeca650 ti: ffff8800d7528000
task.ti: ffff8800d7528000
Nov  9 21:56:55 server kernel: RIP: 0010:[<ffffffffa03d0ee5>]
[<ffffffffa03d0ee5>] bch_extent_bad+0xf5/0x1b0 [bcache]
Nov  9 21:56:55 server kernel: RSP: 0018:ffff8800d752bc20  EFLAGS: 00000202
Nov  9 21:56:55 server kernel: RAX: 0000000000000000 RBX: ffff8800dbb40000 RCX:
000000000000000a
Nov  9 21:56:55 server kernel: RDX: ffffc9001107b000 RSI: 0000000000000004 RDI:
00000001288dd804
Nov  9 21:56:55 server kernel: RBP: ffff88021313a8d0 R08: ffff8800dbb40000 R09:
0000000000000001
Nov  9 21:56:55 server kernel: R10: 0000000000000000 R11: ffff8800dafae000 R12:
ffff8800daecc800
Nov  9 21:56:55 server kernel: R13: 0000000000000018 R14: ffffffffa03cd419 R15:
ffff8800daecc800
Nov  9 21:56:55 server kernel: FS:  0000000000000000(0000)
GS:ffff88021fc00000(0000) knlGS:0000000000000000
Nov  9 21:56:55 server kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
000000008005003b
Nov  9 21:56:55 server kernel: CR2: 00007fc9cba2a000 CR3: 00000001d0ee9000 CR4:
00000000000007f0
Nov  9 21:56:55 server kernel: Stack:
Nov  9 21:56:55 server kernel:  ffff8800d752bc80 ffff8800d752bc70
ffffffffa03c8920 ffffffffa03c85db
Nov  9 21:56:55 server kernel:  ffff88021313a8d0 0000000000002b7a
ffff8800d752be38 ffff8800d752bde0
Nov  9 21:56:55 server kernel:  ffff8800daecc8d0 ffff8800d752bfd8
ffff88021313a8d0 ffffffffa03c8e98
Nov  9 21:56:55 server kernel: Call Trace:
Nov  9 21:56:55 server kernel:  [<ffffffffa03c85db>]
bch_btree_iter_next_filter+0x1bb/0x350 [bcache]
Nov  9 21:56:55 server kernel:  [<ffffffffa03c8e98>]
btree_gc_count_keys+0x48/0x60 [bcache]
Nov  9 21:56:55 server kernel:  [<ffffffffa03cde4d>]
btree_gc_recurse+0x19d/0x300 [bcache]
Nov  9 21:56:55 server kernel:  [<ffffffffa03ce527>] bch_btree_gc+0x3d7/0x560
[bcache]
Nov  9 21:56:55 server kernel:  [<ffffffffa03ce6e8>] bch_gc_thread+0x38/0x120
[bcache]
Nov  9 21:56:55 server kernel:  [<ffffffff81078a4d>] kthread+0xbd/0xe0
Nov  9 21:56:55 server kernel:  [<ffffffff815e14bc>] ret_from_fork+0x7c/0xb0
Nov  9 21:56:55 server kernel: Code: 48 c1 ea 08 81 e6 ff 0f 00 00 4c 21 e2 4d
8b 9c f0 40 0c 00 00 48 d3 ea 48 8d 34 52 49 8b 93 d8 0a 00 00 48 8d 34 b2 0f
b6 76 06 <29> fe 40 80 fe 80 0f 87 7f 00 00 00 40 0f b6 d6 83 fa 60 76 66

(I'll attach /var/log/messages)

After investigating, I found patches on the bcache mailing list, which are not
really upstream yet, probably due to the maintainer being busy.

I applied those 5 patches and with the patched bcache module, no problems have
been observed since 21th of November.

Patch 0-2 look "important", patch 3 and 4 only fix the error path in case the
bcache init fails, which seems to be not that urgent.


--1418826042.16bF0.4446
Date: Wed, 17 Dec 2014 14:20:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 910500
           Summary: mdcheck @ cron errors: /var/lib/mdcheck/.md-check-8965: line 5: none: No such file or directory
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: grantksupport-at-operamail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

on

    uname -a
        Linux lab010.DOMAIN.net 3.18.0-2.g99a9f76-xen #1 SMP Sun Dec 14
10:25:49 UTC 2014 (99a9f76) x86_64 x86_64 x86_64 GNU/Linux
    lsb_release -rd
        Description:    openSUSE 13.2 (Harlequin) (x86_64)
        Release:        13.2
    mdadm --version
        mdadm - v3.3.1 - 5th June 2014

i am getting these email notices from system cron every couple of days

    ...
    From: "(Cron Daemon)" <cron-admin=lab010.DOMAIN.net@DOMAIN.net>
    To: cron-admin=lab010.DOMAIN.net@DOMAIN.net
    Subject: Cron <root@server> source /etc/sysconfig/mdadm; [ -n
"$MDADM_CHECK_DURATION" -a -x /usr/share/mdadm/mdcheck ] &&
/usr/share/mdadm/mdcheck --continue --duration "$MDADM_CHECK_DURATION"
    Content-Type: text/plain; charset=UTF-8
    Auto-Submitted: auto-generated
    Precedence: bulk
    X-Cron-Env: <XDG_SESSION_ID=569>
    X-Cron-Env: <XDG_RUNTIME_DIR=/run/user/0>
    X-Cron-Env: <LANG=POSIX>
    X-Cron-Env: <LC_CTYPE=en_US.UTF-8>
    X-Cron-Env: <PATH=/sbin:/usr/sbin:/bin:/usr/bin>
    X-Cron-Env: <SHELL=/bin/sh>
    X-Cron-Env: <HOME=/root>
    X-Cron-Env: <LOGNAME=root>
    X-Cron-Env: <USER=root>
    ...
    /var/lib/mdcheck/.md-check-8965: line 5: none: No such file or directory
    /var/lib/mdcheck/.md-check-8965: line 5: none: No such file or directory
    /usr/share/mdadm/mdcheck: line 109: echo: write error: Invalid argument

they originate from

    grep -rlni mdcheck /etc/cron*
        /etc/cron.d/mdadm
    cat /etc/cron.d/mdadm
        #
        # cron.d/mdadm - regular redundancy checks
        #

        # Start checking each month early in the morning.
        # Continue each day until all done

        PATH=/sbin:/usr/sbin:/bin:/usr/bin
        0 1 * * 0 root source /etc/sysconfig/mdadm; [ -n
"$MDADM_CHECK_DURATION" -a -x /usr/share/mdadm/mdcheck -a $(date +\%d) -le 7 ]
&& /usr/share/mdadm/mdcheck --duration "$MDADM_CHECK_DURATION"
        0 1 * * 1-6 root source /etc/sysconfig/mdadm; [ -n
"$MDADM_CHECK_DURATION" -a -x /usr/share/mdadm/mdcheck ] &&
/usr/share/mdadm/mdcheck --continue --duration "$MDADM_CHECK_DURATION"

checking

cat /usr/share/mdadm/mdcheck
    ...
    # To support '--continue', arrays are identified by UUID and the
'sync_completed'
    # value is stored  in /var/lib/mdcheck/$UUID
    ...
    sysname() {
        set `ls -lLd $1`
        maj=${5%,}
        min=$6
        readlink -f /sys/dev/block/$maj:$min
    }
    ..
    for dev in /dev/md?*
    do
        [ -e "$dev" ] || continue
        sys=`sysname $dev`
    ...
        echo $start > $fl
109        echo $start > $sys/md/sync_min
        echo check > $sys/md/sync_action
    ...

on my system

    ls -al /var/lib/mdcheck/
        total 16K
        drwxr-xr-x  2 root root 4.0K Dec 17 01:56 ./
        drwxr-xr-x 78 root root 4.0K Dec 15 13:59 ../
        -rw-r--r


--1419018118.07f7611.20123
Date: Fri, 19 Dec 2014 19:41:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 910898
           Summary: seccheck weekly and monthly report mails have no subject in mail header
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: d_werner-at-gmx.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 618054
  --> http://bugzilla.opensuse.org/attachment.cgi?id=618054&action=edit
patch to remove the leading blanks from the here documents in
security-control.sh

The monthly and weekly report mails generated by seccheck contain no subject in
the mail header.

This is caused by whitespace formatting in the here document which generates
the header in security-control.sh, similar to #904544 for the daily reports.

####
Current result:
dirk@linux:~> mail
Heirloom mailx version 12.5 7/5/10.  Type ? for help.
"/var/mail/dirk": 1 message 1 new
>N  1 root@linux-qbcc.si Fri Dec 19 19:49  866/29578
?
####
Desired result:
dirk@linux:~> mail
Heirloom mailx version 12.5 7/5/10.  Type ? for help.
"/var/mail/dirk": 1 message 1 new
>N  1 root@linux-qbcc.si Fri Dec 19 19:57  865/29533 Local Monthly Security for linux: Complete
?
####

The faulty mail looks like this:
From root@linux-qbcc.site  Fri Dec 19 19:49:55 2014
Return-Path: <root@linux-qbcc.site>
X-Original-To: root
Delivered-To: root@linux-qbcc.site
Received: by linux-qbcc.site (Postfix, from userid 0)
<------>id 5358A4071B; Fri, 19 Dec 2014 19:49:55 +0100 (CET)
Message-Id: <20141219184955.5358A4071B@linux-qbcc.site>
Date: Fri, 19 Dec 2014 19:49:55 +0100 (CET)
From: root@linux-qbcc.site (root)
Status: RO

            To: root
            Subject: Local Monthly Security for linux: Complete

            Monthly security check v3.0 by Marc Heuse <marc-at-suse.de>
            This is an automated mail by the seccheck tool. If you want to
disable
this service, set START_SECCHK=no in /etc/sysconfig/seccheck.

DISCLAIMER
...
Please note that these security checks are neither complete nor reliable.
Any attacker with proper experience and root access to your system can
deceive *any* security check!

            Monthly security check v3.0 by Marc Heuse <marc-at-suse.de>

NOTE: have you checked http://www.novell.com/products/security.html for
security updates?!

####
The correct mail looks like this:
From root@linux-qbcc.site  Fri Dec 19 19:57:18 2014
Return-Path: <root@linux-qbcc.site>
X-Original-To: root
Delivered-To: root@linux-qbcc.site
Received: by linux-qbcc.site (Postfix, from userid 0)
        id E7AA24071B; Fri, 19 Dec 2014 19:57:17 +0100 (CET)
To: root@linux-qbcc.site
Subject: Local Monthly Security for linux: Complete
Message-Id: <20141219185717.E7AA24071B@linux-qbcc.site>
Date: Fri, 19 Dec 2014 19:57:17 +0100 (CET)
From: root@linux-qbcc.site (root)
Status: RO

Monthly security check v3.0 by Marc Heuse <marc-at-suse.de>
This is an automated mail by the seccheck tool. If you want to disable
this service, set START_SECCHK=no in /etc/sysconfig/seccheck.

DISCLAIMER

Please note that these security checks are neither complete nor reliable.
Any attacker with proper experience and root access to your system can
deceive *any* security check!

Monthly security check v3.0 by Marc Heuse <marc-at-suse.de>

NOTE: have you checked http://www.novell.com/products/security.html for
security updates?!

####
The difference is just the whitespace.

The attached patch removes the blanks at the line begin of the here-documents
for the weekly and monthly reports from security-control.sh and results in
correct mails.

Sorry for raising this just after the update for 904544 is pushed, but the
weekly and monthly reports do not come so often.


--1419020643.db0a30.3313
Date: Fri, 19 Dec 2014 20:24:03 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 910900
           Summary: Espeak-gui does not use selected language to speech
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: opensuse.lietuviu.kalba-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Espeak-gui 0.4 seems to work correctly only with few languages, thought it try
to automaticaaly detect all espeak provided languages.

try execute in terminal and compare:

espeak -v lt "labas rytas"
espeak -v lv "labas rytas"
espeak -v en "labas rytas"

You will here difference!

Now open espeak-gui and try to say the same:
labas rytas

by selecting English, Lithuanian or Latvian language. No difference...


body:
--1419125291.aCe10.3025
Date: Sun, 21 Dec 2014 01:28:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 910933
           Summary: Canna can not start
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: bkbin005-at-rinku.zaq.ne.jp
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I installed canna-devel in openSUSE 13.2.
But I can not start Canna.

Steps to Reproduce:

1) install openSUSE 13.2
2) sudo zypper install canna-devel
3) sudo systemctl status canna.service

Actual Results:

mitsutoshi@linux-rvvx:~> sudo systemctl start canna.service
root's password:
Job for canna.service failed. See "systemctl status canna.service" and
"journalctl -xn" for details.

mitsutoshi@linux-rvvx:~> sudo systemctl status canna.service
canna.service - Canna Japanese Conversion Engine
   Loaded: loaded (/usr/lib/systemd/system/canna.service; disabled)
   Active: failed (Result: exit-code) since Sun 2014-12-21 09:57:54 JST; 32s
ago
  Process: 6362 ExecStart=/usr/sbin/cannaserver -syslog (code=exited,
status=1/FAILURE)

Dec 21 09:57:54 linux-rvvx cannaserver[6362]: /usr/sbin/cannaserver: invalid
option

summary: Canna can not start


--1419235708.50400.23455
Date: Mon, 22 Dec 2014 08:08:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 910983
           Summary: Internal speaker does not work on Thinkpad T410s
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: uli.2001-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I have recently updated from 13.1 to 13.2. Since the update, the internal
speaker of my Thinkpad T410s laptop does not work reliably. After reboot, it
seems to work, but it seems that at some point after going into standby and/or
using headphones, the speakers do not work any longer.

On the other hand, sound via headphones always works.

I am using KDE, apparently with the GStreamer backend.

Previously, on 13.1, going back and forth between speakers and headphones, with
standby in between, always seemed to work (except that sometimes the red light
on the "mute" button of my Thinkpad showed the wrong state).


--1419243391.65AE10.31625
Date: Mon, 22 Dec 2014 10:16:31 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911001
           Summary: dnsmasq apparmor profile prevents libvirt default network to start
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201412*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: cbosdonnat-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

This commit in libvirt forces dnsmasq to actually use the leaseshelper program:
http://libvirt.org/git/?p=libvirt.git;a=commit;h=421406808abaf7eb66abd27d71c21ae5b783a380

The problem is that the dnsmasq apparmor profile prevents the libvirt default
network to start due to:
  * Not allowing /bin/bash to be run
  * Not allowing leaseshealper contained in /usr/lib64 folder to be run.

Note that this bug may hit 13.2 if an updated libvirt is shipped there.


--1419389837.c253bd9.28185
Date: Wed, 24 Dec 2014 02:57:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911205
           Summary: Do not start susegreeter on none KDE desktops.
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201412*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE4 Workspace
          Assignee: kde-maintainers-at-suse.de
          Reporter: mrueckert-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

/etc/xdg/autostart/SUSEgreeter.desktop is a bad place for this file. this makes
it start in gnome e.g. every single time. it doesnt even remember that i closed
it already. this is highly annoying.

please consider moving it to a kde specific autostart directory.


body:
--1419600886.6CbFF20.20181
Date: Fri, 26 Dec 2014 13:34:46 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911298
           Summary: Typo in German translation of 'sudo'
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: bjoernv-at-arcor.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 618420
  --> http://bugzilla.suse.com/attachment.cgi?id=618420&action=edit
Patch for German translation in sudo-1.8.10p3

There is a little typo in German translation of the 'sudo' package. You see
this typo, if you start 'sudo' first time. The typo is already fixed upstream.

Affected version: sudo-1.8.10p3 (and probably lower)
Fixed version: sudo-1.8.10p3

A patch is attached.

summary: Typo in German translation of 'sudo'


--1419651653.bE8a0.10074
Date: Sat, 27 Dec 2014 03:40:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911300
           Summary: xf86-video-openchrome driver crashes X11; framebuffer driver works only provides very low resolution.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: X.Org
          Assignee: bnc-team-xorg-bugs-at-forge.provo.novell.com
          Reporter: psmithw-at-hotmail.com
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

Hardware IDs for the VX900 chip on this motherboard are not specified in the
driver, I found a debian patch description for the exact **same set of errors**
on the exact **same hardware** here:
https://lists.debian.org/debian-x/2014/12/msg00022.html
(this page includes an error log very similar to mine)

This motherboard does not have a PCIe slot, so just swapping to a more standard
video card is not an option for me.  At the moment, the web site hosting their
source code seems to be defunct, so I could not conveniently attempt a local
build.


--1419708101.CBaEc8a0.553
Date: Sat, 27 Dec 2014 19:21:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911303
           Summary: libffado2 puts it's udev - rule into the wrong directory
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: dieter.jurzitza@t-online.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

By accident I found out that for both openSUSE 13.1 and openSUSE 13.2 the
library libffado2 puts it's udev - rule

60-ffado.rules

into /usr/lib/udev/60-ffado.rules

rather than

/usr/lib/udev/rules.d/60-ffado.rules

I'd consider this a bug the severity of which I cannot judge as I do not know
what this library is good for.


--1419782921.DBfE5d0.31043
Date: Sun, 28 Dec 2014 16:08:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911310
           Summary: /usr/bin/logger (util-linux-systemd) not prerequired
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: wicked-maintainers-at-suse.de
          Reporter: lmuelle-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: No

While zypper dup from openSUSE 13.1 to 13.2 I've seen:

( 878/3412) Installation von: wicked-service-0.6.12-1.1
......................................................................................................[fertig]
Zus�tzliche rpm-Ausgabe:
Network is managed by NetworkManager.service
 and rcnetwork does not support '' action.
scripts/functions.common: line 138: logger: command not found
Use systemctl for systemd specific actions.
scripts/functions.common: line 138: logger: command not found

I guess that's caused by a missing prereq statement in the wicked-service
package.


--1419806615.1D8AF50.6639
Date: Sun, 28 Dec 2014 22:43:35 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911315
           Summary: Specifying 'Access Point' under YaST Wireless Expert Settings and Network Settings Global Option Network Setup Method 'Wicked Service' yields 'changeDevice() failed'
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: mrviridis-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Configuring Edimax Wifi USB Stick for home network fails after upgrade to
OpenSUSE 13.2. Newly specifying WLAN setting under YaST made me locate the
critical network option in YaST: Specification of field 'Access Point' under
YaST Wireless Expert Settings in combination with Network Settings > Global
Options > Network Setup Method 'Wicked Service' yields an error 'changeDevice()
failed'.

Hardware is
> linux:/etc/sysconfig/network # lsusb
> Bus 001 Device 002: ID 7392:7711 Edimax Technology Co., Ltd EW-7711UTn
> nLite Wireless Adapter [Ralink RT2870]

Device is automatically recognized at boot up and an network error is
displayed. The file '/var/log/messages' shows:
> 2014-12-28T22:49:48.074468+01:00 linux wickedd[7146]: ni_wpa_network_set
> failed: fi.epitest.hostap.WPASupplicant.InvalidOptions (Did not receive
> correct message arguments.)
> 2014-12-28T22:49:48.075229+01:00 linux wicked[8032]: device wlp0s2f1u1
> failed: call to org.opensuse.Network.Wireless.changeDevice() failed:
> General failure
> 2014-12-28T22:49:48.079051+01:00 linux wicked[8032]: wlp0s2f1u1
>       device-ready
2014-12-28T22:49:48.079374+01:00 linux wicked[8032]: wlp0s2f1u1
>       device-not-running

while the user gets the following message manually restarting network service:
> linux:/etc/sysconfig/network # systemctl restart wickedd
> linux:/etc/sysconfig/network # wicked ifup all
> wicked: device wlp0s2f1u1 failed: call to
> org.opensuse.Network.Wireless.changeDevice() failed: General failure
> lo              up
> wlp0s2f1u1      device-not-running

The error disappears transitioning from config ifcfg-wlp0s2f1u1.old to
ifcfg-wlp0s2f1u1:
> linux:/etc/sysconfig/network # diff ifcfg-wlp0s2f1u1 ifcfg-wlp0s2f1u1.old
> 12c12
> < WIRELESS_AP=''
> ---
> > WIRELESS_AP='9C:C7:A6:39:62:4B'

System is
> linux:/etc/sysconfig/network # uname -a
> Linux linux-to84 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44
> UTC 2014 (762f27a) x86_64 x86_64 x86_64 GNU/Linux
> linux:/etc/sysconfig/network # cat /etc/issue
> Welcome to openSUSE 13.2 "Harlequin" - Kernel \r (\l).


body:
--1419886936.2DEa4780.16814
Date: Mon, 29 Dec 2014 21:02:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911355
           Summary: Job for spamd.service failed
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: stephan.barth-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After the upgrade from 12.3 I found out that spmad was not running anymore.
When trying to start it manually I get:

# /etc/init.d/spamd restart
redirecting to systemctl restart spamd.service
Job for spamd.service failed. See "systemctl status spamd.service" and
"journalctl -xn" for details.

Running the latter command yields:

Dec 29 16:40:11 linux-wulv echo[6901]: Starting spamd:
Dec 29 16:40:11 linux-wulv spamd[6903]: logger: removing stderr method
Dec 29 16:40:11 linux-wulv spamd[6905]: config: no rules were found! Do you
need to run 'sa-update'?
Dec 29 16:40:12 linux-wulv spamd[6903]: child process [6905] exited or timed
out without signaling production of a PID file: exit 255 at /us
Dec 29 16:40:12 linux-wulv spamd[6903]: child process [6905] exited or timed
out without signaling production of a PID file: exit 255 at /us
Dec 29 16:40:12 linux-wulv systemd[1]: Failed to start Daemonized version of
spamassassin.

summary: Job for spamd.service failed


body:
--1420213413.aCAcCB0.2059
Date: Fri, 2 Jan 2015 15:43:33 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911562
           Summary: wicked does not activate interfaces
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: jengelh-at-inai.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

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

This wicked wicked daemon is messed up, and I have NO idea why, because it
outputs so LITTLE information. Manually calling ifup starts the interface, but
WHY can it not already do that at boot? This is SO stupid.

summary: wicked does not activate interfaces


--1420290627.abcE34B0.23751
Date: Sat, 3 Jan 2015 13:10:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911577
           Summary: xvnc isn`t working course of unresolved symbol in libvnc
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: i686
                OS: openSUSE 13.2
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: X.Org
          Assignee: bnc-team-xorg-bugs-at-forge.provo.novell.com
          Reporter: n.moendjen-at-vodafone.de
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

[    13.954] (II) LoadModule: "vnc"
[    13.955] (II) Loading /usr/lib/xorg/modules/extensions/libvnc.so
[    14.015] (EE) Failed to load /usr/lib/xorg/modules/extensions/libvnc.so:
/usr/lib/xorg/modules/extensions/libvnc.so: undefined symbol: _Z13
getvnchomedirPPc
[    14.015] (II) UnloadModule: "vnc"
[    14.015] (II) Unloading vnc
[    14.015] (EE) Failed to load module "vnc" (loader failed, 7)

Linux linux-lbi6 3.16.7-7-default #1 SMP Wed Dec 17 18:00:44 UTC 2014 (762f27a)
i686 i686 i386 GNU/Linux


--1420317740.dDA37861.1854
Date: Sat, 3 Jan 2015 20:42:20 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911588
           Summary: microcode updater and microcode updates are not installed for Intel Core i7
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Installation
          Assignee: yast2-maintainers-at-suse.de
          Reporter: Ulrich.Windl-at-rz.uni-regensburg.de
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

See https://bugzilla.opensuse.org/show_bug.cgi?id=911358#c5
There are microcode bugs for (e.g.) Intel Core I7 4th generation, but no
microcode updates/updater are installed by default (Maybe it's just when you
are offline during installation).
Even when I have installed the latest BIOS (Asus Z87-C, BIOS "2103" from
"08/15/2014"), the microcode was not new enough (microcode 0x19, see
https://bugzilla.opensuse.org/show_bug.cgi?id=911358#c4) for stable operation.


--1420388831.1FfEDbDe0.29739
Date: Sun, 4 Jan 2015 16:27:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911615
           Summary: after boot, volume of 'speaker' is set to zero
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: jnelson-suse-at-jamponi.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 618579
  --> http://bugzilla.opensuse.org/attachment.cgi?id=618579&action=edit
alsa-info.sh output

Hardware: thinkpad B570 (but this also happens on my ThinkPad T520)
Observation: after every boot, I have to go into 'alsamixer', use F6 to choose
the 'HDA Intel PCH', select the 'speaker' item and increase the volume from
zero back up to normal.

Also, sometimes it thinks headphones are plugged in and they most assuredly are
not.


--1420462998.0d13B72.11704
Date: Mon, 5 Jan 2015 13:03:18 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911683
           Summary: xterm no longer understands font related options
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201412*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: idonmez-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

[~]> /usr/bin/xterm -uc -fa "Consolas" -fs 13 -rightbar -geometry 128x55+70+41
/usr/bin/xterm: bad command line option "-fa"

[~]> /usr/bin/xterm -uc -fs 13 -rightbar -geometry 128x55+70+41
/usr/bin/xterm: bad command line option "-fs"

and so on. Seems to broken due to changes done on Dec. 19 2014.


body:
Build Identifier:

I am using an automounter map that is intended to mount devices based on blkid
information such as a file system label. It is able to mount ext2/3/4 and ntfs
devices. As the latest autofs versions use the "-s" argument for mount,
mounting my ntfs disk is no longer working.

Reproducible: Always

Steps to Reproduce:
1. Create an ntfs disk, and a respective autofs entry
2. Try to cd into the respective dir

Actual Results:
automounted dir is not available, autofs output (if foreground, verbose, debug
flags are used) includes the following info (my ntfs disk is named
"datenhafen3"):
[...]
mount_mount: mount(generic): calling mount -t ntfs -s -o
rw,allow_other,nonempty,relatime,blkdev /dev/sdf1 /by-label/datenhafen3
spawn_mount: mtab link detected, passing -n to mount
>> ntfs-3g: Unknown option '-s'.
>> ntfs-3g 2014.2.15 external FUSE 29 - Third Generation NTFS Driver
[...]

I understand that the sloppy flag is there for a reason. Adding the
"--disable-sloppy-mount" configure option drops the flag, and results in a
working autofs daemon in my scenario.

Possibly an additional flag for autofs maps is required?

summary: autofs usage of sloppy argument breaks ntfs mounts (others?)


body:
--1420499586.4Ce6a0.2155
Date: Mon, 5 Jan 2015 23:13:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911756
           Summary: calibre conflicts with liberation-fonts
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201412*
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: tuliom-at-quites.com.br
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

While trying to update calibre-2.13.0-1.1.x86_64 to calibre-2.15.0-1.1.x86_64,
I've got the following conflict messages with
liberation-fonts-1.07.3-3.1.noarch (provided by Tumbleweed's oss repository):

Checking for file conflicts:
.....................................................................[error]
Detected 12 file conflicts:

File /usr/share/calibre/fonts/liberation/LiberationMono-Bold.ttf
  from install of
     calibre-2.15.0-1.1.x86_64(repo-oss)
  conflicts with file
     /usr/share/fonts/truetype/LiberationMono-Bold.ttf
  from package
     liberation-fonts-1.07.3-3.1.noarch(@System)

File /usr/share/calibre/fonts/liberation/LiberationMono-BoldItalic.ttf
  from install of
     calibre-2.15.0-1.1.x86_64(repo-oss)
  conflicts with file
     /usr/share/fonts/truetype/LiberationMono-BoldItalic.ttf
  from package
     liberation-fonts-1.07.3-3.1.noarch(@System)

File /usr/share/calibre/fonts/liberation/LiberationMono-Italic.ttf
  from install of
     calibre-2.15.0-1.1.x86_64(repo-oss)
  conflicts with file
     /usr/share/fonts/truetype/LiberationMono-Italic.ttf
  from package
     liberation-fonts-1.07.3-3.1.noarch(@System)

File /usr/share/calibre/fonts/liberation/LiberationMono-Regular.ttf
  from install of
     calibre-2.15.0-1.1.x86_64(repo-oss)
  conflicts with file
     /usr/share/fonts/truetype/LiberationMono-Regular.ttf
  from package
     liberation-fonts-1.07.3-3.1.noarch(@System)

File /usr/share/calibre/fonts/liberation/LiberationSans-Bold.ttf
  from install of
     calibre-2.15.0-1.1.x86_64(repo-oss)
  conflicts with file
     /usr/share/fonts/truetype/LiberationSans-Bold.ttf
  from package
     liberation-fonts-1.07.3-3.1.noarch(@System)

File /usr/share/calibre/fonts/liberation/LiberationSans-BoldItalic.ttf
  from install of
     calibre-2.15.0-1.1.x86_64(repo-oss)
  conflicts with file
     /usr/share/fonts/truetype/LiberationSans-BoldItalic.ttf
  from package
     liberation-fonts-1.07.3-3.1.noarch(@System)

File /usr/share/calibre/fonts/liberation/LiberationSans-Italic.ttf
  from install of
     calibre-2.15.0-1.1.x86_64(repo-oss)
  conflicts with file
     /usr/share/fonts/truetype/LiberationSans-Italic.ttf
  from package
     liberation-fonts-1.07.3-3.1.noarch(@System)

File /usr/share/calibre/fonts/liberation/LiberationSans-Regular.ttf
  from install of
     calibre-2.15.0-1.1.x86_64(repo-oss)
  conflicts with file
     /usr/share/fonts/truetype/LiberationSans-Regular.ttf
  from package
     liberation-fonts-1.07.3-3.1.noarch(@System)

File /usr/share/calibre/fonts/liberation/LiberationSerif-Bold.ttf
  from install of
     calibre-2.15.0-1.1.x86_64(repo-oss)
  conflicts with file
     /usr/share/fonts/truetype/LiberationSerif-Bold.ttf
  from package
     liberation-fonts-1.07.3-3.1.noarch(@System)

File /usr/share/calibre/fonts/liberation/LiberationSerif-BoldItalic.ttf
  from install of
     calibre-2.15.0-1.1.x86_64(repo-oss)
  conflicts with file
     /usr/share/fonts/truetype/LiberationSerif-BoldItalic.ttf
  from package
     liberation-fonts-1.07.3-3.1.noarch(@System)

File /usr/share/calibre/fonts/liberation/LiberationSerif-Italic.ttf
  from install of
     calibre-2.15.0-1.1.x86_64(repo-oss)
  conflicts with file
     /usr/share/fonts/truetype/LiberationSerif-Italic.ttf
  from package
     liberation-fonts-1.07.3-3.1.noarch(@System)

File /usr/share/calibre/fonts/liberation/LiberationSerif-Regular.ttf
  from install of
     calibre-2.15.0-1.1.x86_64(repo-oss)
  conflicts with file
     /usr/share/fonts/truetype/LiberationSerif-Regular.ttf
  from package
     liberation-fonts-1.07.3-3.1.noarch(@System)

summary: calibre conflicts with liberation-fonts


--1420538737.EFe35.14368
Date: Tue, 6 Jan 2015 10:05:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911806
           Summary: config.postfix does not set up correct saslauthd socket directory for chroot
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: jreuter-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: bwiedemann-at-suse.com, d.kuhn@heinlein-support.de,
                    michael-at-stroeder.com
        Depends on: 910265
          Found By: ---
           Blocker: ---

As a spin-off of bsc#910265:

/usr/sbin/config.postfix still copies the deprecated /var/run contents into the
chroot:

SASL_SOCKET_DIR="/var/run/sasl2"
CHR_SASL_SOCKET_DIR="var/run/sasl2"

However the saslauthd library is looking for its socket in /run/sasl2/:

socket(PF_LOCAL, SOCK_STREAM, 0)        = 44
connect(44, {sa_family=AF_LOCAL, sun_path="/run/sasl2//mux"}, 110) = -1 ENOENT
 (No such file or directory)

which obviously won't work if smtpd is run chroot'ed:

Jan  6 09:38:09 martes postfix/smtpd[20262]: warning: SASL authentication
failure: cannot connect to saslauthd server: No such file or directory
Jan  6 09:38:09 martes postfix/smtpd[20262]: warning:
p5791BDD0.dip0.t-ipconnect.de[87.145.189.208]: SASL PLAIN authentication
failed: generic failure

Please note that there are multiple other references to /var/run left in
config.postfix that need to be fixed.


--1420556238.85aC0.22044
Date: Tue, 6 Jan 2015 14:57:18 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911871
           Summary: outdated drbd 8.3. tools package  does not work with the 13.2 kernel
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: High Availability
          Assignee: lmb-at-suse.com
          Reporter: kkeil-at-novell.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

uname -a
Linux pingi7 3.16.7-7-default #1 SMP Wed Dec 17 18:00:44 UTC 2014 (762f27a)
x86_64 x86_64 x86_64 GNU/Linux

pingi7:~ # drbdadm help
DRBD module version: 8.4.3
   userland version: 8.3.11
you should upgrade your drbd tools!

First I was thinking this is only a hint, but with this version I could not
connect to any other drbd instance in my network. The drbdsetup always run into
a timeout.

With a self build of drbd-8.4.3 tools package everything is working again, so
please update the drbd tools to a version which is compatible with the newer
kernel versions.


body:
--1420612579.f65BdC271.1984
Date: Wed, 7 Jan 2015 06:36:19 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 911986
           Summary: yast2-nfs-client with nfs-client 1.3.1
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201412*
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: mlin-at-suse.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

nfs-utils(nfs-client) 1.3.1 on its way to Staging Project
https://build.opensuse.org/request/show/265210, however in yast2-nfs-client we
had the specific nfs-client version requirement and the comment as below,

# yast2-nfs-client depends on nfs-utils in term that edits nfs-utils' options.
# Support was checked against nfs-utils 1.2.7.
# As soon as nfs-utils reaches version 1.2.9 there should be another update.
# FIXME: 1.3.0 works but adds these new options we need to handle:
# - multiple "sec" with colons
# - "migration"
# - "v4.1" v4.x
BuildRequires:  nfs-client < 1.3.1

therefore, new nfs-utils can not get into Factory, so the question is, is it
possible yast2-nfs-client can support nfs-client 1.3.1?

summary: yast2-nfs-client with nfs-client 1.3.1


--1420680978.474CB833.9528
Date: Thu, 8 Jan 2015 01:36:18 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912170
           Summary: Boot fails with BTRFS RAID1 array as /home - open ctree failed
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: 64bit
                OS: openSUSE 13.2
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: RyanSKingsbury-at-alumni.utexas.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I recently did a clean install of OpenSUSE 13.2 into a system with three drives
- 1 SSD containing the / partition (btrfs format with default subvolumes), and
2 identical HDD's containing /home in an encrypted BTRFS RAID1 array.
Initially, I was using only one of the HDD's as /home (still encrypted BTRFS).
Once I added the second drive and started the RAID1 mirroring, my system will
no longer boot without manual intervention. I get dropped into "emergency
mode", but then all I have to do is exit (Ctrl+D) to continue booting and
everything works normally.

The last entry in the system log before Emergency Mode is invoked is:
Code:

BTRFS: open_ctree failed

It appears that a similar (maybe the same) bug was reported on ArchWiki:
https://wiki.archlinux.org/index.php/Btrfs#BTRFS:_open_ctree_failed

But the solution refers to mkinitcpio rather than dracut that OpenSUSE uses, so
I'm unsure how to apply it to my system.

Some relevant system information:

excerpt from /etc/fstab:
----
# encrypted RAID1 array containing /home
UUID=e91f611f-524a-43f5-bde5-8ebb9672f146 /home btrfs defaults 0 0
----

/etc/crypttab:
----
encrypted-home-sdb UUID=9c8fb7d0-74e2-4e38-b7c7-6211bbb6d2b1 none luks, retry=1
encrypted-home-sdc UUID=b82e5894-cea2-4fe7-a0a5-80f918e9db61 none luks, retry=1
----

excerpt from fdisk -l:
----
Device     Start        End    Sectors   Size Type
/dev/sdb1   2048 1953523711 1953521664 931.5G Microsoft basic data

Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: CAC38602-D5A5-4F28-8344-65B559124514

Device     Start        End    Sectors   Size Type
/dev/sdc1   2048 1953525134 1953523087 931.5G Linux filesystem

Disk /dev/mapper/encrypted-home-sdc: 931.5 GiB, 1000201723392 bytes, 1953518991
sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/encrypted-home-sdb: 931.5 GiB, 1000200994816 bytes, 1953517568
sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
----

Device UUID's:
----
/dev/sda1: UUID="04e20317-f554-43cf-a95d-b0385ebd22bb"
UUID_SUB="cb9dc431-1855-466b-ae9a-5c0ddcd7f95a" TYPE="btrfs" PTTYPE="dos"
PARTLABEL="primary" PARTUUID="860c637a-83c8-4399-8dc4-5b5ab66c0f06"
/dev/sdb1: UUID="9c8fb7d0-74e2-4e38-b7c7-6211bbb6d2b1" TYPE="crypto_LUKS"
PARTLABEL="primary" PARTUUID="532a7bd2-6774-422e-90c0-31f19796098d"
/dev/sdc1: UUID="1ca9d3ba-c409-4127-91f5-e3d9c21242bd" TYPE="crypto_LUKS"
PARTLABEL="Linux filesystem" PARTUUID="5a6830cc-9064-476c-aa79-6189dd0964bd"
/dev/mapper/encrypted-home-sdc: UUID="e91f611f-524a-43f5-bde5-8ebb9672f146"
UUID_SUB="6007c4c7-5119-4b0f-ab21-134832c4774c" TYPE="btrfs"
/dev/mapper/encrypted-home-sdb: UUID="e91f611f-524a-43f5-bde5-8ebb9672f146"
UUID_SUB="020bae26-b64f-413e-8263-a6e832ccb224" TYPE="btrfs"
----


body:
--1420716662.35C6c0.32192
Date: Thu, 8 Jan 2015 11:31:02 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912229
           Summary: scary fsck output
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: mrmazda-at-earthlink.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Mailing list thread instigator:
http://lists.opensuse.org/opensuse-factory/2015-01/msg00113.html

13.2/3.16.7
# e2fsck /dev/sdb2
e2fsck 1.42.12 (29-Aug-2014)
ST32000542ASp1: clean, 334/61054976 files, 210156348/244189440 blocks
Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
e2fsck[0x427fd1]
/lib64/libc.so.6(+0x35200)[0x7f0ef74cc200]
/lib64/libext2fs.so.2(ext2fs_free_dblist+0xd)[0x7f0ef80ac6fd]
e2fsck(e2fsck_reset_context+0xf8)[0x40e9e8]
e2fsck(e2fsck_free_context+0x16)[0x40ec66]
e2fsck(main+0x2600)[0x40c870]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f0ef74b8b05]
e2fsck[0x40cc8f]

TW/3.18.1
# e2fsck /dev/sdb2
e2fsck 1.42.12 (29-Aug-2014)
e2fsck: need terminal for interactive repairs

Same system, same disk, 13.1 behaves in tradition, all OK.

That was yesterday, here's now:
#13.3/TW
# zypper install e2fsprogs-debuginfo-1.42.12-1.2.x86_64
Loading repository data...
Reading installed packages...
'e2fsprogs-debuginfo-1.42.12-1.2.x86_64' not found in package names. Trying
capabilities.
No provider of 'e2fsprogs-debuginfo-1.42.12-1.2.x86_64' found. ['--plus-content
debug'?]
Resolving package dependencies...

Nothing to do.

# gdb --args e2fsck /dev/sdb1
GNU gdb (GDB; openSUSE Factory) 7.8.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...

warning: /etc/gdbinit.d/gdb-heap.py: No such file or directory
Reading symbols from e2fsck...(no debugging symbols found)...done.
Missing separate debuginfos, use: zypper install
e2fsprogs-debuginfo-1.42.12-1.2.x86_64
(gdb) r
Starting program: /sbin/e2fsck /dev/sdb1
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
e2fsck 1.42.12 (29-Aug-2014)
AZBOXPREMIUMPLUS has gone 738 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information

AZBOXPREMIUMPLUS: ***** FILE SYSTEM WAS MODIFIED *****
AZBOXPREMIUMPLUS: 660/122101760 files (25.8% non-contiguous),
307151561/488377600 blocks
[Inferior 1 (process 3328) exited with code 01]
(gdb) where
No stack.
(gdb) quit

13.2
# gdb --args e2fsck /dev/sdb2
GNU gdb (GDB; openSUSE 13.2) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...

warning: /etc/gdbinit.d/gdb-heap.py: No such file or directory
Reading symbols from e2fsck...Reading symbols from
/usr/lib/debug/usr/sbin/e2fsck.debug...done.
done.
(gdb) r
Starting program: /sbin/e2fsck /dev/sdb2
Got object file from memory but can't read symbols: File truncated.
Missing separate debuginfos, use: zypper install
glibc-debuginfo-2.19-16.2.5.x86_64
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
e2fsck 1.42.12 (29-Aug-2014)
ST32000542ASp1: clean, 334/61054976 files, 210156348/244189440 blocks

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7bb36fd in ext2fs_free_dblist () from /lib64/libext2fs.so.2
Missing separate debuginfos, use: zypper install
libblkid1-debuginfo-2.25.1-5.1.x86_64 libcom_err2-debuginfo-1.42.12-1.2.x86_64
libext2fs2-debuginfo-1.42.12-1.2.x86_64 libuuid1-debuginfo-2.25.1-5.1.x86_64
(gdb) where
#0  0x00007ffff7bb36fd in ext2fs_free_dblist () from /lib64/libext2fs.so.2
#1  0x000000000040e9e8 in e2fsck_reset_context (ctx=ctx@entry=0x640750) at
e2fsck.c:88
#2  0x000000000040ec66 in e2fsck_free_context (ctx=0x640750) at e2fsck.c:177
#3  0x000000000040c870 in check_if_skip (ctx=0x640750) at unix.c:463
#4  main (argc=<optimized out>, argv=<optimized out>) at unix.c:1594
(gdb) quit
A debugging session is active.

        Inferior 1 [process 1823] will be killed.

Quit anyway? (y or n) y
# dmesg | tail -n22
[   52.760035] ata8: hard resetting link
[   54.350047] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   54.353466] ata8.00: ATA-8: ST2000DL003-9VT166, CC32, max UDMA/133
[   54.353470] ata8.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[   54.359452] ata8.00: configured for UDMA/100
[   54.359461] ata8: EH complete
[   54.359547] scsi 7:0:0:0: Direct-Access     ATA      ST2000DL003-9VT1 CC32
PQ: 0 ANSI: 5
[   54.359805] sd 7:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00
TB/1.81 TiB)
[   54.359872] sd 7:0:0:0: [sdb] Write Protect is off
[   54.359876] sd 7:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[   54.359907] sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[   54.360498] sd 7:0:0:0: Attached scsi generic sg2 type 0
[   54.382987]  sdb: sdb1 sdb2
[   54.383379] sd 7:0:0:0: [sdb] Attached SCSI disk
[   54.638642] EXT4-fs (sdb2): mounting ext2 file system using the ext4
subsystem
[   54.693349] EXT4-fs (sdb2): mounted filesystem without journal. Opts: (null)
[   54.811193] fuse init (API version 7.23)
[   63.197890] Key type dns_resolver registered
[   63.226661] NFS: Registering the id_resolver key type
[   63.226677] Key type id_resolver registered
[   63.226678] Key type id_legacy registered
[  446.900338] snd_hda_intel 0000:00:1b.0: IRQ timing workaround is activated
for card #0. Suggest a bigger bdl_pos_adj.

summary: scary fsck output


--1420728325.ebE1Fd1.26561
Date: Thu, 8 Jan 2015 14:45:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912279
           Summary: Changing font preferences of serif, sans, and monospace needs manually running fonts-config
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: cornelis-at-solcon.nl
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

I used Yast to change the preferred fonts for serif, sans, and monospace, but
nothing happened. It took me some time to discover that I needed to run
fonts-config manually. Shoudln't Yast do this automatically after these values
are changed? Now users think this is not working (it is what I initially
thought).


body:
--1420732837.cAcf0.850
Date: Thu, 8 Jan 2015 16:00:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912298
           Summary: make gcc build PIE binaries by default
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201412*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: meissner-at-suse.com
          Reporter: meissner-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: rguenther-at-suse.com
          Found By: ---
           Blocker: ---

we should integrate the Gentoo solution of building PIE binaries,
namely having this as option in gcc.

richi found the patch submission:
https://gcc.gnu.org/ml/gcc-patches/2014-11/msg00861.html

pkgs: gcc rpm

summary: make gcc build PIE binaries by default


--1420739002.eefbC9.13848
Date: Thu, 8 Jan 2015 17:43:22 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912315
           Summary: Networkmanager/dhcpv6 conflict with buggy devices
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: tschaefer@t-online.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The bug 888787  is solved for Opensuse 13.1 but it was made again in 13.2.

It is about removal of:

add_also_request (alsoreq, "dhcp6.server-id");

in

/src/dhcp-manager/nm-dhcp-dhclient-utils.c

In the meantime I have got a further router/device, where this bug is producing
time outs.


--1420749008.3F6f0.27307
Date: Thu, 8 Jan 2015 20:30:08 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912334
           Summary: undue start job delay from nofail fstab entries for unattached/unpowered devices
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201412*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: mrmazda-at-earthlink.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I have in 13.1 3.12.33, 13.2 3.16.7 and TW 3.18.1 installations on the same
machine these identical fstab entries:

#/dev/disk/by-label/RS1933-1109
/dev/disk/by-id/ata-ST2000DL003-9VT166_5YD4SNQ6-part1 /disks/esata    ntfs-3g

noatime,nofail,users,user_id=1050,group_id=1000,fmask=0111,dmask=0000,locale=en_US.UTF-8
   0 0
#/dev/disk/by-label/ST32000542ASp1
/dev/disk/by-id/ata-ST2000DL003-9VT166_5YD4SNQ6-part2 /disks/esata2    ext2
noatime,nofail    0 0

#/dev/disk/by-label/ST2000DM001Z2F0RXAS AZBme Seagate
/dev/disk/by-id/ata-ST2000DM001-1CH164_Z2F0RXAS-part1 /disks/esata2    ext2
noatime,nofail    0 0

#/dev/disk/by-label/WD20EURSAV-GP1208 AZBme WD
/dev/disk/by-id/ata-WDC_WD20EURS-63S48Y0_WD-WCAZAE933621-part1 /disks/esata
ext2    noatime,nofail    0 0

Boot proceeds normally on 13.1 and 13.2. On TW there is substantial delay from
timing out 4 start jobs for the first 2 of these 4 filesystems  when booting
without them attached and powered up:
# journalctl | grep start | grep disk
Jan 08 14:48:12 big41 systemd[1]: Job
dev-disk-by\x2did-ata\x2dST2000DL003\x2d9VT166_5YD4SNQ6\x2dpart2.device/start
timed out.
Jan 08 14:50:38 big41 systemd[1]: Job
dev-disk-by\x2did-ata\x2dST2000DL003\x2d9VT166_5YD4SNQ6\x2dpart1.device/start
timed out.
Jan 08 15:03:00 big41 systemd[1]: Job
dev-disk-by\x2did-ata\x2dST2000DL003\x2d9VT166_5YD4SNQ6\x2dpart2.device/start
timed out.
Jan 08 15:03:00 big41 systemd[1]: Job
dev-disk-by\x2did-ata\x2dST2000DL003\x2d9VT166_5YD4SNQ6\x2dpart1.device/start
timed out.


--1420755684.3E7e0.3651
Date: Thu, 8 Jan 2015 22:21:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912365
           Summary: CVE-2015-0559, CVE-2015-0560: Wireshark: WCCP dissector crash
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: All
               URL: https://www.wireshark.org/security/wnpa-sec-2015-01.ht
                    ml
                OS: openSUSE 13.2
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

https://www.wireshark.org/security/wnpa-sec-2015-01.html

Name: WCCP dissector crash
Docid: wnpa-sec-2015-01
Date: January 7, 2015
Affected versions: 1.12.0 to 1.12.2, 1.10.0 to 1.10.11
Fixed versions: 1.12.3, 1.10.12

(this includes all previous versions)

References:
Wireshark bug 10720
Wireshark bug 10806
CVE-2015-0559
CVE-2015-0560

Description: The WCCP dissector could crash.
Impact:  It may be possible to make Wireshark crash by injecting a malformed
packet onto the wire or by convincing someone to read a malformed packet trace
file.


--1420755867.200036E16.4113
Date: Thu, 8 Jan 2015 22:24:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912368
           Summary: CVE-2015-0561: Wireshark: LPP dissector crash
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: All
               URL: https://www.wireshark.org/security/wnpa-sec-2015-02.ht
                    ml
                OS: openSUSE 13.2
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

From https://www.wireshark.org/security/wnpa-sec-2015-02.html

Name: LPP dissector crash
Docid: wnpa-sec-2015-02
Date: January 7, 2015
Affected versions: 1.12.0 to 1.12.2, 1.10.0 to 1.10.11
( this includes previous versions )
Fixed versions: 1.12.3, 1.10.12

References:
Wireshark bug 10773
CVE-2015-0561

It may be possible to make Wireshark crash by injecting a malformed packet onto
the wire or by convincing someone to read a malformed packet trace file.


--1420756005.6cbf63e50.4510
Date: Thu, 8 Jan 2015 22:26:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912369
           Summary: CVE-2015-0562: Wireshark: DEC DNA Routing Protocol dissector crash
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: All
               URL: https://www.wireshark.org/security/wnpa-sec-2015-03.ht
                    ml
                OS: openSUSE 13.2
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

From https://www.wireshark.org/security/wnpa-sec-2015-03.html

Name: DEC DNA Routing Protocol dissector crash
Docid: wnpa-sec-2015-03
Date: January 7, 2015
Affected versions: 1.12.0 to 1.12.2, 1.10.0 to 1.10.11
( this includes previous discontinued versions)
Fixed versions: 1.12.3, 1.10.12

References:
Wireshark bug 10724
CVE-2015-0562

It may be possible to make Wireshark crash by injecting a malformed packet onto
the wire or by convincing someone to read a malformed packet trace file.


--1420756165.B7A8f2FA18.4510
Date: Thu, 8 Jan 2015 22:29:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912370
           Summary: CVE-2015-0563: Wireshark: SMTP dissector crash
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: All
               URL: https://www.wireshark.org/security/wnpa-sec-2015-04.ht
                    ml
                OS: openSUSE 13.2
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

From https://www.wireshark.org/security/wnpa-sec-2015-04.html

Name: SMTP dissector crash
Docid: wnpa-sec-2015-04
Date: January 7, 2015
Affected versions: 1.12.0 to 1.12.2, 1.10.0 to 1.10.11
( This includes previous versions )
Fixed versions: 1.12.3, 1.10.12

References:
Wireshark bug 10823
CVE-2015-0563

It may be possible to make Wireshark crash by injecting a malformed packet onto
the wire or by convincing someone to read a malformed packet trace file.


--1420756337.44055fc0.4515
Date: Thu, 8 Jan 2015 22:32:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912372
           Summary: CVE-2015-0564: Wireshark: TLS/SSL decryption crash
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: All
               URL: https://www.wireshark.org/security/wnpa-sec-2015-05.ht
                    ml
                OS: openSUSE 13.2
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

From https://www.wireshark.org/security/wnpa-sec-2015-05.html

Name: TLS/SSL decryption crash
Docid: wnpa-sec-2015-05
Date: January 7, 2015
Affected versions: 1.12.0 to 1.12.2, 1.10.0 to 1.10.11
(Includes previous versions)
Fixed versions: 1.12.3, 1.10.12

References:
CVE-2015-0564

Wireshark could underflow a buffer while decypting TLS/SSL sessions.

It may be possible to make Wireshark crash by injecting a malformed packet onto
the wire or by convincing someone to read a malformed packet trace file.


--1420774838.BBE77A0.3800
Date: Fri, 9 Jan 2015 03:40:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912398
           Summary: Asymptote in Texlive uses ghostscript epswrite device which is not present
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: don.raboud-at-ualberta.ca
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

asymptote tries to use ghostscript device "epswrite" but that device is no
longer supported by ghostscript and appears to have been replaced by the
"eps2write" device instead.

"epswrite" appears in the file utils/asymptote/runlabel.cc in the texlive
source rpm while gs --help does not list epswrite as a supported device, but
eps2write is shown as one of the supported devices.

Generating asymptote files containing  3D labels doesn't work, although the
same asymptote file works fine in 12.3 and I suspect this may be the cause.

texlive-2013.20130620-23.1.9.src.rpm
ghostscript-9.15-1.4.x86_64


body:
--1420806458.A1d770.3832
Date: Fri, 9 Jan 2015 12:27:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912460
           Summary: zeromq test_security_plain test fails
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201412*
          Hardware: PowerPC-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: dvaleev-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

zeromq build process hangs on test_security_plain test.

[   40s] PASS: test_ctx_destroy
[   40s] PASS: test_security_null
[   40s] test_security_plain: testutil.hpp:143: void expect_bounce_fail(void*,
void*): Assertion `rc == 32' failed.
[   40s] /bin/sh: line 5: 111819 Aborted                 ${dir}$tst
[   40s] FAIL: test_security_plain

summary: zeromq test_security_plain test fails


--1420840941.4F54D0.21547
Date: Fri, 9 Jan 2015 22:02:21 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 912565
           Summary: After latest upgrade of Tumbleweed I can't log in any more; error Could not sync environment to dbus.
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201412*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: freek-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Late on 2015-01-09 I upgrades Tumbleweed to the newest 20150107 version.
I am using KF5. After reboot I get the log in screen and tried to log in. After
a while I get a small X-Window like window showing the message "Could not sync
environment to dbus." Pressing the OK button brings me back to the log in
screen. <Ctrl><Alt><F1> brings me to tty1 and I can log there.
How to proceed?