body:
--1412451410.aD8A04.11646
Date: Sat, 4 Oct 2014 19:36:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 899756
           Summary: VUL-0: CVE-2014-3683: rsyslog/syslogd: remote syslog PRI vulnerability - incomplete fix for CVE-2014-3634
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201409*
          Hardware: Other
               URL: http://www.rsyslog.com/remote-syslog-pri-vulnerability
                    -cve-2014-3683/
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: Andreas.Stieger-at-gmx.de, meissner-at-suse.com,
                    mt-at-suse.com, schwab-at-suse.com, security-team-at-suse.de,
                    werner-at-suse.com
            Blocks: 897262
          Found By: ---
           Blocker: ---

http://www.rsyslog.com/remote-syslog-pri-vulnerability-cve-2014-3683/

emote syslog PRI vulnerability
===============================

CVE: CVE-2014-3683

See also CVE: CVE-2014-3634

Status of this report
———————
FINAL

Reporter
——-
mancha <mancha1-at-zoho.com>, intial detection and analysis
Rainer Gerhards <rgerhards-at-adiscon.com>, rsyslog project lead

Affected
——–
- rsyslog, most probably all versions (checked v3-stable and above)
- sysklogd (checked most recent versions)

Short Description
—————–
While preparing a fix for CVE-2014-3634 for sysklogd, mancha discovered and
privately reported that the initial rsyslog fix set was incomplete. It did
not cover cases where PRI values > MAX_INT caused integer overflows
resulting in negative values.

Root Cause
———-
A while parsing the syslog message’s PRI value, an integer overlow can
happen (for PRI > MAX_INT), which may cause negative PRI values. The
solutions provided in CVE-2014-3634 do not handle that case.

Effect in Practice
——————

General
~~~~~~~
Almost all distributions do ship rsyslog without remote reception by
default and almost all distros also put firewall rules into place that
prevent reception of syslog messages from remote hosts (even if rsyslog
would be listening). With these defaults, it is impossible to trigger
the vulnerability in v7 and v8. Older versions may still be vulnerable
if a malicious user writes to the local log socket.

Even when configured to receive remote message (on a central server),
it is good practice to protect such syslog servers to accept only
messages from trusted peers, e.g. within the relay chain. If setup in
such a way, a trusted peer must be compromised to send malfromed
messages. This further limits the magnitude of the vulnerability.

If, however, any system is permitted to send data unconditionally to
the syslogd, a remote attack is possible.

sysklogd
~~~~~~~~
A segfault seems possible in sysklogd if a negative facility value (due to
integer overrun in facility parsing) is used. This could be used to
carry out a remote DoS.

rsyslogd
~~~~~~~~
Rsyslogd experiences the same problem as sysklogd.

As in CVE-2014-3634, rsyslog v7 and v8 have an elevated risk due to some
tables lookups used during writing. For details see CVE2014-3634.
Contrary to CVE-2014-3634, rsyslog prior to v6 is also likely to segfault.

Note that a segfault of rsyslog can cause message loss. There are multiple
scenarios for this, but likely ones are:

- reception via UDP, where all messages arriving during downtime are lost
- corruption of disk queue structures, which can lead to loss of all disk
queue contents (manual recovery is possible).

This list does not try to be complete. Note that disk queue corruption is
likely
to occur in default settings, because the important queue information file
(.qi)
is only written on successful shutdown. Without a valid .qi file, queue message
files cannot be processed.

How to Exploit
————–
A syslog message with a PRI > MAX_INT needs to be sent and the resulting
overflow must lead to a negative value. It is usually sufficient
to send just the PRI as in this example

""

Severity
——–
Given the fact that multiple changes must be made to default system
configurations
and potential problems we classify the severity of this vulnerability as

MEDIUM

Note that the probability of a successful attack is on LOW. However, the risk
of
message loss is HIGH in those rare instances where an attack is successful. As
mentioned above, it cannot totally be outruled that remote code injection is
possible using this vulnerability.

Patches
——-

sysklogd
~~~~~~~~
A patch for version 1.5 is available at: from mancha

rsyslog
~~~~~~~
Patches are available for versions known to be in wide-spread use.

Version 8.4.2 is not vulnerable. Version 7.6.7, while no longer being project
supported, received a patch and is also not vulnerable.

Versions 8.4.1 and 7.6.6 do NOT handle integer overflows and resulting negative
PRI values correctly. So upgrading to them is NOT a sufficient solution.

The rsyslog project also provides patches for older versions 5 and 3. This is
purely a convenience to those that still run these very outdated versions.
Note that these patches address the segfault issue. They do NOT offer all
features
of the v7/8 series, as this would require considerate code changes. Most
importantly, the "invld" facility is not available in the v3 patch. Also,
the dead-version patches do not try to assing a specific severity to messages
with invalid PRI values nor do they prevent parsing those messages. In general,
it is suggested to upgrade to the currently supported version 8.4.2.

The patch is available:
http://www.rsyslog.com/files/download/rsyslog/CVE-2014-3683-pri-vuln.tar.gz

Special thanks to mancha for his suggestions on how to fix the problem. The
core idea went into the rsyslog patches.

pkgs: rsyslog syslogd


--1412655283.23de0.3414
Date: Tue, 7 Oct 2014 04:14:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900013
           Summary: Bunch of errors when profiler is opened.
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.2 Beta 1
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: roger.luedecke-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 609133
  --> http://bugzilla.opensuse.org/attachment.cgi?id=609133&action=edit
Errors in profile

Couldn't copy the error text. Looks like AppArmor hasnt been configured.

Just open the YaST module and try using it.


--1412691670.B1bBfe5.17602
Date: Tue, 7 Oct 2014 14:21:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900099
           Summary: smartmontools: generate_smartd_opts refers to init script
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201410*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: sbrabec-at-suse.com
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

- /usr/lib/smartmontools/generate_smartd_opts refers to an init script that no
longer exists
- /usr/lib/smartmontools/generate_smartd_opts is never called AFAICS unless one
uses YaST to edit /etc/sysconfig/smartmontools. Maybe the service file should
call it before launching smartd?
- /var/lib/smartmontools/smartd_opts should probably be moved to /run
- rcsmartd symlink is missing


body:
Build Identifier: Factory snapshot 20141002

The summary line tells it all.

Reproducible: Always

summary: man 2 ioctl says to see also ioctl_list(2), but ioctl_list(2) is missing


--1412717680.c1A5EaeF0.20358
Date: Tue, 7 Oct 2014 21:34:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900159
           Summary: SSSD AD support partially broken in 1.12.0
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.2 Beta 1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: joschibrauchle-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The sssd-ad plugin seems to be partially broken in SSSD version 1.12.0.

It does not resolv the name of the users main groups as well as any of the
users additional groups at all. The problem was mentioned on the sssd_devel
email list and the suggested solution was to upgrade to version 1.12.1.

Please upgrade openSUSE 13.2 to SSSD 1.12.1. I have built a test version in OBS
here:
https://build.opensuse.org/package/show/home:endzone:branches:network:ldap/sssd

The new plugins coming with 1.12.1 have been disabled, so the same
functionality as in 1.12.0 is provided.


body:
Build Identifier: Default factory build as well as security:apparmor build

When I try to create a profile following the instructions on activedoc
(https://activedoc.opensuse.org/book/opensuse-security-guide/chapter-17-getting-started#sec.apparmor.start.build)
apparmor crashes before I can look over the rules.

Reproducible: Always

Steps to Reproduce:
1. run aa-genprof firefox
2. Press S to scan logs
3. apparmor crashes
Actual Results:
Apparmor crashes and spits out an error (see attachment)

summary: Apparmor crashes attempting to create profile


--1412735049.Df13f460.7071
Date: Wed, 8 Oct 2014 02:24:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900186
           Summary: Uninstalling libreoffice packages lead to bunch of warning/error messages
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201410*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LibreOffice
          Assignee: bnc-team-ooo-at-forge.provo.novell.com
          Reporter: badshah400-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

From terminal

sudo zypper rm libreoffice*

leads to

(17/21) Removing libreoffice-l10n-en-4.3.1.2-1.2
............................................[done]
Additional rpm output:
ls: cannot access /usr/lib64//libreoffice/help/en-US/sbasic.idxl/*: No such
file or directory
ls: cannot access /usr/lib64//libreoffice/help/en-US/scalc.idxl/*: No such file
or directory
ls: cannot access /usr/lib64//libreoffice/help/en-US/schart.idxl/*: No such
file or directory
ls: cannot access /usr/lib64//libreoffice/help/en-US/sdatabase.idxl/*: No such
file or directory
ls: cannot access /usr/lib64//libreoffice/help/en-US/sdraw.idxl/*: No such file
or directory
ls: cannot access /usr/lib64//libreoffice/help/en-US/simpress.idxl/*: No such
file or directory
ls: cannot access /usr/lib64//libreoffice/help/en-US/smath.idxl/*: No such file
or directory
ls: cannot access /usr/lib64//libreoffice/help/en-US/swriter.idxl/*: No such
file or directory
ls: cannot access /usr/lib64//libreoffice/program/resource/*: No such file or
directory
ls: cannot access /usr/lib64//libreoffice/share/autotext/en-US/*: No such file
or directory
ls: cannot access /usr/lib64//libreoffice/share/registry/res/*: No such file or
directory

(18/21) Removing libreoffice-icon-theme-tango-4.3.1.2-1.2
...................................[done]
(19/21) Removing libreoffice-icon-theme-sifr-4.3.1.2-1.2
....................................[done]
(20/21) Removing libreoffice-4.3.1.2-1.2
....................................................[done]
Additional rpm output:
warning: file /usr/lib64/libreoffice/share/uno_packages/cache/uno_packages:
remove failed: No such file or directory

The last "remove failed" looks scary.


--1412754630.7CFDbc80.25601
Date: Wed, 8 Oct 2014 07:50:30 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900217
           Summary: VUL-0: CVE-2014-7275: The IMAP-over-SSL implementation in getmail 4.44.0 does not verify that theserver hostname matches ...
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: krahmer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2014-7275

The POP3-over-SSL implementation in getmail 4.0.0 through 4.44.0 does not
verify
X.509 certificates from SSL servers, which allows man-in-the-middle attackers
to
spoof POP3 servers and obtain sensitive information via a crafted certificate.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-7273
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-7275
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-7274
http://seclists.org/oss-sec/2014/q4/199
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-7273
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-7275
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-7274
http://openwall.com/lists/oss-security/2014/10/07/33
http://pyropus.ca/software/getmail/CHANGELOG


body:
--1412849330.6f53cC800.6928
Date: Thu, 9 Oct 2014 10:08:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900424
           Summary: zsh completion for rpm missing
    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: devel-at-fresse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

_rpm, the completion file for the rpm(1) command, is in Completion/Redhat/ in
the upstream source tarball and the upstream installation.

However, on openSuSE 13.1 this file is missing altogether.

summary: zsh completion for rpm missing


--1412908936.Cb7f10a0.31277
Date: Fri, 10 Oct 2014 02:42:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900558
           Summary: Impossible to boot in single user mode with root mounted read only
    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: archie-at-dellroad.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I have a 13.1 system with all the latest updates as of today and it is spitting
out the

  UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY

message for the root filesystem, and then booting normally with root mounted
root read-write.

First of all, I would expect it to not boot normally in this case, but
whatever.

Anyway, when I try to do what it says, it's impossible!

Here's why: even though I reboot with "single ro" on the boot line and it does
in fact go into single user mode, it still mounts root read-write (after
complaining of the same fsck errors).

Since the 1980's single user mode has always left root mounted read-only so you
can run fsck if needed, and you can always remount it read-write if you want.
Why did this change?

Of course "mount -o remount,ro /" doesn't work.

Because root is mounted read-write and it's impossible to get the system to
boot with root mounted read-only, then even in single user mode, it's
impossible to run fsck and fix the problem.

So it's impossible to resolve this problem without the use of a rescue disk.

Please fix, this is a bad dead-end people can fall into.


--1412947167.8b0A7304.17216
Date: Fri, 10 Oct 2014 13:19:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900639
           Summary: firefox stopped to spell check - needs external dictionaries
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201410*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Firefox
          Assignee: pcerny-at-suse.com
          Reporter: sbrabec-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: pgajdos-at-suse.com
          Found By: ---
           Blocker: ---

Two days ago after update to the latest Factory, Firefox stopped to spell
check. Instead of it the pull-down menu offers installation of dictionaries
from https://addons.mozilla.org/cs/firefox/language-tools/ . These dictionaries
work.


body:
--1412951324.F5110.16525
Date: Fri, 10 Oct 2014 14:28:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900654
           Summary: hb_report can't find logs on Factory / 13.2, breaking crmsh and hawk history explorer
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201410*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: High Availability
          Assignee: lmb-at-suse.com
          Reporter: kgronlund-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

It seems all logs are now through journalctl, so hb_report needs to gain the
ability to discover and collect those.

Hawk will report an error like this when trying to collect logs:

linux-ew84: WARN: no log at linux-ew84
ERROR: 2:
/srv/www/hawk/tmp/explorer/hb_report-hawk-2014-10-09_15:32-2014-10-10_15:32.tar.bz2:
no nodes in report

pkgs: cluster-glue crmsh


body:
--1413116608.3D233.24476
Date: Sun, 12 Oct 2014 12:23:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900815
           Summary: iwlwifi connection issue
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

iwlwifi has problems with the connection. It appears to be good quality but
suddenly barely allows any traffic anymore. The same system works fine on 12.3.

Output of dmesg|grep iwlwifi

[   10.499912] iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM
control
[   10.500140] iwlwifi 0000:02:00.0: irq 46 for MSI/MSI-X
[   10.762101] iwlwifi 0000:02:00.0: loaded firmware version 18.168.6.1 op_mode
iwldvm
[   10.770955] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG enabled
[   10.770960] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS enabled
[   10.770962] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[   10.770964] iwlwifi 0000:02:00.0: Detected Intel(R) Centrino(R) Advanced-N
6235 AGN, REV=0xB0
[   10.771152] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
[   26.894352] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
[   26.901016] iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
[   27.169496] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
[   27.176147] iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
[  455.029060] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 2
[  455.029067] iwlwifi 0000:02:00.0: Current SW read_ptr 120 write_ptr 171
[  455.029151] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[  455.029171] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x80102087
[  455.029191] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[  455.029205] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x80300015
[  455.029225] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[  455.029252] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[  455.029278] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[  455.029353] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090b1
[  455.029542] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid
0x0000 [22,22]
[  455.029623] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  455.029700] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid
0x0000 [120,171]
[  455.029767] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  455.029829] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  455.029891] iwlwifi 0000:02:00.0: Q 5 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  455.029952] iwlwifi 0000:02:00.0: Q 6 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  455.030056] iwlwifi 0000:02:00.0: Q 7 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  455.030141] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  455.030221] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid
0x0000 [178,178]
[  455.030381] iwlwifi 0000:02:00.0: Q 10 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  455.030460] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  455.030546] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  455.030632] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  455.030712] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  455.030791] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  455.030871] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  455.030951] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  455.031103] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  455.031182] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  457.034393] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 2
[  457.034398] iwlwifi 0000:02:00.0: Current SW read_ptr 142 write_ptr 174
[  457.034463] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[  457.034476] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x8010209d
[  457.034489] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[  457.034502] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x80300016
[  457.034515] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[  457.034528] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[  457.034541] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[  457.034555] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090b2
[  457.034610] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid
0x0000 [23,23]
[  457.034664] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  457.034724] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid
0x0000 [142,174]
[  457.034778] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  457.034832] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  457.034887] iwlwifi 0000:02:00.0: Q 5 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  457.034941] iwlwifi 0000:02:00.0: Q 6 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  457.034995] iwlwifi 0000:02:00.0: Q 7 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  457.035055] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  457.035109] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid
0x0000 [179,179]
[  457.035164] iwlwifi 0000:02:00.0: Q 10 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  457.035218] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  457.035272] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  457.035368] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  457.035481] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  457.035564] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  457.035679] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  457.035739] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  457.035793] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  457.035848] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  460.024288] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 2
[  460.024310] iwlwifi 0000:02:00.0: Current SW read_ptr 156 write_ptr 187
[  460.024395] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[  460.024415] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x801020ab
[  460.024435] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[  460.024449] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x80300018
[  460.024463] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[  460.024483] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[  460.024504] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[  460.024524] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090b5
[  460.024587] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid
0x0000 [25,25]
[  460.024664] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  460.024741] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid
0x0000 [156,187]
[  460.024803] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  460.024886] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  460.024947] iwlwifi 0000:02:00.0: Q 5 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  460.025008] iwlwifi 0000:02:00.0: Q 6 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  460.025070] iwlwifi 0000:02:00.0: Q 7 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  460.025137] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  460.025198] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid
0x0000 [182,182]
[  460.025266] iwlwifi 0000:02:00.0: Q 10 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  460.025416] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  460.025499] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  460.025561] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  460.025628] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  460.025690] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  460.025752] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  460.025814] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  460.025883] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  460.025945] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  464.032948] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 2
[  464.032956] iwlwifi 0000:02:00.0: Current SW read_ptr 172 write_ptr 214
[  464.033041] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[  464.033077] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x801020bb
[  464.033103] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[  464.033124] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x80300020
[  464.033144] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[  464.033181] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[  464.033201] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[  464.033228] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090bf
[  464.033291] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid
0x0000 [33,33]
[  464.033367] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  464.033445] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid
0x0000 [172,214]
[  464.033523] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  464.033606] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  464.033684] iwlwifi 0000:02:00.0: Q 5 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  464.033762] iwlwifi 0000:02:00.0: Q 6 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  464.033847] iwlwifi 0000:02:00.0: Q 7 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  464.033974] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  464.034052] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid
0x0000 [192,192]
[  464.034136] iwlwifi 0000:02:00.0: Q 10 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  464.034294] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  464.034377] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  464.034454] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  464.034568] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  464.034635] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  464.034751] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  464.034828] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  464.034911] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  464.034990] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  487.942626] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 2
[  487.942633] iwlwifi 0000:02:00.0: Current SW read_ptr 234 write_ptr 66
[  487.942718] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[  487.942738] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x801020f9
[  487.942758] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[  487.942772] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x80300021
[  487.942792] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[  487.942812] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[  487.942826] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[  487.942840] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090ce
[  487.942909] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid
0x0000 [34,34]
[  487.942993] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  487.943071] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid
0x0000 [234,66]
[  487.943138] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  487.943200] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  487.943268] iwlwifi 0000:02:00.0: Q 5 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  487.943330] iwlwifi 0000:02:00.0: Q 6 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  487.943397] iwlwifi 0000:02:00.0: Q 7 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  487.943459] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  487.943527] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid
0x0000 [207,207]
[  487.943600] iwlwifi 0000:02:00.0: Q 10 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  487.943717] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  487.943795] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  487.943878] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  487.943933] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  487.944010] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  487.944072] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  487.944139] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  487.944194] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  487.944260] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  491.040658] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 2
[  491.040664] iwlwifi 0000:02:00.0: Current SW read_ptr 239 write_ptr 70
[  491.040748] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[  491.040768] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x801020fe
[  491.040788] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[  491.040808] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x80300022
[  491.040822] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[  491.040836] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[  491.040849] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[  491.040863] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090d3
[  491.040925] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid
0x0000 [35,35]
[  491.040986] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  491.041047] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid
0x0000 [239,70]
[  491.041108] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  491.041169] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  491.041230] iwlwifi 0000:02:00.0: Q 5 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  491.041297] iwlwifi 0000:02:00.0: Q 6 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  491.041358] iwlwifi 0000:02:00.0: Q 7 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  491.041425] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  491.041480] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid
0x0000 [212,212]
[  491.041541] iwlwifi 0000:02:00.0: Q 10 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  491.041602] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  491.041704] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  491.041801] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  491.041953] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  491.042020] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  491.042075] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  491.042142] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  491.042203] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  491.042270] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  494.052691] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 2
[  494.052699] iwlwifi 0000:02:00.0: Current SW read_ptr 245 write_ptr 80
[  494.052784] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[  494.052804] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x80102004
[  494.052825] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[  494.052860] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x80300023
[  494.052880] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[  494.052900] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[  494.052921] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[  494.052941] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090d4
[  494.053004] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid
0x0000 [36,36]
[  494.053081] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  494.053159] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid
0x0000 [245,80]
[  494.053236] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  494.053298] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  494.053382] iwlwifi 0000:02:00.0: Q 5 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  494.053466] iwlwifi 0000:02:00.0: Q 6 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  494.053527] iwlwifi 0000:02:00.0: Q 7 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  494.053613] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  494.053692] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid
0x0000 [213,213]
[  494.053754] iwlwifi 0000:02:00.0: Q 10 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  494.053818] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  494.053897] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  494.053980] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  494.054042] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  494.054126] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  494.054188] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  494.054250] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  494.054312] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  494.054389] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  500.054562] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 2
[  500.054569] iwlwifi 0000:02:00.0: Current SW read_ptr 6 write_ptr 96
[  500.054658] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[  500.054695] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x80102015
[  500.054715] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[  500.054736] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x80300024
[  500.054756] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[  500.054775] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[  500.054796] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[  500.054810] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090d7
[  500.054872] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid
0x0000 [37,37]
[  500.054950] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  500.055027] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid
0x0000 [6,96]
[  500.055105] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  500.055183] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  500.055250] iwlwifi 0000:02:00.0: Q 5 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  500.055312] iwlwifi 0000:02:00.0: Q 6 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  500.055397] iwlwifi 0000:02:00.0: Q 7 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  500.055458] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  500.055539] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid
0x0000 [216,216]
[  500.055657] iwlwifi 0000:02:00.0: Q 10 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  500.055742] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  500.055821] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  500.055908] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  500.055994] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  500.056072] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  500.056157] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  500.056242] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  500.056323] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  500.056404] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  502.059891] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 2
[  502.059898] iwlwifi 0000:02:00.0: Current SW read_ptr 14 write_ptr 101
[  502.059982] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[  502.060002] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x8010201d
[  502.060023] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[  502.060057] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x80300025
[  502.060078] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[  502.060097] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[  502.060117] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[  502.060138] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090d8
[  502.060200] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid
0x0000 [38,38]
[  502.060278] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  502.060339] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid
0x0000 [14,101]
[  502.060407] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  502.060469] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  502.060535] iwlwifi 0000:02:00.0: Q 5 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  502.060596] iwlwifi 0000:02:00.0: Q 6 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  502.060663] iwlwifi 0000:02:00.0: Q 7 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  502.060724] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  502.060792] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid
0x0000 [217,217]
[  502.060894] iwlwifi 0000:02:00.0: Q 10 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  502.060974] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  502.061059] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  502.061139] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  502.061217] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  502.061301] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  502.061379] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  502.061462] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  502.061548] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  502.061628] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  505.053834] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 2
[  505.053841] iwlwifi 0000:02:00.0: Current SW read_ptr 29 write_ptr 103
[  505.053925] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[  505.053945] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x8010202c
[  505.053966] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[  505.054001] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x80300026
[  505.054021] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[  505.054041] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[  505.054055] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[  505.054070] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090de
[  505.054138] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid
0x0000 [39,39]
[  505.054216] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  505.054293] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid
0x0000 [29,103]
[  505.054378] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  505.054455] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  505.054523] iwlwifi 0000:02:00.0: Q 5 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  505.054606] iwlwifi 0000:02:00.0: Q 6 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  505.054668] iwlwifi 0000:02:00.0: Q 7 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  505.054753] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  505.054865] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid
0x0000 [223,223]
[  505.054945] iwlwifi 0000:02:00.0: Q 10 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  505.055024] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  505.055110] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  505.055195] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  505.055272] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  505.055356] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  505.055434] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  505.055503] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  505.055565] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  505.055632] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  509.055469] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 2
[  509.055476] iwlwifi 0000:02:00.0: Current SW read_ptr 47 write_ptr 110
[  509.055559] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[  509.055579] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x8010203e
[  509.055599] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[  509.055619] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x80300027
[  509.055639] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[  509.055659] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[  509.055673] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[  509.055688] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090e6
[  509.055765] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid
0x0000 [40,40]
[  509.055843] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  509.055905] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid
0x0000 [47,110]
[  509.055988] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  509.056050] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  509.056117] iwlwifi 0000:02:00.0: Q 5 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  509.056179] iwlwifi 0000:02:00.0: Q 6 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  509.056256] iwlwifi 0000:02:00.0: Q 7 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  509.056340] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  509.056402] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid
0x0000 [231,231]
[  509.056522] iwlwifi 0000:02:00.0: Q 10 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  509.056607] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  509.056688] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  509.056770] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  509.056856] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  509.056934] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  509.057011] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  509.057095] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  509.057173] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  509.057251] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  515.060371] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 2
[  515.060375] iwlwifi 0000:02:00.0: Current SW read_ptr 105 write_ptr 121
[  515.060433] iwlwifi 0000:02:00.0: FH TRBs(0) = 0x00000000
[  515.060446] iwlwifi 0000:02:00.0: FH TRBs(1) = 0x80102078
[  515.060459] iwlwifi 0000:02:00.0: FH TRBs(2) = 0x00000000
[  515.060472] iwlwifi 0000:02:00.0: FH TRBs(3) = 0x8030002a
[  515.060484] iwlwifi 0000:02:00.0: FH TRBs(4) = 0x00000000
[  515.060497] iwlwifi 0000:02:00.0: FH TRBs(5) = 0x00000000
[  515.060509] iwlwifi 0000:02:00.0: FH TRBs(6) = 0x00000000
[  515.060522] iwlwifi 0000:02:00.0: FH TRBs(7) = 0x007090eb
[  515.060576] iwlwifi 0000:02:00.0: Q 0 is active and mapped to fifo 3 ra_tid
0x0000 [43,43]
[  515.060629] iwlwifi 0000:02:00.0: Q 1 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  515.060683] iwlwifi 0000:02:00.0: Q 2 is active and mapped to fifo 1 ra_tid
0x0000 [105,121]
[  515.060736] iwlwifi 0000:02:00.0: Q 3 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  515.060790] iwlwifi 0000:02:00.0: Q 4 is active and mapped to fifo 0 ra_tid
0x0000 [0,0]
[  515.060849] iwlwifi 0000:02:00.0: Q 5 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  515.060902] iwlwifi 0000:02:00.0: Q 6 is active and mapped to fifo 2 ra_tid
0x0000 [0,0]
[  515.060956] iwlwifi 0000:02:00.0: Q 7 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  515.061009] iwlwifi 0000:02:00.0: Q 8 is active and mapped to fifo 4 ra_tid
0x0000 [0,0]
[  515.061063] iwlwifi 0000:02:00.0: Q 9 is active and mapped to fifo 7 ra_tid
0x0000 [236,236]
[  515.061117] iwlwifi 0000:02:00.0: Q 10 is active and mapped to fifo 5 ra_tid
0x0000 [0,0]
[  515.061171] iwlwifi 0000:02:00.0: Q 11 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  515.061224] iwlwifi 0000:02:00.0: Q 12 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  515.061278] iwlwifi 0000:02:00.0: Q 13 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  515.061331] iwlwifi 0000:02:00.0: Q 14 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  515.061448] iwlwifi 0000:02:00.0: Q 15 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  515.061509] iwlwifi 0000:02:00.0: Q 16 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  515.061564] iwlwifi 0000:02:00.0: Q 17 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  515.061618] iwlwifi 0000:02:00.0: Q 18 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]
[  515.061672] iwlwifi 0000:02:00.0: Q 19 is inactive and mapped to fifo 0
ra_tid 0x0000 [0,0]

summary: iwlwifi connection issue


--1413138266.1f8405.6458
Date: Sun, 12 Oct 2014 18:24:26 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900836
           Summary: GNOME lock screen unlocks without password if fprintd is installed
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201410*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: rbrown-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Using the latest openSUSE Factory snapshot (also present in openSUSE 13.2 RC1)
GNOME automatically unlocks if fprintd is present

The user never gets asked for a password
The user never has an opportunity to enter their fingerprint

journal shows fprintd starting each time the lock screen is activated, but no
errors or warnings to imply it's misbehaving

Removing fprintd 'resolves' the issue but disables fingerprint authentication

Current theories to resolve this include -
Using the same gdm-fingerprint pam configuration as Fedora
https://git.gnome.org/browse/gdm/tree/data/pam-redhat/gdm-fingerprint.pam

Enabling split-authentication in the gdm package (currently being built in my
OBS home)


--1413142440.066cD0.21389
Date: Sun, 12 Oct 2014 19:34:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900839
           Summary: vim: when editing *.changes, set expandtab
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201410*
          Hardware: Other
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: msvec-at-suse.com
          Reporter: suse-beta-at-cboltz.de
        QA Contact: qa-bugs-at-suse.de
          Found By: Beta-Customer
           Blocker: ---

When editing a .changes file, vim in some cases inserts tabs after pressing
enter.

Please add
    set expandtab
for *.changes files to make sure only spaces are used.

I'm not sure if adding it to /usr/share/vim/vim74/syntax/changes.vim will work,
but I'll let that detail for you to test ;-)

Until this bug is fixed, I'm using a one-line
~/.vim/ftplugin/changes/changes-cboltz.vim with just "set expandtab".


--1413186907.258fCd0.13701
Date: Mon, 13 Oct 2014 07:55:07 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900877
           Summary: new libreoffice does not obsolete old libreoffice
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201410*
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LibreOffice
          Assignee: bnc-team-ooo-at-forge.provo.novell.com
          Reporter: ohering-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

upgrading from 11.2 to Factory leaves old packages behind. yast just forces
install of new packages, but zypper dup does fileconflict checking.
I suggest to add proper Provides/Obsoletes/Conflicts to the spec file.

File /usr/lib64/libreoffice/ure/bin/javaldx
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/bin/regmerge
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/bin/regview
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/bin/startup.sh
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/bin/uno.bin
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/JREProperties.class
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/jvmfwk3rc
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/libaffine_uno_uno.so
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/libgcc3_uno.so
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/libjava_uno.so
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/libjpipe.so
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/libjuh.so
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/libjuhx.so
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/liblog_uno_uno.so
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/libuno_cppu.so.3
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/libuno_cppuhelpergcc3.so.3
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/libuno_purpenvhelpergcc3.so.3
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/libuno_sal.so.3
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/libuno_salhelpergcc3.so.3
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/libunsafe_uno_uno.so
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/lib/unorc
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/share/java/java_uno.jar
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/share/java/juh.jar
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/share/java/jurt.jar
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/share/java/ridl.jar
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/share/java/unoloader.jar
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/share/misc/javavendors.xml
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/lib64/libreoffice/ure/share/misc/types.rdb
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)

File /usr/share/libreoffice/link-to-ooo-home
  from install of
     libreoffice-4.3.2.2-1.1.x86_64(factory-oss)
  conflicts with file from package
     libreoffice-ure-3.3.1.2-2.2.3.x86_64(@System)


--1413190233.af0310.22191
Date: Mon, 13 Oct 2014 08:50:33 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900884
           Summary: xserver Xorg hangs in vmware_drv.so during reset/shutdown
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: VMWare
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: holger.a.teutsch-at-googlemail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: Beta-Customer
           Blocker: ---

When a KDE is terminated (Logout) the Xserver hangs and loops with 100% CPU.

(gdb) bt
#0  0x00007f4b65c3b0f5 in vmwgfx_saa_drop_master (pScreen=<optimized out>)
    at vmwgfx_saa.c:1605
#1  0x00007f4b65c340b3 in drv_leave_vt (arg=0x1e80240) at vmwgfx_driver.c:1185
#2  0x00007f4b65c3461f in drv_close_screen (pScreen=0x1e8ed10)
    at vmwgfx_driver.c:1237
#3  0x00000000004ada27 in ?? ()
#4  0x0000000001e9a610 in ?? ()
#5  0x0000000001ea9d90 in ?? ()
#6  0x0000000001e9a610 in ?? ()
#7  0x00000000004cb158 in ?? ()
#8  0x0000000100000000 in ?? ()
#9  0x0000000001e8ed10 in ?? ()
#10 0x0000000001ea8fa0 in ?? ()
#11 0x0000000001ea9d90 in ?? ()
#12 0x0000000001eab6e0 in ?? ()
#13 0x0000000000000006 in ?? ()
#14 0x0000000000827078 in ?? ()
#15 0x000000000050f1b4 in ?? ()
#16 0x0000000000827040 in ?? ()
#17 0x0000000001e8ed10 in ?? ()
#18 0x0000000001eab6e0 in ?? ()
#19 0x0000000000510a03 in ?? ()
#20 0x00000000008267e8 in ?? ()
#21 0x0000000000000000 in ?? ()
(gdb) li
1600
1601        WSBMLISTFOREACH(list, &vsaa->pixmaps) {
1602            vpix = WSBMLISTENTRY(list, struct vmwgfx_saa_pixmap,
pixmap_list);
1603            spix = &vpix->base;
1604
1605            if (!vpix->hw)
1606                continue;
1607
1608            (void) vmwgfx_download_from_hw(&vsaa->driver, spix->pixmap,
1609                                           &spix->dirty_hw);
(gdb)

Each iteration returns the same vpix with vpix->hw == NULL.

Can be reproduced at will.

Vmware Player: 6.0.3 build-1895310 / Windows 7 64 bit


--1413220937.EA2bf30.30554
Date: Mon, 13 Oct 2014 17:22:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 900982
           Summary: NetworkManager doesn't write ntp settings
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

# grep -i ntp
/var/lib/NetworkManager/dhclient-983a1f84-fc81-434a-a168-6ac814bbf868-enp4s0.lease
  option ntp-servers 192.168.170.3;
# grep -i ntp /run/netconfig/NetworkManager.netconfig
# ntpq -c peers
No association ID's returned
#


body:
--1413306522.F31baE0.5645
Date: Tue, 14 Oct 2014 17:08:42 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 901148
           Summary: colord apparmor profile missing file
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201410*
          Hardware: 64bit
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: tpikalek-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

File /etc/udev/hwdb.bin is missing in apparmor colord profile, I get this
error:
apparmor="DENIED" operation="open" profile="/usr/lib/colord"
name="/etc/udev/hwdb.bin" pid=1985 comm="colord" requested_mask="r"
denied_mask="r" fsuid=483 ouid=0

summary: colord apparmor profile missing file


--1413378619.5dD4d7C0.4636
Date: Wed, 15 Oct 2014 13:10:19 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 901337
           Summary: network/wicked: Bug Request to add new systemd network-pre,target to enable early/secure pre-network dependency activation of network services
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Hardware: Other
                OS: openSUSE 13.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: dev+opensuse-at-pgnd.us
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Upstream systemd v>=214 has added a network-pre.target necessary for early
ordering of services before network start, with particular useful application
for firewalls.

As resolved in

    "Bug 900505 - Base:System/systemd: Bug Request to add upstream's patch to
include v214's new 'network-pre.target' for early/secure pre-network dependency
activation of firewall services
    https://bugzilla.opensuse.org/show_bug.cgi?id=900505#c15

the patch implementing the target has been backported & added to openSUSE's
systemd v210, which is available from Base:System in openSUSE v13.1, and will
be standard in v>=13.2.

As correctly pointed out by Werner Fink in response @ Shorewall ML's thread

    Re: [Shorewall-devel] [Shorewall-users] SW 4.6.4+' systemd service files'
Before=/After= dependency on 'network.target'


body:
--1413383115.4cDc222.17268
Date: Wed, 15 Oct 2014 14:25:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 901361
           Summary: IMAP+ plugin forces SSL 3.0
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Evolution
          Assignee: bnc-team-evolution-at-forge.provo.novell.com
          Reporter: sionescu-at-cddr.org
        QA Contact: lakhil-at-novell.com
          Found By: ---
           Blocker: ---

Today(2014-10-15), FastMail disabled SSL 3.0 on all their servers because of a
recently discovered vulnerability, and Evolution cannot connect to the imap
server because it apparently forces SSL 3.0 on the outbound connection.

I'm using Evolution 3.10.4-24.1 on x86_64 and the account is configured as
follows: plugin IMAP+ on host "mail.messagingengine.com", port 993, encryption
method "SSL on a dedicated port"

The exact error message I get is
"Could not connect to 'mail.messagingengine.com:993': Cannot communicate
securely with peer: no common encryption algorithm(s)."

summary: IMAP+ plugin forces SSL 3.0


--1413407113.02c50.32694
Date: Wed, 15 Oct 2014 21:05:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 901450
           Summary: rss-glx should install screensavers into /usr/lib(64)/xscreensaver
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: i-at-marguerite.su
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hi,

rss-glx has been broken since it was introduced into openSUSE:

http://www.linuxquestions.org/questions/linuxquestions-org-member-success-stories-23/opensuse-12-3-rss-glx-screen-savers-and-kde-4175460477/

I found this because coolo introduced its translations for 13.2, and I had to
get it running first before translating properly.

As the quickfix showed, currently the binraries are installed into /usr/bin,
But KDE will find it in /usr/lib64/xscreensaver.

I don't know if this directory is KDE-specific or Xorg-specific, but if those
binraries won't go there, rss-glx will be broken all the time.

But openSUSE won't allow binraries in /usr/lib64, so we need a patch for
rss-glx at least.

Marguerite


--1413476816.5B38a0.26554
Date: Thu, 16 Oct 2014 16:26:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 901597
           Summary: SambaBackendLDAP.pm line 121: Possible precedence issue with control flow operator
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201410*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Samba
          Assignee: samba-maintainers@SuSE.de
          Reporter: locilka-at-suse.com
        QA Contact: samba-maintainers@SuSE.de
          Found By: ---
           Blocker: ---

Created attachment 610396
  --> http://bugzilla.suse.com/attachment.cgi?id=610396&action=edit
Yast logs

linux-3fmo:~ # yast2 clone_system

Produces this <STDERR>:

Possible precedence issue with control flow operator at
        /usr/share/YaST2/modules/SambaBackendLDAP.pm line 121 (#1)
    (W syntax) There is a possible problem with the mixing of a control
    flow operator (e.g. return) and a low-precedence operator like
    or.  Consider:

        sub { return $a or $b; }

    This is parsed as:

        sub { (return $a) or $b; }

    Which is effectively just:

        sub { return $a; }

    Either use parentheses or the high-precedence variant of the operator.

    Note this may be also triggered for constructs like:

        sub { 1 if die; }


body:
--1413656992.cdd00.22303
Date: Sat, 18 Oct 2014 18:29:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 901836
           Summary: ocaml fails to build on PowerPC 64bit
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 201410*
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: dvaleev-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

With update to ocaml 4.02.0 build starts to fail for PowerPC 64bit
[  149s] File "asmcomp/proc.ml", line 1:
[  149s] Error: The implementation asmcomp/proc.ml
[  149s]        does not match the interface asmcomp/proc.cmi:
[  149s]        The value `op_is_pure' is required but not provided
[  149s]        The value `regs_are_volatile' is required but not provided
[  149s] Makefile:822: recipe for target 'asmcomp/proc.cmo' failed
[  149s] make[3]: *** [asmcomp/proc.cmo] Error 2

summary: ocaml fails to build on PowerPC 64bit


body:
--1413716054.86317125.25015
Date: Sun, 19 Oct 2014 10:54:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 901845
           Summary: Dirmngr crashes immediately
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: 32bit
                OS: openSUSE 13.2
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: Pavel.Vachek-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Dirmngr version 1.1.1-2.1.3 (i586) crashes immediately every time in OpenSUSE
13.2 RC1 (and Beta1):

$ dirmngr --server -v
Segmentation fault

$ dirmngr --daemon
Segmentation fault

$ dirmngr --help
Segmentation fault

$ dirmngr --version
Segmentation fault

Dirmngr version 1.1.0-18.1.2 in OpenSUSE version 13.1 works correctly:

$ dirmngr --version
dirmngr 1.1.0
Copyright (C) 2010 g10 Code GmbH
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.

Thank you very much for your attention.
P.V.

summary: Dirmngr crashes immediately


--1413735473.e3cbc30.5794
Date: Sun, 19 Oct 2014 16:17:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 901857
           Summary: Base:System/gnutls: disable-srp in gnutls.spec
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: x86-64
                OS: SUSE Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: 3rd party software
          Assignee: shchang-at-suse.com
          Reporter: BM-2cTD873dxoyND9nkERkefY9xMV8Vy2ga2w-at-bitmessage.ch
        QA Contact: opensuse-communityscreening-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

In the gnutls.spec file the configure script is started with the option
"--disable-srp".

In the log file the script gives a warning:

configure: WARNING: unrecognized options: --disable-srp

and ignores this option.

Perhaps "--disable-srp-authentication" or "--disable-dtls-srtp-support" was
intended but not given as option?


--1413752644.3851D4d0.18070
Date: Sun, 19 Oct 2014 21:04:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 901859
           Summary: LVM2: lvs command gives error message about lvmetad
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: i686
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: seroton10-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Did a fresh install of 13.2 RC1 on a clean disk with default settings, except
that for the disk layout I enabled use of LVM and encryption. The installed
system works fine.

The strange thing is the following:

linux-ho45:~ # lvs
  WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
  LV   VG     Attr      LSize  Pool Origin Data%  Move Log Cpy%Sync Convert
  home system -wi-ao-


--1413839736.16a1BE2e8.16197
Date: Mon, 20 Oct 2014 21:15:36 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 901968
           Summary: serf / libserf supports insecure SSL protocol versions
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Hardware: Other
                OS: Other
            Status: CONFIRMED
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: Andreas.Stieger-at-gmx.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: ---
           Blocker: ---

From https://serf.googlecode.com/svn/tags/1.3.8/CHANGES
> Serf 1.3.8 [2014-10-20, from /tags/1.3.8, rxxxx]
> Fix issue #152: CRC calculation error for gzipped http reponses > 4GB.
> Fix issue #153: SSPI CredHandle not freed when APR pool is destroyed.
> Fix issue #154: Disable SSLv2 and SSLv3 as both or broken.

Patches for previous releases:

https://code.google.com/p/serf/source/detail?r=2313
> Disable the use of deprecated and broken SSL 2.0.
>
> * buckets/ssl_buckets.c
>   (ssl_init_context): Disable SSLv2.

https://code.google.com/p/serf/source/detail?r=2433
> Disable SSLv3 support (POODLE).
>
> * buckets/ssl_buckets.c
>   (ssl_init_context): Disable SSLv3, like already done for SSLv2.

Current versions:
openSUSE 12.3: serf 1.1.1 (to be patched as above on buckets/ssl_buckets.c
only)
openSUSE 13.1: serf 1.3.7 (straight update)
openSUSE 13.2: serf 1.3.7 (straight update)


body:
Build Identifier: yast2-samba-client-3.1.13-1.2.noarch

Hello,

My smb.conf in OpenSuSE 13.2 become invalid when I runned "yast2 samba-client
winbind enable". It added full domain path (instead of only domain name). Also,
it replaced my "idmap config" settings to deprecated format.

-

summary: "yast2 samba-client winbind enable" changes workgroup to realm


--1414058356.1B31340.24457
Date: Thu, 23 Oct 2014 09:59:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 902375
           Summary: mkinitrd/dracut ignores symlink in kernel argument
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: per-at-computer.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I have the following:

/boot/vmlinuz -> vmlinuz-vmlinuz-3.16.4-1.g7a8842b-desktop

when I run mkinitrd

# mkinitrd -i initrd -k vmlinuz -f nfs
Creating initrd: /boot/initrd
Kernel version vmlinuz has no module directory /lib/modules/vmlinuz

This clearly doesnt work, apparently "vmlinuz" is taken literally instead of as
a symlink?


--1414076503.c0edBB7.3602
Date: Thu, 23 Oct 2014 15:01:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 902421
           Summary: libsmbclient-devel demanding RUNPATH in pc file breaks programs also using libGL of Nvidia driver
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Hardware: x86-64
                OS: openSUSE 13.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Samba
          Assignee: samba-maintainers@SuSE.de
          Reporter: joachim.banzhaf-at-googlemail.com
        QA Contact: samba-maintainers@SuSE.de
          Found By: ---
           Blocker: ---

I tested latest xbmc aka kodi on opensuse with latest Nvidia driver.

Symptom: kodi menus show no text.

Cause:

Kodi links to libGL and libsmbclient.

There are 2 libGL.so on the system. One from Mesa in /usr/lib64 and one from
Nvidia in /usr/X11R6/lib64

System linker usually finds the correct Nvidia libGL through definition in
/etc/ld.so.conf.d

But not for Kodi (and maybe any other program that also uses libsmbclient)
because /usr/lib64/pkgconfig/smbclient.pc demands these linker options:
"-Wl,-rpath,/usr/lib64".

That looks wrong to me.

I removed the options from the pc file and kodi compiles and runs just fine.
Menu text visible and samba functionality still available.

Can the options be removed systemwide or why are they in the pc file?

More details here:
https://forums.opensuse.org/showthread.php/498989-13-1-NVIDIA-libGL-renderer-problem
http://forum.xbmc.org/showthread.php?tid=206976
http://trac.xbmc.org/ticket/15497


body:
--1414096331.7A677Cb0.16002
Date: Thu, 23 Oct 2014 20:32:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 902476
           Summary: tor: disable SSL3 (POODLE)
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: All
                OS: openSUSE 13.1
            Status: CONFIRMED
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: Andreas.Stieger-at-gmx.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
          Found By: ---
           Blocker: ---

https://gitweb.torproject.org/tor.git?a=blob_plain;hb=release-0.2.4;f=ReleaseNotes

Changes in version 0.2.4.25 - 2014-10-20
  Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
  (even though POODLE does not affect Tor). It also works around a crash
  bug caused by some operating systems' response to the "POODLE" attack
  (which does affect Tor).

  o Major security fixes (also in 0.2.5.9-rc):
    - Disable support for SSLv3. All versions of OpenSSL in use with Tor
      today support TLS 1.0 or later, so we can safely turn off support
      for this old (and insecure) protocol. Fixes bug 13426.

  o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
    - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
      1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
      13471. This is a workaround for an OpenSSL bug.

openSUSE:12.3:Update 0.2.4.24
openSUSE:13.1:Update 0.2.4.24
openSUSE:13.2 0.2.4.24
openSUSE:Factory 0.2.4.24

summary: tor: disable SSL3 (POODLE)


--1414146887.AF3Af8c0.16716
Date: Fri, 24 Oct 2014 10:34:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 902509
           Summary: zsh history garbled with option hist_reduce_blanks on
    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: devel-at-fresse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

How to reproduce:

$ zsh
$ setopt hist_reduce_blanks
$ echo  LALA LELE LULU
LALA LELE LULU

Now use cursor up to go to the previous history line:

$ echo LLAA LLEE ULUU

will appear


--1414180670.7A6DAcF0.27997
Date: Fri, 24 Oct 2014 19:57:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 902588
           Summary: mlocate no longer requires user to be member of locate group
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: Other
                OS: Other
            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: ---

I noticed when "mlocate" was selected as one of the packages for first time
install of openSUSE 13.1 the locate group was automatically created.

However, with openSUSE 13.2 RC1 the locate group is no longer created. This is
due to the fact that the locate group is no longer required.

The locate group is not necessary with the recent mlocate package as mlocate is
currently executed as nobody.

The description tab in Yast Software Management shows:

mlocate - An utility for finding files by name

A new locate implementation. The m character stands for merging, because
updatedb reuses the existing database to avoid re-reading most of the file
system. User must be member of locate group in order to use this package.

This description MUST be amended.


--1414372968.eaC317f9.23199
Date: Mon, 27 Oct 2014 01:22:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 902657
           Summary: digital clock's calender holiday settings are not saved when changed
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE4 Workspace
          Assignee: kde-maintainers-at-suse.de
          Reporter: rb03884-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 611255
  --> http://bugzilla.opensuse.org/attachment.cgi?id=611255&action=edit
Days Off Screenshot

The digital clock's calender holiday feature should allow the user to alter the
settings to show:

Not Used
Information
Days Off

When I select Canada as the region and choose "Days Off" then click on the
Apply and/or OK buttons the window closes and the changes are not saved.

I open the digital clock again to check the calender's holiday settings it
reset back to the "Days Off" default setting every time.


--1414573457.EfAC7B45.27376
Date: Wed, 29 Oct 2014 09:04:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 903009
           Summary: Failed at step EXEC spawning /usr/bin/systemd-tmpfiles-keep: No such file or directory
    Classification: openSUSE
           Product: openSUSE Factory
           Version: NO 13.2 BUGS!!
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Basesystem
          Assignee: systemd-maintainers-at-suse.de
          Reporter: mpluskal-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

With systemd from obs://build.opensuse.org/Base:System (systemd-210-872.4) I
have noticed following:
# dmesg
...
[  833.538753] systemd-coredump[15532]: Failed to log coredump: Connection
refused
[  833.641093] systemd-coredump[15470]: Failed to log coredump: Connection
refused
[  900.226178] systemd[22527]: Failed at step EXEC spawning
/usr/bin/systemd-tmpfiles-keep: No such file or directory

While is indeed not present on system systemd-tmpfiles-keep:
# file /usr/bin/systemd-tmpfiles-keep
/usr/bin/systemd-tmpfiles-keep: cannot open `/usr/bin/systemd-tmpfiles-keep'
(No such file or directory)


--1414588561.DA63B4.30502
Date: Wed, 29 Oct 2014 13:16:01 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 903051
           Summary: mdcheck sends emails about missing /dev/md* when no mdraid is used
    Classification: openSUSE
           Product: openSUSE Factory
           Version: NO 13.2 BUGS!!
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Basesystem
          Assignee: nfbrown-at-suse.com
          Reporter: mpluskal-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On freshly installed openSUSE-Factory I have noticed that root is recieving lot
of emails from /etc/cron.daily/mdadm / mdchechk:
Subject: Cron <root@daredevil> source /etc/sysconfig/mdadm; [ -n
"$MDADM_CHECK_DURATION" -a -x /usr/share/mdadm/mdcheck ] &&
/usr/share/mdadm/mdcheck --continue --duration "$MDADM_CHECK_DURATION"
...
X-Cron-Env: <USER=root>
Message-Id: <20141029000001.9EB45207@linux-e66k.site>
Date: Wed, 29 Oct 2014 01:00:01 +0100 (CET)

ls: cannot access /dev/md?*: No such file or directory

Which however does not make much sense since there is and never was any mdraid
used at all - perhaps mdcheck should not consider missing /dev/md* as error?


--1414677024.cFDD10.3001
Date: Thu, 30 Oct 2014 13:50:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 903276
           Summary: claws-mail please update to 3.11.0 from GNOME:Apps
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: nemysis-at-gmx.ch
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since yesterday with normal claws-mail 3.10.1 not works more SSL connections
with gmx.net and some other Provider.

Get always:

'SSL handshake failed'

Please update to 3.11.0 from GNOME:Apps that this now more happens.

After update from

https://build.opensuse.org/package/show?project=GNOME%3AApps&package=claws-mail

not have more this Issue and can normal use claws-mail with SSL and gmx.net
more accounts.

Have get advice from Upstream #claws from Freenode to use only 3.11.x or not
works this because SSL problems.


--1414752138.AF460.10396
Date: Fri, 31 Oct 2014 10:42:18 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 903431
           Summary: linphone supposed to support ZRTP but doesn't
    Classification: openSUSE
           Product: openSUSE Factory
           Version: NO 13.2 BUGS!!
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: bjacke-at-samba.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

accouring to the RPM changelog it looks like linphone should have been compiled
with ZRTP encryption support:

* Di Feb 11 2014 zaitor-at-opensuse.org
- Version pkgconfig(libzrtpcpp) BuildRequires to resolve build for
  13.2 and newer.
...
* Mo Nov 12 2012 mailaender-at-opensuse.org
- add libsrtp and libzrtpcpp as build dependency

But ZRTP is not compiled in.


--1414785495.afdB8F40.24110
Date: Fri, 31 Oct 2014 19:58:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 903520
           Summary: sensors fancontrol service status spam after start: fancontrol: /usr/sbin/fancontrol: line 481: [: too many arguments
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Hardware: x86-64
                OS: openSUSE 13.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: zombah-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,
I generated fancontrol config for my motherboard (asrock e350m1) with pwmconfig
from sensors-3.3.4-3.1.2.x86_64 package on openSUSE 13.1, but after fancontrol
service start, systemd status for fancontrol service spam messages like this:

Nov 01 06:58:19 hamtaro.site fancontrol[2481]: /usr/sbin/fancontrol: line 481:
[: too many arguments
Nov 01 06:58:29 hamtaro.site fancontrol[2481]: /usr/sbin/fancontrol: line 481:
[: too many arguments
Nov 01 06:58:39 hamtaro.site fancontrol[2481]: /usr/sbin/fancontrol: line 481:
[: too many arguments

Here is content of /etc/fancontrol that pwmconfig created:
# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=10
DEVPATH=hwmon2=devices/pci0000:00/0000:00:18.3
hwmon3=devices/platform/w83627ehf.656
DEVNAME=hwmon2=k10temp hwmon3=nct6775
FCTEMPS=hwmon3/device/pwm2=hwmon2/device/temp1_input
FCFANS= hwmon3/device/pwm2=
MINTEMP=hwmon3/device/pwm2=40
MAXTEMP=hwmon3/device/pwm2=65
MINSTART=hwmon3/device/pwm2=128
MINSTOP=hwmon3/device/pwm2=57


--1414835165.Bc4be1.12299
Date: Sat, 1 Nov 2014 09:46:05 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 903543
           Summary: systemd kadmind.service missing openldap dependency
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: x86-64
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: gleixner-at-lrz.de
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

If you configure auth-server via yast2 and herein kerberos using ldap as
storage (default), then kadmind.service fails to start on next reboot:

systemctl -l status kadmind.service
kadmind.service - Kerberos 5 Password-changing and Administration
   Loaded: loaded (/usr/lib/systemd/system/kadmind.service; enabled)
   Active: failed (Result: exit-code) since Sat 2014-11-01 09:38:21 CET; 1h
5min ago
  Process: 1035 ExecStart=/usr/lib/mit/sbin/kadmind -P /var/run/kadmind.pid
$KADMIND_ARGS (code=exited, status=1/FAILURE)

Nov 01 09:38:21 opensuse132beta kadmind[1035]: kadmind: Cannot bind to LDAP
server 'ldapi://' as 'cn=Administrator,dc=kerberos,dc=test': Can't contact LDAP
server while initializing, aborting

The service should also depend on slapd.service as krb5kdc.service does:

# grep slap /usr/lib/systemd/system/krb5kdc.service
After=network.target slapd.service
# grep After /usr/lib/systemd/system/kadmind.service
After=network.target


--1414947505.88cFf1D0.31782
Date: Sun, 2 Nov 2014 16:58:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 903581
           Summary: wwwoffled does not run with wwwoffle.service file
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: All
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: d_werner-at-gmx.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After upgrade with zypper dup from openSUSE 13.1 to 13.2 (13.2 repos) on Nov. 2
wwwoffled no longer works.
After the startup wwwoffled immediately terminates again.

systemctl status wwwoffle.service
wwwoffle.service - The wwwoffle proxy server
   Loaded: loaded (/usr/lib/systemd/system/wwwoffle.service; enabled)
   Active: inactive (dead) since Sun 2014-11-02 17:12:36 CET; 4s ago
  Process: 7103 ExecStart=/usr/sbin/wwwoffled -c /etc/wwwoffle/wwwoffle.conf
(code=exited, status=0/SUCCESS)
 Main PID: 7104 (code=exited, status=0/SUCCESS)

Nov 02 17:12:36 computer wwwoffled[7103]: WWWOFFLE Demon Version 2.9i (with
ipv6,with zlib,with gnutls) started.
Nov 02 17:12:36 computer wwwoffled[7103]: wwwoffled[7103] Important: WWWOFFLE
Demon Version 2.9i (with ipv6,with zlib,with gnutls) started.
Nov 02 17:12:36 computer wwwoffled[7105]: Detached from terminal and changed
pid to 7105.
Nov 02 17:12:36 computer wwwoffled[7103]: wwwoffled[7103] Important: Detached
from terminal and changed pid to 7105.

Workaround:
in /usr/lib/systemd/system/wwwoffle.service change the line
ExecStart=/usr/sbin/wwwoffled -c /etc/wwwoffle/wwwoffle.conf

to
ExecStart=/usr/sbin/wwwoffled -d -c /etc/wwwoffle/wwwoffle.conf


--1414957501.EA6A640.16164
Date: Sun, 2 Nov 2014 19:45:01 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 903588
           Summary: ddclient various severe file permissions after upgrade via zypper dup from 13.1 x86 to 13.2
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: x86
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Upgrade Problems
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: abittner-at-abittner.de
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

perfectly working 13.1 x86 with working ddclient

zypper dup to 13.2 (today)

ddclient doesnt work any more, doesnt start up, claims it cannot read
ddclient.conf and its ddclient.cache file and all sorts of weird stuff

-----

 rpm -qi ddclient
Name        : ddclient
Version     : 3.8.2
Release     : 4.1.3
Architecture: noarch
Install Date: Sun Nov  2 19:55:51 2014
Group       : Productivity/Networking/DNS/Utilities
Size        : 184935
License     : GPL-2.0+
Signature   : RSA/SHA256, Mon Oct  6 17:42:36 2014, Key ID b88b2fd43dbdc284
Source RPM  : ddclient-3.8.2-4.1.3.src.rpm
Build Date  : Mon Oct  6 17:42:26 2014
Build Host  : build05

-----

systemctl start ddclient.service
Job for ddclient.service failed. See "systemctl status ddclient.service" and
"journalctl -xn" for details.

Nov 02 20:43:38 tux ddclient[2829]: Use of uninitialized value $mode in bitwise
and (&) at /usr/sbin/ddclient line 1002.
Nov 02 20:43:38 tux ddclient[2829]: readline() on closed filehandle FD at
/usr/sbin/ddclient line 1014.
Nov 02 20:43:38 tux ddclient[2829]: stat() on closed filehandle FD at
/usr/sbin/ddclient line 1001.
Nov 02 20:43:38 tux ddclient[2829]: Use of uninitialized value $mode in bitwise
and (&) at /usr/sbin/ddclient line 1002.
Nov 02 20:43:38 tux ddclient[2829]: readline() on closed filehandle FD at
/usr/sbin/ddclient line 1014.
Nov 02 20:43:38 tux ddclient[2829]: WARNING:  file /etc/ddclient.conf: Cannot
open file '/etc/ddclient.conf'. (Permission denied)
Nov 02 20:43:38 tux ddclient[2829]: WARNING:  file /etc/ddclient.conf: Cannot
open file '/etc/ddclient.conf'. (Permission denied)
Nov 02 20:43:38 tux systemd[1]: Failed to start A Perl Client Used To Update
Dynamic DNS.


--1415018484.A21ca6B10.13651
Date: Mon, 3 Nov 2014 12:41:23 +0000
MIME-Version: 1.0
Content-Type: text/plain

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

            Bug ID: 903671
           Summary: hiawatha fails to start due to missing POLARSSL_THREADING_PTHREAD flag in polarssl
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2 RC 1
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: fisiu-at-opensuse.org
          Reporter: fisiu-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After installing hiawatha (9.7-2.2) package and dependencies, it fails to
start.

# systemctl status hiawatha
hiawatha.service - Hiawatha Web Server
   Loaded: loaded (/usr/lib/systemd/system/hiawatha.service; enabled)
   Active: failed (Result: exit-code) since pon 2014-11-03 11:29:25 CET; 1h
11min ago
 Main PID: 1184 (code=exited, status=1/FAILURE)

lis 03 11:29:25 pendrak hiawatha[1144]: Using /etc/hiawatha
lis 03 11:29:25 pendrak hiawatha[1144]: Reading hiawatha.conf
lis 03 11:29:25 pendrak hiawatha[1144]: No non-fatal errors found in the
Hiawatha configuration.
lis 03 11:29:25 pendrak hiawatha[1157]: Using /etc/hiawatha
lis 03 11:29:25 pendrak hiawatha[1157]: Reading hiawatha.conf
lis 03 11:29:25 pendrak hiawatha[1157]: Reading mimetype.conf
lis 03 11:29:25 pendrak hiawatha[1157]: Configuration OK.
lis 03 11:29:25 pendrak hiawatha[1184]: PolarSSL was compiled without the
required POLARSSL_THREADING_PTHREAD compiler flag.

Solution is to rebuild polarssl with enabled POLARSSL_THREADING_PTHREAD flag.