body:
The python-qt4 package in openSUSE 13.1 does not include phonon support because
the test for Phonon in the configure.py script fails because the path
/usr/include/QtGui as an include is not included in g++ command for compiling
the test so the build script thinks that Phonon is not supported, despite
phonon-devel being installed. The configure-ng.py script which uses qmake
properly adds the include path, so it does not have this issue. The best long
term solution would be to switch the package to use configure-ng.py but I don't
know if this would be allowed so close to the release. This change should be
made for factory so that it gets into the next release. The pyqt4 project
documentation recommends using configure-ng.py over configure.py
http://pyqt.sourceforge.net/Docs/PyQt4/installation.html#configuring-pyqt4.

The following is the build output when the --verbose flag is added to the
configure.py step showing the issue with the Phonon check.

[  170s] Checking to see if the phonon module should be built...
[  170s] g++ -DQT_PHONON_LIB -I. -I/usr/mkspecs/linux-g++ -I/usr/include/phonon
-I/usr/include -pipe -g -w -D_REENTRANT cfgtest_phonon.cpp -o cfgtest_phonon
-L/usr/lib64 -lpthread -ldl -lutil -lm -lpython2.7 -lphonon -lpthread
[  170s] In file included from cfgtest_phonon.cpp:1:0:
[  170s] /usr/include/phonon/videowidget.h:28:19: fatal error: QWidget: No such
file or directory
[  170s]  #include <QWidget>
[  170s]                    ^
[  170s] compilation terminated.
..
[  170s] These PyQt modules will be built: QtCore, QtGui, QtHelp, QtMultimedia,
[  170s] QtNetwork, QtDBus, QtDeclarative, QtScript, QtScriptTools, QtXml,
QtOpenGL,
[  170s] QtSql, QtSvg, QtTest, QtWebKit, QtXmlPatterns, QtDesigner.

Using configure-ng.py instead fixes the problem.

[  128s] Checking to see if the phonon module should be built...
[  128s] /usr/bin/qmake -o cfgtest_phonon.mk cfgtest_phonon.pro
[  128s] make -f cfgtest_phonon.mk
[  131s] g++ -c -pipe -g -Wall -W -D_REENTRANT -DQT_WEBKIT -DQT_PHONON_LIB
-DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/default -I.
-I/usr/include/QtCore -I/usr/include/QtGui -I/usr/include/phonon -I/usr/include
-I/usr/include/phonon_compat -I. -o cfgtest_phonon.o cfgtest_phonon.cpp
[  131s] g++  -o cfgtest_phonon cfgtest_phonon.o    -L/usr/lib64 -lphonon
-lQtGui -L/usr/lib64 -L/usr/X11R6/lib -lQtCore -lpthread
[  131s] { test -n "" && DESTDIR="" || DESTDIR=.; } && test $(gdb --version |
sed -e 's,[^0-9]\+\([0-9]\)\.\([0-9]\).*,\1\2,;q') -gt 72 && gdb --nx --batch
--quiet -ex 'set confirm off' -ex "save gdb-index $DESTDIR" -ex quit
'cfgtest_phonon' && test -f cfgtest_phonon.gdb-index && objcopy --add-section
'.gdb_index=cfgtest_phonon.gdb-index' --set-section-flags '.gdb_index=readonly'
'cfgtest_phonon' 'cfgtest_phonon' && rm -f cfgtest_phonon.gdb-index || true
[  131s] /bin/sh: gdb: command not found
[  131s] /bin/sh: line 0: test: -gt: unary operator expected
..
[  131s] These PyQt4 modules will be built: QtCore, QtGui, QtHelp,
QtMultimedia,
[  131s] QtNetwork, QtDeclarative, QtScript, QtScriptTools, QtXml, QtOpenGL,
QtSql,
[  131s] QtSvg, QtTest, QtWebKit, QtXmlPatterns, phonon, QtDesigner, QtDBus.

For some reason the test works fine on openSUSE 12.3 with the version of
python-qt4 in 12.3

[  181s] Checking to see if the phonon module should be built...
[  181s] g++ -DQT_PHONON_LIB -I. -I/usr/mkspecs/linux-g++ -I/usr/include/phonon
-I/usr/include -m64 -pipe -g -w -D_REENTRANT cfgtest_phonon.cpp -o
cfgtest_phonon -L/usr/lib64 -lpthread -ldl -lutil -lm -lpython2.7 -lphonon
-lpthread
..
[  225s] These PyQt modules will be built: QtCore, QtGui, QtHelp, QtMultimedia,
[  225s] QtNetwork, QtDBus, QtDeclarative, QtOpenGL, QtScript, QtScriptTools,
QtSql,
[  225s] QtSvg, QtTest, QtWebKit, QtXml, QtXmlPatterns, phonon, QtDesigner.

This bug currently prevents the OpenLP package from working as it requires
Phonon to work.

jdmulloy@linux-e8l2:~> openlp
Traceback (most recent call last):
  File "/usr/bin/openlp", line 31, in <module>
    from openlp.core import main
  File "/usr/lib/python2.7/site-packages/openlp/__init__.py", line 33, in
<module>
    import core
  File "/usr/lib/python2.7/site-packages/openlp/core/__init__.py", line 46, in
<module>
    from openlp.core.lib import Receiver, check_directory_exists
  File "/usr/lib/python2.7/site-packages/openlp/core/lib/__init__.py", line
399, in <module>
    from dockwidget import OpenLPDockWidget
  File "/usr/lib/python2.7/site-packages/openlp/core/lib/dockwidget.py", line
39, in <module>
    from openlp.core.ui import ScreenList
  File "/usr/lib/python2.7/site-packages/openlp/core/ui/__init__.py", line 82,
in <module>
    from maindisplay import MainDisplay, Display
  File "/usr/lib/python2.7/site-packages/openlp/core/ui/maindisplay.py", line
39, in <module>
    from PyQt4.phonon import Phonon
ImportError: No module named phonon

Reproducible: Always

summary: Phonon support missing from python-qt4 in openSUSE 13.1 - breaks OpenLP


body:
https://bugzilla.novell.com/show_bug.cgi?id=848963

https://bugzilla.novell.com/show_bug.cgi?id=848963#c0

           Summary: user cannot change nis password
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 2
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: YaST2
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: kukuk-at-suse.com
         QAContact: jsrain-at-suse.com
          Found By: Community User
           Blocker: ---

With the switch to pam_unix.so a change in yast2 nis-client is necessary:

if pam_unix.so is used (pam-config -q --unix), we need to add the nis keyword
to pam_unix.so if NIS will be enabled, and we need to remove it if it will be
disabled:
pam-config -a --unix-nis
and
pam-config -d --unix-nis

The bug exist already in openSUSE 12.3.

summary: user cannot change nis password


body:
https://bugzilla.novell.com/show_bug.cgi?id=849071

https://bugzilla.novell.com/show_bug.cgi?id=849071#c0

           Summary: Boot cycle
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 2
          Platform: x86-64
        OS/Version: openSUSE 12.2
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: werner-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: werner-at-suse.com, coolo-at-suse.de, fcrozat-at-suse.com
          Found By: Development
           Blocker: ---

This happens on a virtual system but may also happen on a normal system if
consoles are enabled and also I see several messages with

[ *** ] A start job is running for dev-disk-by\x2d

 ... I see after booting into rescue mode from the RC2 boot image and mounting
the root partition I have investigated /var/log/messages and /var/log/warn.

summary: Boot cycle


body:
When I enter a packed rar file with in midnight commander, if the RAR file
contains file or directory names with spaces, the file or directory names are
only displayed until the first space character.

Reproducible: Always

Steps to Reproduce:
Browse a .rar file in midnight commander where the rar file contains filenames
with spaces.
Actual Results:
The file names which are shown in midnight commander are trimmed at the first
space character.

Expected Results:
File names with spaces are shown correctly.

This used to work in openSuSE 12.3.

summary: midnight commander unrar plugin broken with filenames with spaces


body:
LibreOffice has moved on to using Python 3 for PyUNO, but the system Python on
openSUSE is still 2.7 so the exception handling code on line 336 of
/usr/lib/python2.7/site-packages/uno.py will crash because it tries to use
"with_traceback" on an exception, which is a Python 3 feature. I'll submit a
patch to fix this.

https://bugs.freedesktop.org/show_bug.cgi?id=69070

This is the Traceback generated when attempting to run OpenLP

  File "/usr/bin/openlp", line 44, in <module>
    main()
  File "/usr/lib/python2.7/site-packages/openlp/core/__init__.py", line 342, in
main
    sys.exit(app.run(qt_args))
  File "/usr/lib/python2.7/site-packages/openlp/core/__init__.py", line 150, in
run
    self.mainWindow = MainWindow(self)
  File "/usr/lib/python2.7/site-packages/openlp/core/ui/mainwindow.py", line
685, in __init__
    self.pluginManager.find_plugins(plugin_path, self.pluginHelpers)
  File "/usr/lib/python2.7/site-packages/openlp/core/lib/pluginmanager.py",
line 113, in find_plugins
    __import__(modulename, globals(), locals(), [])
  File "/usr/lib/python2.7/site-packages/uno.py", line 269, in _uno_import
    return _g_delegatee( name, *optargs, **kwargs )
  File "/usr/lib/python2.7/site-packages/openlp/plugins/bibles/bibleplugin.py",
line 38, in <module>
    from openlp.plugins.bibles.lib import BibleManager, BiblesTab,
BibleMediaItem
  File "/usr/lib/python2.7/site-packages/uno.py", line 269, in _uno_import
    return _g_delegatee( name, *optargs, **kwargs )
  File
"/usr/lib/python2.7/site-packages/openlp/plugins/bibles/lib/__init__.py", line
456, in <module>
    from manager import BibleManager
  File "/usr/lib/python2.7/site-packages/uno.py", line 269, in _uno_import
    return _g_delegatee( name, *optargs, **kwargs )
  File "/usr/lib/python2.7/site-packages/openlp/plugins/bibles/lib/manager.py",
line 47, in <module>
    from openlp1 import OpenLP1Bible
  File "/usr/bin/openlp", line 44, in <module>
    main()
  File "/usr/lib/python2.7/site-packages/openlp/core/__init__.py", line 342, in
main
    sys.exit(app.run(qt_args))
  File "/usr/lib/python2.7/site-packages/openlp/core/__init__.py", line 150, in
run
    self.mainWindow = MainWindow(self)
  File "/usr/lib/python2.7/site-packages/openlp/core/ui/mainwindow.py", line
685, in __init__
    self.pluginManager.find_plugins(plugin_path, self.pluginHelpers)
  File "/usr/lib/python2.7/site-packages/openlp/core/lib/pluginmanager.py",
line 113, in find_plugins
    __import__(modulename, globals(), locals(), [])
  File "/usr/lib/python2.7/site-packages/uno.py", line 269, in _uno_import
    return _g_delegatee( name, *optargs, **kwargs )
  File "/usr/lib/python2.7/site-packages/openlp/plugins/bibles/bibleplugin.py",
line 38, in <module>
    from openlp.plugins.bibles.lib import BibleManager, BiblesTab,
BibleMediaItem
  File "/usr/lib/python2.7/site-packages/uno.py", line 269, in _uno_import
    return _g_delegatee( name, *optargs, **kwargs )
  File
"/usr/lib/python2.7/site-packages/openlp/plugins/bibles/lib/__init__.py", line
456, in <module>
    from manager import BibleManager
  File "/usr/lib/python2.7/site-packages/uno.py", line 269, in _uno_import
    return _g_delegatee( name, *optargs, **kwargs )
  File "/usr/lib/python2.7/site-packages/openlp/plugins/bibles/lib/manager.py",
line 47, in <module>
    from openlp1 import OpenLP1Bible

Reproducible: Always

summary: LibreOffice PyUno crashes OpenLP by trying to use Python 3 feature


body:
https://bugzilla.novell.com/show_bug.cgi?id=849152

https://bugzilla.novell.com/show_bug.cgi?id=849152#c0

           Summary: Latest randr patches changes ABI
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Milestone 4
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: X.Org
        AssignedTo: bnc-team-xorg-bugs-at-forge.provo.novell.com
        ReportedBy: idonmez-at-suse.com
         QAContact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

https://build.opensuse.org/request/show/204958 adds a multitude of randr
patches which changes the RandR ABI. This breaks all versions of the nvidia
drivers.

A fix is available in https://build.opensuse.org/request/show/205808.

summary: Latest randr patches changes ABI


body:
https://bugzilla.novell.com/show_bug.cgi?id=849211

https://bugzilla.novell.com/show_bug.cgi?id=849211#c0

           Summary: anthy is broken on Emacs 24.3
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 2
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: tiwai-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

anthy, a Japanese input method, doesn't work on Emacs on openSUSE 13.1.

The culprit is the use of the deprecated function last-command-char.  It needs
to be replaced with last-command-event.

summary: anthy is broken on Emacs 24.3


body:
https://bugzilla.novell.com/show_bug.cgi?id=849258

https://bugzilla.novell.com/show_bug.cgi?id=849258#c0

           Summary: drop dummy testutf8
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: lnussel-at-suse.com
        ReportedBy: sbrabec-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: jsuchome-at-suse.com
          Found By: ---
           Blocker: ---

testutf8 no longer exists in its original UTF-8 testing form. The new
deprecated testutf8 is just a dummy and does no any UTF-8 detection.

All references to it should be dropped:
/etc/profile.d/csh.utf8 (aaa_base)
/etc/profile.d/sh.utf8 (aaa_base)
/usr/lib/YaST2/startup/common/language.sh (yast2-installation)

Then testutf8 can be dropped from kbd.

For discussion please look at bug 436378.

summary: drop dummy testutf8


https://bugzilla.novell.com/show_bug.cgi?id=849264

https://bugzilla.novell.com/show_bug.cgi?id=849264#c0

           Summary: debugreiserfs: crashes due to use-after-free with _MALLOC_PERTURB set
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 2
          Platform: Other
        OS/Version: Other
            Status: ASSIGNED
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: jeffm-at-suse.com
        ReportedBy: jeffm-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: Development
           Blocker: ---

Created an attachment (id=566378)
 --> (http://bugzilla.novell.com/attachment.cgi?id=566378)
[PATCH] debugreiserfs: fix use after free while closing log

reiserfs_close(fs) frees fs and we were using it after freeing to close the
log.

With _MALLOC_PERTURB set, this causes a crash.


https://bugzilla.novell.com/show_bug.cgi?id=849342

https://bugzilla.novell.com/show_bug.cgi?id=849342#c0

           Summary: mlterm cannot show Japanese characters as default
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 2
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: tiwai-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

mlterm cannot show any Japanese characters as default unless you set up the
font manually.

The culprit is the recent change in the upstream code to query the fixed font
at first.

https://bitbucket.org/arakiken/mlterm/commits/b55a26f18f5f63804040b8d3cbcbf46f8868a67d

This changes not only using the fixed font but also checking only "c" spacing.
Unfortunately most of biwidth fonts (e.g. efont-unicode) don't give c but only
p spacing.  Thus, with this change, these fonts won't hit any longer but a
wrong font is picked up in the end.

A possible fix is either to fall back to efont for biwidth fonts just like
doing for gnu-unifont.  But this is ugly.

Another fix is to probe other spacing variants for biwidth unicode fonts.  This
works, but if gnu-unifont is in the font path, gnu-unifont will be picked up
even if it doesn't match with the actual pixel size by X server side resizing.
This results in badly shaped glyphs.

Though, gnu-unifont-bitmap-fonts is installed in /usr/share/fonts/uni/ and this
path isn't included in the default font path, thus the problem won't happen as
default.  If any user changes the font path, it's user's responsibility, so we
don't have to care so much, too.


body:
After the last security update of the following packages this error occurs:

libopenssl1_0_0-1.0.1e-2.8.1.x86_64 -> 2.12.1.x86_64
libopenssl1_0_0-32bit-1.0.1e-2.8.1.x86_64 -> 2.12.1.x86_64
openssl-1.0.1e-2.8.1.x86_64 -> 2.12.1.x86_64

kernel: [1309662.907438] sudo[6512]: segfault at 0 ip 00007fd3771a4f79 sp
00007fff3fc9ebd0 error 4 in libssl.so.1.0.0[7fd37715d000+60000]

any sudo command can=C2=B4t be executed anymore

Please ask if you need more information
Thanks

Reproducible: Always

Steps to Reproduce:
1.After downgrading the version again, it works ok. Not a good workaround
because this are are security fixes.
2.
3.

--=20
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=3Demail
-----

summary: segfault in libssl.so.1.0.0 after security upgrade of openssl/libopenssl


body:
https://bugzilla.novell.com/show_bug.cgi?id=849378

https://bugzilla.novell.com/show_bug.cgi?id=849378#c0

           Summary: Incorrect cmake policy behaviour
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Development
        AssignedTo: vcizek-at-suse.com
        ReportedBy: vcizek-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

We've received an email from cmake developers:

> Subject: CMake 2.8.12.1
> Date: Wed, 06 Nov 2013 14:26:51 -0500
> From: Brad King <brad.king-at-kitware.com>
>
> FYI, I've just tagged this bugfix release:
>
>  http://cmake.org/gitweb?p=cmake.git;a=tag;h=v2.8.12.1
>  http://www.cmake.org/files/v2.8/cmake-2.8.12.1.tar.gz
>
> Most importantly, it was discovered that 2.8.12.0 had a bad
> implementation of a CMake Policy it introduced: CMP0022.
> This is the worst kind of bug because the fix causes a change
> in behavior for projects in a way that is incompatible with
> 2.8.12.0 (but still compatible with 2.8.11.2 and lower).
>
> Therefore we need to get 2.8.12.0 replaced with 2.8.12.1
> as soon as possible to prevent anyone from depending on
> the former's incorrect behavior.
>
> Thanks,
> -Brad

summary: Incorrect cmake policy behaviour


body:
Hi

As you see logrotate runs every day 17:00:

$ xzcat /var/log/messages-201311*.xz | grep logrotate
2013-10-30T17:00:01.315236+01:00 tenfore run-crons[12489]: logrotate: OK
2013-10-31T17:00:01.971270+01:00 tenfore run-crons[10404]: logrotate: OK
2013-11-01T17:00:02.656443+01:00 tenfore run-crons[21323]: logrotate: OK
2013-11-02T17:00:01.317445+01:00 tenfore run-crons[7495]: logrotate: OK
2013-11-03T17:00:01.810987+01:00 tenfore run-crons[23194]: logrotate: OK
2013-11-04T17:00:02.052003+01:00 tenfore run-crons[1316]: logrotate: OK
2013-11-05T17:00:01.174979+01:00 tenfore run-crons[10312]: logrotate: OK
2013-11-06T17:00:01.746856+01:00 tenfore run-crons[15202]: logrotate: OK

Today (20131107) /var/log/messages was rotated, but the new one is still empty:
$ date
Thu Nov  7 18:53:04 CET 2013
$ ls -l /var/log/messages-20131*.xz /var/log/messages
-rw-r---

summary: logrotate syslog breaks /var/log/messages


https://bugzilla.novell.com/show_bug.cgi?id=849476

https://bugzilla.novell.com/show_bug.cgi?id=849476#c0

           Summary: /etc/init.d/nfsserver fails to start because -nfs-version needs 2 hyphens
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: x86-64
        OS/Version: SUSE Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: jimc-at-math.ucla.edu
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Package: nfs-kernel-server-1.2.8-4.2.1.x86_64

When you do /etc/init.d/nfsserver start, rpc.mountd exits printing its
usage message.  The reason is that VERSION_PARAMS is set to -nfs-version 4
where it should be --nfs-version 4 (2 hyphens).  Patch coming.

Also, if NFS4_SERVER_MINOR_VERSION != '0', i.e. if it is unset
(as it was in my case due to copying /etc/sysconfig/nfs from v12.3),
the option -nfs-version 4. (four dot) will be appended.  rpc.mountd does
not care, but rpc.nfsd chokes on it, "unsupported minor version".  May I
suggest a case statement such as:
case "$NFS4_SERVER_MINOR_VERSION" in
[1-9]* ) (append the minor version option)
esac


body:
On a system newly upgraded to 13.1rc2, I noticed mdadmd was running despite
/etc/mdadm.conf being non-existent and no RAID arrays being present. It seems
pretty odd for it to be started to monitor nothing.  When I asked on
opensuse-factory, this was part of the answer:

> Package mdadmd is installed as a dependency of package libstorage4,
> which is dependency by autoyast and yast-backup

I don't know if this is a YaST issue, but I'll start with you guys.

Reproducible: Always

summary: mdadmd running superfluously


https://bugzilla.novell.com/show_bug.cgi?id=849587

https://bugzilla.novell.com/show_bug.cgi?id=849587#c0

           Summary: QEMU Gtk GUI doesn't grab mouse properly
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KVM
        AssignedTo: kvm-bugs-at-forge.provo.novell.com
        ReportedBy: tiwai-at-suse.com
         QAContact: jdouglas-at-suse.com
          Found By: ---
           Blocker: ---

Since openSUSE 13.1, qemu gtk interface is used as default, and I noticed that
the mouse pointer grab doesn't work properly.

When the input is grabbed via ctrl-alt-G, both the key focus and the mouse are
grabbed to the qemu window.  Then move your mouse, and you'll see the pointer
stops moving at some point suddenly.  It starts moving again when you move the
mouse backward to some point.

It seems that the X mouse pointer isn't actually fully grabbed but it's only
invisible.  When the (invisible) X pointer goes over the qemu window, qemu
loses the mouse input, thus the mouse pointer in qemu window freezes.  When the
X pointer comes back to the position of qemu window, the mouse pointer in qemu
starts moving again, too.

The problem isn't seen in SDL UI.  It grabs the X pointer, and after releasing
the grab, X pointer re-appears at the same place it was grabbed.

The behavior might depend on DE.  My system is with XFCE.


body:
[Applies to all versions of netatalk up to 3.1.0]

When using "ad mv" like so:

ad mv /Volume/Path/File /Volume/Path/Target/File

where the afp volume path is "/Volume/Path" and all files and dirs exist, an
error is generated with the following error message:

Nov 08 15:13:31.369557 [1717] {ad_util.c:360} (E:Default): lstat(rpath:
Target/File, elem: CanvasScripts): /Volume/PathTarget/File: No such file or
directory
Couldn't resolve CNID for parent of /Volume/PathTarget/File

Seemingly this is only an error message, otherwise the command works and
resource forks seem to be correctly moved. Still it is annoying.

The reason is, that cnid_for_paths_parent(...) (in ad_utils.c) splits the path
into the volume (base) path [here /Volume/Path ] and the relative path to the
target [Target/File]. The relative path is then split into path components and
every component is then in a loop concatenated to a statpath (initially set to
the volume path) to retrieve (and set?) the correct parent CNIDs. Within the
loop the statpath gets a "/" appended _after_ the relative path component is
appended to statpath. This fails since the initial value of statpath is e.g.
"/Volume/Path" without a trailing "/". The attached patch moves the call to
"EC_ZERO(bcatcstr(statpath, "/"));" to the start of the loop, fixing the error
generation.

Additionally, "EC_NULL(statpath = bfromcstr(vol->volinfo.v_path));" was moved
after the "if (l->qty==1)....", because the loop is only entered for l->qty!=1
and only then statpath is used.

I reported the same error over at netatalk.sf.net.

Reproducible: Always

Steps to Reproduce:
1. have a target directory for an "ad mv" which is a sub-directory of the
volume path
2. use ad mv (like above)
3. error message is generated

Expected Results:
the program should silently work

Applies to all versions of netatalk up to 3.1.0 and thus all versions of
netatalk in openSuSE

summary: utility program ad fails under certain conditions, because cnid_for_paths_parent(...) (ad_utils.c) handles path concatenation wrongly


Chrome has been updated to 30.0.1599.114 for Windows, Mac, Linux and Chrome
Frame.=20

 Security Fixes and Rewards

 Note: Access to bug details and links may be kept restricted until a major=
ity
of users are updated with a fix. We will also retain restrictions if the bug
exists in a third party library that other projects similarly depend on, but
haven=E2=80=99t yet fixed.

 This update includes 5 security fixes. Below, we highlight fixes that were
either contributed by external researchers or particularly interesting. Ple=
ase
see the Chromium security page for more information.=20

 [$1000][292422] High CVE-2013-2925: Use after free in XHR. Credit to Atte
Kettunen of OUSPG.
[$2000][294456] High CVE-2013-2926: Use after free in editing. Credit to
cloudfuzzer.
[$2000][297478] High CVE-2013-2927: Use after free in forms. Credit to
cloudfuzzer.

 As usual, our ongoing internal security work responsible for a wide range =
of
fixes:
[305790] CVE-2013-2928: Various fixes from internal audits, fuzzing and oth=
er
initiatives.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

--=20
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=3Demail
-----


body:
Installed at-3.1.13-5.1.2.i586 rpm. Added user 'guest' to /etc/at.deny. Tried
to execute an "at" command but it immediately exited with error "Cannot create
atjob file /var/spool/atjobs/a0000a015ff720: Permission denied". Ran the
command again using strace:

 sudo strace -u myuser -o /tmp/x.log /usr/bin/at 0000

The tail of the strace output shows that an open system call is failing with
EACCES:
 open("/var/spool/atjobs/a0000a015ff720", O_WRONLY|O_CREAT|O_EXCL|O_TRUNC,
0400) = -1 EACCES (Permission denied)

Related file permissions and /etc/at.deny contents:
#sudo ls -ld /usr/bin/at /var/spool/atjobs/
-rwsr-xr-x 1 root trusted 51156 Sep 27 17:22 /usr/bin/at
drwx----

summary: "at" command immediately exit with: Cannot create atjob file /var/spool/atjobs/...: Permission denied


body:
Due to changes in kwalletmanager for KDE's 4.12 release, we're requesting
whitelisting the following:

kwalletmanager.i586: E: suse-dbus-unauthorized-service (Badness: 100)
/usr/share/dbus-1/system-services/org.kde.kcontrol.kcmkwallet.service
kwalletmanager.i586: E: suse-dbus-unauthorized-service (Badness: 100)
/etc/dbus-1/system.d/org.kde.kcontrol.kcmkwallet.conf
The package installs a DBUS system service file. If the package is intended
for inclusion in any SUSE product please open a bug report to request review
of the service by the security team.

kwalletmanager.i586: E: polkit-unauthorized-privilege (Badness: 100)
org.kde.kcontrol.kcmkwallet.save (??:no:auth_self_keep)
The package allows unprivileged users to carry out privileged operations
without authentication. This could cause security problems if not done
carefully. If the package is intended for inclusion in any SUSE product please
open a bug report to request review of the package by the security team

kwalletmanager.i586: I: polkit-cant-acquire-privilege
org.kde.kcontrol.kcmkwallet.save (??:no:auth_self_keep)
Usability can be improved by allowing users to acquire privileges via
authentication. Use e.g. 'auth_admin' instead of 'no' and make sure to define
'allow_any'. This is an issue only if the privilege is not listed in /etc
/polkit-default-privs.*

Changes are introduced with this commit:
http://quickgit.kde.org/?p=kwallet.git&a=commit&h=717f925b77f13c54e92ecd81ea92487f933a1915

Reproducible: Always

pkgs: polkit-default-privs rpmlint

summary: AUDIT-0: kwalletmanager: Security Review requested due to suse-dbus-unauthorized-service, polkit-untracked-privilege and polkit-cant-acquire-privilege


body:
When I try to connect with rdp session I receive following error:

rdesktop -f -k de localhost:3389

Failed to negotiate protocol, retrying with plain RDP.
WARNING: Remote desktop changed from 1920x1080 to 1920x1075.
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Resource id in failed request:  0x0
  Serial number of failed request:  38
  Current serial number in output stream:  42

Reproducible: Always

Steps to Reproduce:
1. rdesktop -f -k de localhost:3389
2.
3.
Actual Results:
Failed to negotiate protocol, retrying with plain RDP.

It worked with openSUSE 12.3.

It also works when I downgrade rdesktop to version 1.7.0

summary: rdesktop fails to negotiate protocol when trying to connect to RDP session (Virtualbox)


body:
If you try to start IPython console within Spyder you get the following
message:

"""
Unable to open IPython console because no supported IPython version was found.
Supported IPython versions: >=0.13 and <1.0
Installed version: 1.0.0
"""

Reproducible: Always

Steps to Reproduce:
1. Start Spyder with IPython console enabled
2. Message "Unable to open IPython console..." appears
3.
Actual Results:
IPython console doesn't start

Expected Results:
IPython console should start

summary: IPython console doesn't start


body:
Quasselcore (the backend of the quassel irc client) because of an error in the
systemd startup file (/usr/lib/systemd/system/quasselcore.service:

[Unit]
Description=Quassel Core
After=network.target
EnvironmentFile=-/etc/sysconfig/quasselcore

[Service]
PIDFile=/var/run/quassel.pid
User=quasselcore
ExecStart=/usr/bin/quasselcore --listen=$QUASSELCORE_LISTEN
--configdir=/var/lib/quasselcore --logfile=/var/log/quassel/quasselcore

[Install]
WantedBy=multi-user.target

Error in systemlog:

quasselcore[31344]: Invalid listen address $QUASSELCORE_LISTEN

which hints to the fact that QUASSELCORE_LISTEN isn't correctly expanded.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: quasselcore fails to start


body:
https://bugzilla.novell.com/show_bug.cgi?id=849870

https://bugzilla.novell.com/show_bug.cgi?id=849870#c0

           Summary: systemd --user keeps running for logged out user
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: wolfgang-at-rosenauer.org
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I've seen this in connection with gdm/Gnome but not sure if that is related.

1. created a testuser to verify some other bug
2. logged into Gnome
3. logged out of Gnome
4. remove the testuser from system using yast or userdel

Result:
User cannot be removed since it still is logged in.
The process which still runs as that user is:
systemd --user

pkgs: shadow systemd


body:
Handover from the "ast" kernel module to the "ast" X11 driver fails, causing
X11 and kdm to fail. From what I read elsewhere, one of the ast components
doesn't implement the handover interface correctly. However, there's a simple
workaround, see below.

Reproducible: Always

Steps to Reproduce:
1. install on hardware with a video card served by the "ast" driver, for
example the Aspeed AST1300 used on some ASUS server mainboards
2. boot (or run init 3 followed by init 5)

Actual Results:
X11 / kdm doesn't start; xorg error log says that the video driver "cannot
operate" because "[t]he PCI device" xyz "has a kernel module claiming it".

Expected Results:
X11 / kdm starts

Workaround:
 * add "nomodeset" to kernel parameters (this may be enough on its own but I
also did the following)
 * add "ast" as a device in X11 / xorg config
 * remove plymouth (remove 1st search result in software management and then
select removal of around 10-20 other packages)

Note: the issue has been discussed in forums for older versions, for example
http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/486588-12-3-graphic-display-issues-2.html

summary: ast kernel module blocks x11 in 13.2 RC 2


body:
https://bugzilla.novell.com/show_bug.cgi?id=849913

https://bugzilla.novell.com/show_bug.cgi?id=849913#c0

           Summary: Updat to GNOME 3.10.2
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
        AssignedTo: bnc-team-gnome-at-forge.provo.novell.com
        ReportedBy: dimstar-at-opensuse.org
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

GNOME 3.10.2 is being released 'at the moment' and shall be ready by November
20.

Collecting information here to assess / justify an online update to 3.10.2

summary: Updat to GNOME 3.10.2


body:
Privoxy fails to start in opensuse 13.1 because it's not chrooted properly.
Corrected /usr/lib/systemd/system/privoxy.service is in attachment. Original
file also has executable bit set after package installation.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: privoxy fails to start in openSUSE 13.1


https://bugzilla.novell.com/show_bug.cgi?id=850083

https://bugzilla.novell.com/show_bug.cgi?id=850083#c0

           Summary: BT: failure sending a file from a phone to GNOME Desktop
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
        AssignedTo: bnc-team-gnome-at-forge.provo.novell.com
        ReportedBy: dimstar-at-opensuse.org
         QAContact: qa-bugs-at-suse.de
                CC: tittiatcoke-at-gmail.com, juan.ehrenhaus-at-gmail.com,
                    alinm.elena-at-gmail.com, jcheung-at-suse.com,
                    seife-at-novell.slipkontur.de, hrvoje.senjan-at-gmail.com
            Blocks: 844041
          Found By: ---
           Blocker: ---

Using the bluez5 stack, it is possible to send a file from openSUSE to the BT
phone, but not the other way around.


https://bugzilla.novell.com/show_bug.cgi?id=850225

https://bugzilla.novell.com/show_bug.cgi?id=850225#c0

           Summary: less leaves /tmp/less.* files when showing patch files
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: tiwai-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The less program leaves /tmp/less.* temporary files after quitting from viewing
patch files.

The problem happens if no colordiff program is installed.  Then lessopen.sh
fallback to TMPF="$TMPF_pre" but it forgot to delete the previous $TMPF.


body:
https://bugzilla.novell.com/show_bug.cgi?id=850258

https://bugzilla.novell.com/show_bug.cgi?id=850258#c0

           Summary: RN: openSUSE 13.1 update wanted
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: Other
        OS/Version: Other
            Status: ASSIGNED
          Severity: Normal
          Priority: P5 - None
         Component: Release Notes
        AssignedTo: ke-at-suse.com
        ReportedBy: ke-at-suse.com
         QAContact: coolo-at-suse.com
          Found By: Documentation
           Blocker: ---

Collecting bugs...

summary: RN: openSUSE 13.1 update wanted


body:
pip seems to have a problem with urllib. It gives the following traceback:

Traceback (most recent call last):
  File "/usr/bin/pip", line 9, in <module>
    load_entry_point('pip=3D=3D1.4', 'console_scripts', 'pip-3.3')()
  File "/usr/lib/python3.3/site-packages/pkg_resources.py", line 378, in
load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3.3/site-packages/pkg_resources.py", line 2566, in
load_entry_point
    return ep.load()
  File "/usr/lib/python3.3/site-packages/pkg_resources.py", line 2260, in l=
oad
    entry =3D __import__(self.module_name, globals(),globals(), ['__name__'=
])
  File "/usr/lib/python3.3/site-packages/pip/__init__.py", line 11, in <mod=
ule>
    from pip.vcs import git, mercurial, subversion, bazaar  # noqa
  File "/usr/lib/python3.3/site-packages/pip/vcs/mercurial.py", line 9, in
<module>
    from pip.download import path_to_url2
  File "/usr/lib/python3.3/site-packages/pip/download.py", line 147, in
<module>
    class VerifiedHTTPSHandler(urllib.request.HTTPSHandler):
AttributeError: 'module' object has no attribute 'request'

Reproducible: Always

Steps to Reproduce:
1. install python3-pip
2. launch pip with =C2=B4pip=C2=B4 or =C2=B4pip-3.3=C2=B4
3. enjoy traceback
Actual Results:=20=20
pip crashes, the traceback given above appears.

Expected Results:=20=20
pip should work and display a help

I'm using a fully-updated openSUSE 13.1 RC2 with python 3.3.2-5.1.3 and
python3-pip 1.4-3.1.3

--=20
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=3Demail
-----

summary: python3-pip crashes because of urllib problem


body:
/var/log/messages shows:

Nov 13 21:51:19 db046 kernel: [ 3659.370852] type=1400
audit(1384379479.255:32): apparmor="DENIED" operation="mknod" parent=1
profile="/usr/sbin/ntpd" name="/var/lib/ntp/drift/driftfile.TEMP" pid=4682
comm="ntpd" requested_mask="c" denied_mask="c" fsuid=74 ouid=74

/var/log/ntp shows:

13 Nov 21:51:19 ntpd[4682]: frequency file /var/lib/ntp/drift/driftfile.TEMP:
Permission denied
13 Nov 22:51:19 ntpd[4682]: frequency file /var/lib/ntp/drift/driftfile.TEMP:
Permission denied
13 Nov 23:51:19 ntpd[4682]: frequency file /var/lib/ntp/drift/driftfile.TEMP:
Permission denied
14 Nov 00:51:19 ntpd[4682]: frequency file /var/lib/ntp/drift/driftfile.TEMP:
Permission denied

Checking /etc/apparmor.d/usr.sbin.ntpd lists the file
/var/lib/ntp/drift/ntp.drift.TEMP but not the file
/var/lib/ntp/drift/driftfile.TEMP.

Adding /var/lib/ntp/drift/driftfile.TEMP to /etc/apparmor.d/usr.sbin.ntpd at
line 50 solves the problem.

Reproducible: Always

Steps to Reproduce:
1. Install OpenSUSE 12.3
2. Check /var/log/messages and /var/log/ntp for the error
4. Profit!
Actual Results:
ntpd cannot write to the temporary driftfile.

Expected Results:
ntpd working as designed.

You just need to add /var/lib/ntp/drift/driftfile.TEMP to
/etc/apparmor.d/usr.sbin.ntpd to fix the issue.

summary: Apparmor config keeps ntpd from updating /var/lib/ntp/drift/driftfile.TEMP


body:
NET CLR 3.5.30729; OfficeLiveConnector.1.3; OfficeLivePatch.0.0; .NET4.0C;
NET4.0E)

After investigation I found out that this is becouse in
/lib/udev/rules.d/97-bluetooth-hid2hci.rule
KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct
shoudl be chaned with
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct
This is verry annoyng becouse you can not do anything exept to restart in
rescue mode and make some console repair.

Reproducible: Always

Steps to Reproduce:
1. Use Logitech HID mx5500
2. Install suse
3. reboot

summary: When you install OpenSuse 13.1 the Logitech MX5500 (bluetooth) mouse and kaybord stop responding


body:
On RC2, I tried to add a remote Samba printer using Yast2 and CUPS, but it
always failed with the error 'lpadmin: Bad device-uri scheme "smb".

The remote printer is served by a Seagate GoFlex Home Samba Server. There is no
problem adding and using the same SMB printer from openSUSE 12.3 (and Win/XP)
clients.

I found this problem and a workaround discussed on the French and English
forums. Here's a post from the English forum summarizing the problem and
workaround:
http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/491872-connecting-samba-printer-opensuse-13-1-a.html#post2595697

As this post puts it, "For some reason samba-client doesn't create the symbolic
link to smbspool in /usr/lib/cups/backend/smb."  The workaround is to create
the symlink manually.

No one else seems to have reported this problem; but, I thought you'd want to
know.

Reproducible: Always

Steps to Reproduce:
Try to add a remote Samba printer using Yast2's "Add a New Printer
Configuration"
1. Enter printer information
2. Click [OK] button
Actual Results:
Printer is not added.
Error: lpadmin: Bad device-uri scheme "smb"

Expected Results:
Printer added successfully

Not sure if the problem is related to the type or version of the SMB printer
server. IIRC, the Seagate GoFlex Home is running Samba version 3.0??, but not
I'm not certain. Sorry, I don't have access to the GoFlex now, to verify the
version number. As soon as I have access, I'll post the full version number.

summary: Trying to add a remote Samba printer gets 'lpadmin: Bad device-uri scheme "smb".'


https://bugzilla.novell.com/show_bug.cgi?id=850675

https://bugzilla.novell.com/show_bug.cgi?id=850675#c0

           Summary: Regression: Mobile Broadband Module not detected and not offered in NetworkManager
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: x86-64
        OS/Version: openSUSE 13.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
        AssignedTo: oneukum-at-suse.com
        ReportedBy: holgi-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: bili-at-suse.com
          Found By: Component Test
           Blocker: ---

With the last openSUSE versions my (build in) Mobile Broadband Modem
was detected automatically and I could just use it in NetworkManager after
installation. Now it seem that it is not recognized during installation and not
configured. Here are some details about the device:

54: USB 00.1: 10200 Modem
  [Created at usb.122]
  Unique ID: 50SH.dKnPvxQA6r2
  Parent ID: uIhY.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.1
  SysFS BusID: 3-4:1.1
  Hardware Class: modem
  Model: "Ericsson Business Mobile Networks BV H5321 gw"
  Hotplug: USB
  Vendor: usb 0x0bdb "Ericsson Business Mobile Networks BV"
  Device: usb 0x1926 "H5321 gw"
  Serial ID: "6325D4B28FF64BM0"
  Driver: "cdc_acm"
  Driver Modules: "cdc_acm"
  Device File: /dev/ttyACM0
  Device Files: /dev/ttyACM0,
/dev/serial/by-id/usb-Lenovo_H5321_gw_6325D4B28FF64BM0-if01,
/dev/serial/by-path/pci-0000:00:14.0-usb-0:4:1.1
  Speed: 480 Mbps
  Init1: ATZ
  Init2: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
  Module Alias: "usb:v0BDBp1926d0000dc00dsc00dp00ic02isc02ip01in01"
  Driver Info #0:
    Driver Status: cdc_acm is active
    Driver Activation Cmd: "modprobe cdc_acm"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #50 (Hub)


body:
From https://svn.apache.org/repos/asf/subversion/tags/1.8.5/CHANGES

Version 1.8.5
(25 November 2013, from /branches/1.8.x)
http://svn.apache.org/repos/asf/subversion/tags/1.8.5

 User-visible changes:
  - Client-side bugfixes:
    * fix externals that point at redirected locations (issues #4428, #4429)
    * diff: fix assertion with move inside a copy (issue #4444)

  - Server-side bugfixes:
    * mod_dav_svn: Prevent crashes with some 3rd party modules (r1537360 et al)
    * mod_dav_svn: canonicalize paths properly (r1542071)
    * mod_authz_svn: fix crash of mod_authz_svn with invalid config (r1541432)
    * hotcopy: fix hotcopy losing revprop files in packed repos (issue #4448)

  - Other tool improvements and bugfixes:
    * mod_dontdothat: Fix the uri parser (r1542069 et al)

 Developer-visible changes:
  - General:
    * fix compilation with '--enable-optimize' with clang (r1534860)
    * fix copmpilation with debug build of BDB on Windows (r1501656, r1501702)
    * fix '--with-openssl' option when building on Windows (r1535139)
    * add test to fail when built against broken ZLib (r1537193 et al)

  - Bindings:
    * swig-rb: fix tests to run without installing on OS X (r1535161)
    * ctypes-python: build with compiler selected via configure (r1536537)

from https://svn.apache.org/repos/asf/subversion/tags/1.7.14/CHANGES

Version 1.7.14
(25 Nov 2013, from /branches/1.7.x)
http://svn.apache.org/repos/asf/subversion/tags/1.7.14

 User-visible changes:
  - Client- and server-side bugfixes:
    * fix assertion on urls of the form 'file://./' (r1516806)

  - Client-side bugfixes:
    * upgrade: fix an assertion when used with pre-1.3 wcs (r1530849)
    * ra_local: fix error with repository in Windows drive root (r1518184)
    * fix crash on windows when piped command is interrupted (r1522892)
    * fix externals that point at redirected locations (issues #4428, #4429)
    * diff: fix incorrect calculation of changes in some cases (issue #4283)
    * diff: fix errors with added/deleted targets (issues #4153, #4421)

  - Server-side bugfixes:
    * mod_dav_svn: Prevent crashes with some 3rd party modules (r1537360 et al)
    * fix OOM on concurrent requests at threaded server start (r1527103 et al)
    * fsfs: limit commit time of files with deep change histories (r1536790)
    * mod_dav_svn: canonicalize paths properly (r1542071)

  - Other tool improvements and bugfixes:
    * mod_dontdothat: Fix the uri parser (r1542069 et al)

 Developer-visible changes:
  - Bindings:
    * javahl: canonicalize path for streamFileContent method (r1524869)

Reproducible: Didn't try

summary: Apache Subversion 1.8.5 and 1.7.14 maintenance releases


body:
https://bugzilla.novell.com/show_bug.cgi?id=850792

https://bugzilla.novell.com/show_bug.cgi?id=850792#c0

           Summary: ibus: ibus-setup cannot start
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: GNOME
        AssignedTo: ftake-at-geeko.jp
        ReportedBy: jengelh-at-inai.de
         QAContact: qa-bugs-at-suse.de
                CC: i-at-marguerite.su
          Found By: Beta-Customer
           Blocker: ---

When attempting to start ibus-setup, some python code fails.

$ ibus-setup
Traceback (most recent call last):
  File "/usr/share/ibus/setup/main.py", line 28, in <module>
    from gi.repository import Gio
ImportError: No module named gi.repository

This happens because there is no python-gobject package installed in my system,
but ibus requires this.

summary: ibus: ibus-setup cannot start


body:
https://bugzilla.novell.com/show_bug.cgi?id=850807

https://bugzilla.novell.com/show_bug.cgi?id=850807#c0

           Summary: fprintd broken
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: abonilla-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: Field Engineer
           Blocker: ---

After a few attempts to get everything working fine, which did. I decided to
upgrade all packages which brought me to a broken pam_fprintd

# fprintd-enroll
list_devices failed: Unit fprintd.service failed to load: No such file or
directory.

pam_fprint-32bit-0.2-19.1.x86_64              Fri Nov 15 21:56:09 2013
pam_fprint-0.2-19.1.x86_64                    Fri Nov 15 21:56:09 2013
libfprint0-0.5.1-45.1.x86_64                  Fri Nov 15 21:56:09 2013

summary: fprintd broken


body:
rt.jar provided by java-1_7_0-openjdk (version 1.7.0.6-24.2.1) is missing the
class: sun/net/www/protocol/http/HttpCallerInfo

This makes applications that use this class fail at runtime with a
java.lang.NoClassDefFoundError: sun/net/www/protocol/http/HttpCallerInfo

The problem described in bug 850731 (
https://bugzilla.novell.com/show_bug.cgi?id=850731 ) could have this as a
cause, but I have not tested it.

Reproducible: Always

Steps to Reproduce:
1. Install java-1_7_0_openjdk with zypper
2. unzip -l /usr/lib64/jvm/java-1.7.0-openjdk-1.7.0/jre/lib/rt.jar | grep
sun/net/www/protocol/http/HttpCallerInfo | wc -l

Expected Results:
1

If i try to run the same test against a rt.jar that i have copied from a
centos6 installation, the file is there:

unzip -l /tmp/rt.jar | grep sun/net/www/protocol/http/HttpCallerInfo | wc -l
1

summary: rt.jar provided by java-1_7_0-openjdk is missing the class: sun/net/www/protocol/http/HttpCallerInfo


body:
After 2 Years it is time to change to the correct Variables ;)

OLD krb5_kdcip (depcreated)

NEW krb5_server

Also the krb5_kpasswd Variable is not set :(.

It can be set to krb5_server

This Problem fill up only the sssd_default.log

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: Old SSSD Variable in YaST Config


body:
13.1's phonon-backend-vlc requires vlc-noX = 2.1.0.

But VLC got updated to 2.1.1 yesterday, both in Packman and in the VideoLAN
repos.
So it's impossible now to use phonon-backend-vlc with VLC from those repos to
get full multimedia support because of dependency conflicts. You have to stay
with the included VLC version 2.1.0 and can't even play mp3s.

Personally I updated to vlc 2.1.1 by telling YaST to ignore the conflict, and
everything still works fine.
So I think this dependency should just be relaxed, it doesn't seem to be
necessary to require the exact version.

Reproducible: Always

summary: phonon-backend-vlc's requirement on vlc-noX is too strict


body:
curl has not been built with metalink support, despite supporting it and the
metalink library being available in openSUSE.  Please revisit this and enable
metalink support.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: curl not built with metalink support


body:
My openSUSE installation uses Active Directory domain authentication,
configured through YaST. This installation already worked correctly since
v12.1.
Today I upgraded from 12.3 to 13.1 using instructions from
https://en.opensuse.org/SDB:System_upgrade

After reboot I could no longer login using my AD domain account.

Initially journalctl showed me:
nov 19 14:18:09 ********* winbindd[3563]: [2013/11/19 14:18:09.009167,  0]
./lib/util/debug.c:595(reopen_logs_internal)
nov 19 14:18:09 ********* winbindd[3563]: Unable to open new log file
'/var/log/samba/log.winbindd-dc-connect': Permission denied
nov 19 14:18:09 ********* kernel: type=1400 audit(1384867089.008:35):
apparmor="DENIED" operation="open" parent=3243 profile="/usr/sbin/winbindd"
name="/var/log/samba/log.winbindd-dc-connect" pid=3563 comm="winbindd"
requested_mask="c" denied_mask="c" fsuid=0 ouid=0
nov 19 14:18:19 ********* winbindd[3286]: [2013/11/19 14:18:19.013899,  0]
./source3/libads/kerberos_util.c:74(ads_kinit_password)
nov 19 14:18:19 ********* winbindd[3286]: kerberos_kinit_password
*********$@********* failed: Permission denied
nov 19 14:18:19 ********* kernel: type=1400 audit(1384867099.013:36):
apparmor="DENIED" operation="open" parent=3243 profile="/usr/sbin/winbindd"
name="/var/lib/samba/smb_krb5/krb5.conf.***" pid=3286 comm="winbindd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
nov 19 14:18:19 ********* kernel: type=1400 audit(1384867099.013:37):
apparmor="DENIED" operation="open" parent=3243 profile="/usr/sbin/winbindd"
name="/var/lib/samba/smb_krb5/krb5.conf.***" pid=3286 comm="winbindd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0

After changing
  /var/log/samba/log.winbindd-dc-connect c,
into
  /var/log/samba/log.winbindd-dc-connect w,
in the apparmor profile /etc/apparmor.d/usr.sbin.winbindd

I now had these winbind-related errors:
nov 19 14:38:23 ********* winbindd[4342]: [2013/11/19 14:38:23.539361,  0]
./source3/lib/util_sec.c:103(assert_uid)
nov 19 14:38:23 ********* winbindd[4342]: Failed to set uid privileges to
(-1,39756) now set to (0,0)
nov 19 14:38:23 ********* winbindd[4342]: [2013/11/19 14:38:23.539444,  0]
./source3/lib/util.c:785(smb_panic_s3)
nov 19 14:38:23 ********* winbindd[4342]: PANIC (pid 4342): failed to set uid
nov 19 14:38:23 ********* winbindd[4342]: nov 19 14:38:23 uzaws0531
winbindd[4342]: [2013/11/19 14:38:23.539862,  0]
./source3/lib/util.c:896(log_stack_trace)
nov 19 14:38:23 ********* winbindd[4342]: BACKTRACE: 18 stack frames:
nov 19 14:38:23 ********* winbindd[4342]: #0
/usr/lib64/libsmbconf.so.0(log_stack_trace+0x1a) [0x7fb82acdd2ea]
nov 19 14:38:23 ********* winbindd[4342]: #1
/usr/lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x7fb82acdd3c0]
nov 19 14:38:23 ********* winbindd[4342]: #2
/usr/lib64/libsamba-util.so.0(smb_panic+0x2f) [0x7fb82f1d432f]
nov 19 14:38:23 ********* winbindd[4342]: #3
/usr/lib64/samba/libsamba3-util.so(+0x32cd) [0x7fb82aaae2cd]
nov 19 14:38:23 ********* winbindd[4342]: #4
/usr/sbin/winbindd(winbindd_dual_pam_auth+0xe27) [0x7fb82fa784d7]
nov 19 14:38:23 ********* winbindd[4342]: #5 /usr/sbin/winbindd(+0x557c4)
[0x7fb82fa8c7c4]
nov 19 14:38:23 ********* winbindd[4342]: #6 /usr/lib64/libtevent.so.0(+0x904b)
[0x7fb82916804b]
nov 19 14:38:23 ********* winbindd[4342]: #7 /usr/lib64/libtevent.so.0(+0x74f7)
[0x7fb8291664f7]
nov 19 14:38:23 ********* winbindd[4342]: #8
/usr/lib64/libtevent.so.0(_tevent_loop_once+0x8d) [0x7fb82916300d]
nov 19 14:38:23 ********* winbindd[4342]: #9 /usr/sbin/winbindd(+0x57b1a)
[0x7fb82fa8eb1a]
nov 19 14:38:23 ********* winbindd[4342]: #10 /usr/sbin/winbindd(+0x581d5)
[0x7fb82fa8f1d5]
nov 19 14:38:23 ********* winbindd[4342]: #11
/usr/lib64/libtevent.so.0(tevent_common_loop_immediate+0xd4) [0x7fb829163834]
nov 19 14:38:23 ********* winbindd[4342]: #12
/usr/lib64/libtevent.so.0(+0x8e07) [0x7fb829167e07]
nov 19 14:38:23 ********* winbindd[4342]: #13
/usr/lib64/libtevent.so.0(+0x74f7) [0x7fb8291664f7]
nov 19 14:38:23 ********* winbindd[4342]: #14
/usr/lib64/libtevent.so.0(_tevent_loop_once+0x8d) [0x7fb82916300d]
nov 19 14:38:23 ********* winbindd[4342]: #15 /usr/sbin/winbindd(main+0xa92)
[0x7fb82fa5ec32]
nov 19 14:38:23 ********* winbindd[4342]: #16
/lib64/libc.so.6(__libc_start_main+0xf5) [0x7fb828b85be5]
nov 19 14:38:23 ********* winbindd[4342]: #17 /usr/sbin/winbindd(+0x28325)
[0x7fb82fa5f325]
nov 19 14:38:23 ********* winbindd[4342]: [2013/11/19 14:38:23.542655,  0]
./source3/lib/dumpcore.c:317(dump_core)
nov 19 14:38:23 ********* winbindd[4342]: dumping core in
/var/log/samba/cores/winbindd
nov 19 14:38:23 ********* winbindd[4342]: nov 19 14:38:23 uzaws0531 kernel:
type=1400 audit(1384868303.538:77): apparmor="DENIED" operation="capable"
parent=4341 profile="/usr/sbin/winbindd" pid=4342 comm="winbindd" pid=4342
comm="winbindd" capability=7  capname="setuid"

So I added
  capability setuid,
to the apparmor profile /etc/apparmor.d/usr.sbin.winbindd

But logon still failed, now reporting this:
nov 19 15:01:48 ********* kernel: audit_printk_skb: 66 callbacks suppressed
nov 19 15:01:48 ********* kernel: type=1400 audit(1384869708.922:206):
apparmor="DENIED" operation="mknod" parent=4341 profile="/usr/sbin/winbindd"
name="/var/tmp/*********-044_39756" pid=5747 comm="winbindd" requested_mask="c"
denied_mask="c" fsuid=39756 ouid=39756

Finally adding
  capability mknod,
  /var/tmp/* rwlk,
to the apparmor profile /etc/apparmor.d/usr.sbin.winbindd resolved the logon
problem. (the permissions on /var/tmp/ are maybe a bit too open, but I really
wanted the problem to be solved quickly by now..)

I could now log on, but still some errors where logged:
nov 19 15:03:49 ********* kernel: audit_printk_skb: 66 callbacks suppressed
nov 19 15:03:49 ********* kernel: type=1400 audit(1384869829.321:238):
apparmor="DENIED" operation="capable" parent=4341 profile="/usr/sbin/winbindd"
pid=5747 comm="winbindd" pid=5747 comm="winbindd" capability=14
capname="ipc_lock"

So this time I added
  capability ipc_lock,
to the apparmor profile /etc/apparmor.d/usr.sbin.winbindd

And now I don't seem to get any more apparmor/winbind related errors when
logging in using my AD domain account.

I don't know if this bug only appears when the system is upgraded from 12.3
using yast dup, or if it would also manifest when upgrading using the DVD or
even doing a fresh install..

Reproducible: Didn't try

Steps to Reproduce:
1. Connect to Windows Domain using YaST
2. (Upgrade openSUSE 12.3 to 13.1 using yast dup method)
3. Try to log in using a domain account
Actual Results:
winbind can't authenticate the domain user because apparmor denies it from
doing so.

Expected Results:
winbind should be able to correctly authenticate the domain user

summary: AppArmor prevents winbind from working correctly


body:
(gdb) backtrace
#0  0xb0d38fbe in nl_object_get_id_attrs () from /usr/lib/libnl-3.so.200
#1  0xb3f647d7 in update_connectivity (self=self@entry=0x87e7f30,
nl_info=nl_info@entry=0x87e7f50) at ntrack-libnl.c:533
#2  0xb3f64eca in smart_cache_update (user_data=0x87e7f50, self=0x87e7f30) at
ntrack-libnl.c:313
#3  _ntrack_arch_process_data (self=0x87e7f30, fds=0xbfffe788) at
ntrack-libnl.c:209
#4  0xb416835d in ntrack_arch_process_data (self=0x87e7f30, fds=0xbfffe788) at
ntrack.c:184
#5  0xb513abe6 in QNtrack::socketActivated (this=this@entry=0x87e72c8,
socket=16) at QNtrack.cpp:71
#6  0xb513af49 in QNtrack::qt_static_metacall (_o=0x87e72c8,
_c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfffe878) at moc_QNtrack.cpp:57
#7  0xb53dbc55 in QMetaObject::activate(QObject*, QMetaObject const*, int,
void**) () from /usr/lib/libQtCore.so.4
#8  0xb542c6d5 in QSocketNotifier::activated(int) () from
/usr/lib/libQtCore.so.4
#9  0xb53e50df in QSocketNotifier::event(QEvent*) () from
/usr/lib/libQtCore.so.4
#10 0xb58884b4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from
/usr/lib/libQtGui.so.4
#11 0xb588eee3 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQtGui.so.4
#12 0xb53c6fba in QCoreApplication::notifyInternal(QObject*, QEvent*) () from
/usr/lib/libQtCore.so.4
#13 0xb53f7368 in ?? () from /usr/lib/libQtCore.so.4
#14 0xb48d67ce in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#15 0xb48d6b78 in ?? () from /usr/lib/libglib-2.0.so.0
#16 0xb48d6c38 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#17 0xb53f65ef in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#18 0xb593851e in ?? () from /usr/lib/libQtGui.so.4
#19 0xb53c5a03 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQtCore.so.4
#20 0xb53c5d29 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#21 0xb53cb4fe in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#22 0xb5886944 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#23 0x0812eaa0 in main (argc=1, argv=0xbfffef24) at
/usr/src/debug/kadu-0.12.3/kadu-core/main.cpp:407

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: [0.12.3] Kadu crashes shortly after start on openSUSE 13.1


body:
13.1 repo missing python3-numpy, python3-scipy, python3-matplotlib,
python3-IPython packages. There is python3-numpydoc (!) it is useless without
python3-numpy at least. All this packages are stable with python3 and was
included in 12.3 repo.

Reproducible: Always

Steps to Reproduce:
1. Try to search python3-numpy   zypper se python3-numpy

Actual Results:
openSUSE repo miss essential scientific python3 packages. It is regression from
12.3.

Expected Results:
openSUSE 13.1 should provide numpy, scipy, IPython, matplotlib for python3. At
least in update repo.

summary: python3 packages (numpy, scipy, IPython, matplotlib) mising from 13.1 repo


body:
After upgrading from 12.3, if I plugged anything into the *dock* speaker for my
Thinkpad T520, I got no sound output at all.

Some googling suggested a workaround

summary: snd_hda_intel: thinkpad t520: have to specify "model=thinkpad" in modprobe for snd-hda-intel


https://bugzilla.novell.com/show_bug.cgi?id=851374

https://bugzilla.novell.com/show_bug.cgi?id=851374#c0

           Summary: chkconfig --check broken with systemd services
    Classification: openSUSE
           Product: openSUSE 12.3
           Version: Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: werner-at-suse.com
        ReportedBy: mrueckert-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: fcrozat-at-suse.com, tchatzimichos-at-suse.com
          Found By: ---
           Blocker: ---

$ chkconfig apache2
apache2  on
$ chkconfig --check apache2 ; echo $?
1

this breaks the puppet check if the service is enabled.


https://bugzilla.novell.com/show_bug.cgi?id=851393

https://bugzilla.novell.com/show_bug.cgi?id=851393#c0

           Summary: systemd-journald spins with 100% cpu inside a lxc container
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: werner-at-suse.com
        ReportedBy: mrueckert-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: tbehrens-at-suse.com, fcrozat-at-suse.com
          Found By: ---
           Blocker: ---

lxc container was created with 12.3 and then brought up to 13.1. since the
switch to 13.1 the journald spins with 100% cpu load. strace showed:

epoll_wait(7, {{EPOLLIN|EPOLLERR|EPOLLHUP, {u32=8, u64=8}}}, 1, -1) = 1
writev(2, [{"/dev/kmsg buffer overrun, some messages lost.", 45}, {"\n", 1}],
2) = 46
read(8, "", 8192)                       = 0

$ ls -ld /dev/{kmsg,console}
crw--w--


body:
Manipulation of openvswitch configured bridges (ie. via `ovs-vsctl del-br
BR_NAME`) causes a panic (if kdump is enabled) otherwise renders networking
inoperable, causing commands like ifconfig and numerous other network-centric
apps to hang indefinitely.

After some discussion with rhafer on irc.nue.suse.com:#cloud, I took a look
into the openvswitch Ubuntu package and have tested a patch which looks to
solve the problem. Submitting a request to our open build service.

Log of panic attached in report.

Reproducible: Always

Steps to Reproduce:
1. systemctl start openvswitch-switch
2. ovs-vsctl add-br foobr0
3. ovs-vsctl del-br foobr0
Actual Results:
Kernel panic with kdump enabled, otherwise stack dump along with inoperable
networking.

Expected Results:
Proper deletion of bridge without the above fault.

summary: openvswitch kernel module panic on bridge manipulation


body:
https://bitbucket.org/logilab/pylint/issue/14/crashes-on-missing-import

is present in current 13.1 python3-pylint package.

According to the link above an update to python3-logilab-common seems to fix
the problem.

Reproducible: Always

Steps to Reproduce:
1. run pylint-python3.3
2. get exactly the same output as reported in the bug linked above
3.

summary: pylint crashes for python3


https://bugzilla.novell.com/show_bug.cgi?id=851509

https://bugzilla.novell.com/show_bug.cgi?id=851509#c0

           Summary: Please split gimp aa output plug-in to a separate subpackage
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: x86-64
        OS/Version: openSUSE 13.1
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: X11 Applications
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: jdelvare-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: zaitor-at-opensuse.org, dimstar-at-opensuse.org,
                    vuntz-at-suse.com
          Found By: Community User
           Blocker: ---

When I install a minimum system on an old computer, I want to avoid installing
packages I don't really need. Gimp draws libaa1 as a dependency for its aa
output plug-in which I suspect 99% of the users don't care about. libaa1 itself
draws gpm as a dependency, another package 99% of the users don't need.

So can we please split the aa output plugin to a separate subpackage, and not
install it by default?


https://bugzilla.novell.com/show_bug.cgi?id=851619

https://bugzilla.novell.com/show_bug.cgi?id=851619#c0

           Summary: strange permissions on /usr/sbin/icingastats
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: Other
        OS/Version: openSUSE 13.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: lrupp-at-suse.com
        ReportedBy: suse-beta-at-cboltz.de
         QAContact: qa-bugs-at-suse.de
          Found By: Beta-Customer
           Blocker: ---

From ARCHIVES.gz:
/suse/i586/icinga-1.9.3-4.3.1.i586.rpm:
    -rwxr-xr


https://bugzilla.novell.com/show_bug.cgi?id=851620

https://bugzilla.novell.com/show_bug.cgi?id=851620#c0

           Summary: Strange permissions on /usr/sbin/kbdsniffd
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: Other
        OS/Version: openSUSE 13.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: meissner-at-suse.com
        ReportedBy: suse-beta-at-cboltz.de
         QAContact: qa-bugs-at-suse.de
          Found By: Beta-Customer
           Blocker: ---

From ARCHIVES.gz:
/suse/i586/kbdsniffd-0.6-20.1.2.i586.rpm:
    -rwxr--r


https://bugzilla.novell.com/show_bug.cgi?id=851627

https://bugzilla.novell.com/show_bug.cgi?id=851627#c0

           Summary: Strange permissions on /usr/sbin/apache2-systemd-ask-pass and /usr/sbin/start_apache2
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: Other
        OS/Version: openSUSE 13.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: draht-at-suse.com
        ReportedBy: suse-beta-at-cboltz.de
         QAContact: qa-bugs-at-suse.de
          Found By: Beta-Customer
           Blocker: ---

From ARCHIVES.gz:
/suse/i586/apache2-2.4.6-6.3.1.i586.rpm:
    -rwxr--r


body:
https://bugzilla.novell.com/show_bug.cgi?id=851647

https://bugzilla.novell.com/show_bug.cgi?id=851647#c0

           Summary: /usr/bin/pod2readme not executable
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: Other
        OS/Version: openSUSE 13.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: chris-at-computersalat.de
        ReportedBy: suse-beta-at-cboltz.de
         QAContact: qa-bugs-at-suse.de
          Found By: Beta-Customer
           Blocker: ---

ARCHIVES.gz contains:
/suse/noarch/perl-Pod-Readme-0.11-10.1.2.noarch.rpm:
    -rw-r--r

summary: /usr/bin/pod2readme not executable


https://bugzilla.novell.com/show_bug.cgi?id=851722

https://bugzilla.novell.com/show_bug.cgi?id=851722#c0

           Summary: grub2's os-prober reports EMERGENCY corrupt xfs filesystem on extended partition
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: x86-64
        OS/Version: openSUSE 13.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Bootloader
        AssignedTo: jsrain-at-suse.com
        ReportedBy: jimc-at-math.ucla.edu
         QAContact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

This is for os-prober-1.61-3.1.2.x86_64 required by grub2-2.00-39.1.3.x86_64 .

I upgraded from OpenSuSE-12.3 to 13.1 final.  Shortly after reboot, and
again 25 minutes later, something unknown execed os-prober which reports
in syslog probing all partitions, mostly uneventfully except for syslog
reports of negative findings (I have a priority=debug log).  /dev/sda4 is
the extended partition on this disc.  When 50mounted-tests tries to mount
it (without specifying the filesystem type), most filesystem modules are
not too verbose when they fail to mount /dev/sda4.

However, when mounting is attempted as xfs, it spews out a full call trace
and a lot more, plus a report to all logged-in users, presumably at
priority = emergency.  I haven't seen this before: maybe os-prober is
new in 13.1-final (I didn't see the behavior in 13.1-RC1), or maybe
this particular extended partition sets off the bug.

Sooner or later, someone is going to have a partition containing garbage
which looks like a real filesystem


body:
upgrade of working 12.3 servers with /boot on RAID & other parts on
LVM-on-RAID, to 13.1,

    lsb_release -rd
        Description:    openSUSE 13.1 (Bottle) (x86_64)
        Release:        13.1

no longer boot, hanging hard at

    [  OK  ] Reached target Encrypted Volumes.
             Starting Activation of LVM2 logical volumes...
    [  OK  ] Started Activation of LVM2 logical volumes.
    [ TIME ] Timed out waiting for device
dev-disk-by\x2did-md\x2...c30fbff.device.
    [DEPEND] Dependency failed for /boot.
    [DEPEND] Dependency failed for Local File Systems.

on 12.3

    lsb_release -rd
        Description:    openSUSE 12.3 (x86_64)
        Release:        12.3

lvm2 was called from

    grep -rlni lvm2 /etc/init.d
        /etc/init.d/boot.lvm

but on 13.1, it's handled by systemd units,

checking

    rpm -q --whatprovides /usr/lib/systemd/system/lvm2-monitor.service
        lvm2-2.02.98-0.28.1.5.x86_64

in the service file,

    cat /usr/lib/systemd/system/lvm2-monitor.service
        [Unit]
        Description=Monitoring of LVM2 mirrors, snapshots etc. using dmeventd
or progress polling
        Documentation=man:dmeventd(8) man:lvcreate(8) man:lvchange(8)
man:vgchange(8)
        Requires=dm-event.socket
        After=dm-event.socket fedora-storage-init.service
fedora-storage-init-late.service lvm2-activation.service lvm2-lvmetad.service
        Before=local-fs.target
        DefaultDependencies=no
        Conflicts=shutdown.target

        [Service]
        Type=oneshot
        Environment=LVM_SUPPRESS_LOCKING_FAILURE_MESSAGES=1
        ExecStart=/sbin/lvm vgchange --monitor y
        ExecStop=/sbin/lvm vgchange --monitor n
        RemainAfterExit=yes

        [Install]
        WantedBy=sysinit.target

note the incorrect After= dependency on

    fedora-storage-init.service
    fedora-storage-init-late.service

guessing it was simply copied from Fedora without checking/testing the
euqivalent Opensuse deps.

I'm not clear what the right deps in Opensuse 13.1 SHOULD be

summary: lvm2 systemd unit renders systems unbootable; incorrectly uses dependencies on Fedora services (fedora-storage-init.service fedora-storage-init-late.service)


body:
In 12.3, you could specify an IPv6 address for an LXC container with
lxc.network.ipv6, setting it to, say, 2001:x:x::1/64.

However, in 13.1, this is no longer working. When running lxc-start, this error
is produced:

lxc-start: No such file or directory - invalid ipv6 address: 2001:x:x::8/64
lxc-start: failed to read configuration file

Removing the option makes it work, and IPv6 works inside the container.

Reproducible: Always

summary: LXC config file no longer accepts ipv6 addresses


body:
Just after the new installation, the configuration of "br0" not re-read by
YaST, a "bridge" without a name appears. The bridge interface cannot be set,
the last folder is "hardware" instead of "bridged devices".

If the settings done during installation process, it is well configured, until
using of the YaST-network module first time, (then the configuration is damaged
if saved even "as is").

Reproducible: Always

Steps to Reproduce:
1. New installation of openSUSE 12.3
2. Install hypervisor for using of XEN (via YaST virtualization module)
3. Open YaST network module to see the network devices and bridge
(mis)configuration
Actual Results:
Network interfaces cannot be edited and configured using YaST network module.

Expected Results:
Configurable network interfaces using YaST network module.

summary: YaST Network - bridge br0 config not read properly


body:
This is on a full installation of 13.1 KDE 32-bit, using the DVD iso on a USB
stick, formatting both / and /home.

Starting pavucontrol in a terminal gives
howard@X41-os131:/usr/share/applications> pavucontrol
Segmentation fault
howard@X41-os131:/usr/share/applications>

pavucontrol works fine on the same hardware with 12.3

Other people report the same problem at
https://forums.opensuse.org/english/get-technical-help-here/multimedia/492209-segfault-pavucontrol.html

Regards,
Howard

Reproducible: Always

Steps to Reproduce:
1.Start pavucontrol from either the Kickoff application launcher or in a
terminal.
2.
3.
Actual Results:
It fails to run. In a terminal, it returns "Segmentation fault".

Expected Results:
pavucontrol starts and opens a window

summary: pavucontrol fails with segmentation fault


body:
Tab-completion turns any $ into \$, thus making it impossible to tab-complete
variable names.

Reproducible: Always

Steps to Reproduce:
1. enter "echo $PAT" in bash
2. press tab
Actual Results:
Bash completes to "echo \$PATH"

Expected Results:
It should complete to "echo $PATH"

(used to work in openSUSE 12.3 and before)

summary: Tab-completion of environment variables in bash broken


body:
I upgraded a pair of 12.3 systems with bridge configurations to 13.1. However,
it seems that IPv6 gets broken on boot because autoconfiguration is occurring
on the bridge ports. For example, say I have a br0 bridge containing eth0 as a
port. I have ifcfg-eth0 set up like this:

    BOOTPROTO='none'
    STARTMODE='auto'
    ETHTOOL_OPTIONS="-K eth1 rx off tx off"

And I have ifcfg-br0 set up like this:

    IPADDR='10.x.x.x/24'
    USERCONTROL='no'
    BOOTPROTO='static'
    BRIDGE='yes'
    BRIDGE_FORWARDDELAY='0'
    BRIDGE_PORTS='eth0'
    BRIDGE_STP='off'
    STARTMODE='auto'
    IPADDR_IPv6='2001:x:x:x::x/64'

When networking comes up, I end up with local IPv6 routes on eth0 and br0,
which totally breaks IPv6:

    2001:x:x:x::/64 dev eth0  proto kernel  metric 256  expires 2591382sec
    2001:x:x:x::/64 dev br0  proto kernel  metric 256

There is also an automatic IPv6 address on eth0 in the local range, along with
an automatic ipv4 address.

I have to remove the route and address from eth0 in order to get IPv6 working
after boot, which is very annoying as I have to ssh -4 into it and fix it after
every boot.

Reproducible: Always

summary: Network start insists on assigning addresses to bridge ports, breaking IPv6 on bridges


body:
Am unable to install ibus due to a conflict with Libreoffice KDE integration.

conflict message from yast is

"ibus 1.5.4.4.1.x86_64 conflicts with libreoffice-kde4 provided by
libreoffice-kde4-4.1.3.2-4.2.x86_64"

Yast provides no option to ignore the conflict.

ibus is required for Japanese input so this is a showstopper for me.

Reproducible: Always

summary: unable to install ibus due to libreoffice conflict


body:
The systray icon for fcitx is not in keeping with the other tray icons in KDE
4.11 on openSUSE 13.1 and looks visually out of place and unappealing.

Reproducible: Always

summary: fcitx tray icon is incompatible with other systray icons


body:
After having upgraded from 12.3 to 13.1 using the "System Upgrade" method
described in <http://en.opensuse.org/SDB:System_upgrade>, I noticed, that
dovecot was not available, as it failed to start successfully.  The journal
gave me this:

Nov 22 15:21:29 odysseus systemd[1]: Starting Dovecot IMAP/POP3 email server...
Nov 22 15:21:29 odysseus systemd[1]: Started Dovecot IMAP/POP3 email server.
Nov 22 15:21:29 odysseus systemd[1]: dovecot.service: main process exited,
code=exited, status=84/n/a
Nov 22 15:21:29 odysseus systemd[1]: Unit dovecot.service entered failed state.
Nov 22 15:21:29 odysseus kernel: type=1400 audit(1385130089.675:34):
apparmor="DENIED" operation="exec" parent=1 profile="/usr/sbin/dovecot"
name="/usr/bin/doveconf" pid=8779 comm="dovecot" requested_mask="x"
denied_..."x" fsuid=0 ouid=0
Nov 22 15:21:29 odysseus dovecot[8779]: Fatal: execv(/usr/bin/doveconf) failed:
Permission denied

which hinted me at AppArmor denying access to "doveconf".  Using the
appropriate YaST section, I removed all profiles referring to dovecot.  After
that, dovecot started and worked as expected.  I wondered whether reinstalling
the AppArmor profiles would break dovecot again and tried:

  zypper in -f apparmor-profiles

and after that

  systemctl restart dovecot.service

With the fresh profiles from the repository, dovecot still works.

Reproducible: Always

summary: After update (zypper dup) AppArmor profiles for dovecot have to be manually removed to make dovecot work


body:
Hi,

this one is driving me nuts: some operations lead to a hard X server crash with
this traceback:

[   948.483] (EE)
Fatal server error:
[   948.483] (EE) (EE) BUG: triggered 'if (f[f_idx])'
[   948.484] (EE) BUG: log.c:464 in pnprintf()
[   948.484] (EE) Unsupported printf directive '#'
[   948.484] (EE)
[   948.485] (EE) Backtrace:
[   948.485] (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x3d) [0x585acd]
[   948.485] (EE) 1: /usr/bin/Xorg (LogVMessageVerbSigSafe+0x87d) [0x59132d]
[   948.486] (EE) 2: /usr/bin/Xorg (FatalError+0xd5) [0x5915f5]
[   948.486] (EE) 3: /usr/lib64/libglamor.so.0 (0x7f8d4eca7000+0x2631f)
[0x7f8d4eccd31f]
[   948.486] (EE) 4: /usr/lib64/libglamor.so.0 (0x7f8d4eca7000+0x2647e)
[0x7f8d4eccd47e]
[   948.486] (EE) 5: /usr/lib64/libglamor.so.0 (0x7f8d4eca7000+0x2713b)
[0x7f8d4ecce13b]
[   948.487] (EE) 6: /usr/lib64/libglamor.so.0 (0x7f8d4eca7000+0x1eb01)
[0x7f8d4ecc5b01]
[   948.487] (EE) 7: /usr/lib64/libglamor.so.0 (0x7f8d4eca7000+0x1f6b0)
[0x7f8d4ecc66b0]
[   948.488] (EE) 8: /usr/lib64/libglamor.so.0 (0x7f8d4eca7000+0x4fdc)
[0x7f8d4ecabfdc]
[   948.488] (EE) 9: /usr/lib64/libglamor.so.0 (0x7f8d4eca7000+0x5567)
[0x7f8d4ecac567]
[   948.489] (EE) 10: /usr/lib64/libglamor.so.0 (0x7f8d4eca7000+0x6931)
[0x7f8d4ecad931]
[   948.489] (EE) 11: /usr/lib64/libglamor.so.0 (0x7f8d4eca7000+0x6c5a)
[0x7f8d4ecadc5a]
[   948.490] (EE) 12: /usr/bin/Xorg (miCopyRegion+0x1ad) [0x565e0d]
[   948.491] (EE) 13: /usr/bin/Xorg (miDoCopy+0x456) [0x566396]
[   948.491] (EE) 14: /usr/lib64/libglamor.so.0 (0x7f8d4eca7000+0x6c9d)
[0x7f8d4ecadc9d]
[   948.492] (EE) 15: /usr/bin/Xorg (0x400000+0x114dea) [0x514dea]
[   948.492] (EE) 16: /usr/bin/Xorg (0x400000+0x39191) [0x439191]
[   948.493] (EE) 17: /usr/bin/Xorg (0x400000+0x3cc3e) [0x43cc3e]
[   948.493] (EE) 18: /usr/bin/Xorg (0x400000+0x2c1ba) [0x42c1ba]
[   948.493] (EE) 19: /lib64/libc.so.6 (__libc_start_main+0xf5)
[0x7f8d506c6be5]
[   948.494] (EE) 20: /usr/bin/Xorg (0x400000+0x2c501) [0x42c501]
[   948.494] (EE)
[   948.494] destination is framebuffer incomplete: unknown error [%#x]
[   948.495] (EE)
[   948.495] (EE)

Reproducible: Always

Steps to Reproduce:
1. log in
2. run kinfocenter (or mplayer -vo x11 ..)
3. click on OpenGL
Actual Results:
Crash

Expected Results:
OpenGL info displayed

This is a 13.1 system, that I freshly installed(!). In order to get rid of
nvidia proprietary and hassles with nouveau, I decided to check out the "good"
ATI Linux support. With ambivalent results to put it mildly.. X server crashes
are in the class of the worst linux user experiences (and I do that for a while
now, started in '96). Therefor a critical severity is deserved.

BTW, completely changing to X11:Xorg results in the exact same behavior.
I can provide strace logs of the crashing server, if requested.

Let me know, we I can do to help to fix this issue. Hopefully, I can stand it
long enough to not swap graphics card again.

summary: Radeon HD7770: X server crashes hard from several operations (kinfocenter, mplayer)


body:
With the UPower stock version of 0.9.21, system logs are flooded with following
messages:

UPower-Linux-WARNING **: failed to coldplug unifying device: invalid response
from device: 15

They pertain to the Logitech wireless receiver (used to connect mice,
keyboards, etc).

Besides, the mouse battery level is determined incorrectly.

These are known problems of UPower 0.9.21, which are fixed in version 0.9.23,
see
https://bugs.archlinux.org/task/36449

Indeed, installing UPower 0.9.23 from Factory resolves the problems.
Should we upgrade UPower package in openSUSE 13.1 through the updates?

Reproducible: Always

summary: UPower conflict with Logitech wireless receiver


body:
Starting with a working 12.3 server with boot-on-RAID & lvm-on-RAID for other
partitions, I in-place-upgraded to 13.1.

There were no errors on upgrade; and a mkinitrd is successful.

@reboot, it no longer boots.

Appears to hang at an LVM2/Dbus timeout waiting for the /boot device that's on
RAID; here's a log snippet: http://pastebin.com/KcNPriuV

The upgrade from 12.3 -> 13.3 moves LVM2 from sysvinit to systemd init; the
unit files are new.

There's at least 1 issue with LVM2 systemd unit
(https://forums.opensuse.org/newthread.php?do=newthread&f=668)

mdadm 3.3 has issues too (http://www.spinics.net/lists/raid/msg44943.html)

There's obviously a dependency problem.

Finding/fixing it has been elusive so far.

Any suggestions how to specifically identify which dependency is broken?

Fyi, all machines I've upgraded 12.3 -> 13.1 with boot&lvm-on-RAID fail in this
manner.

All machines I've upgraded 12.3 -> 13.1 with boot&LVM, but *NO* RAID, boot
without fail.

@ forums, a comment:

> There was a problem with offline upgrade and raid: the DVD used a
> different device name for the raid than the running system, so that the
> raid is not found at some point. I don't know if it has been solved

points to a possible related comment:
----------------------------------------
Date: Thu, 21 Mar 2013 15:43:37 +0100
From: Claudio ML <>
To: opensuse at opensuse.org
Subject: [opensuse] Usual problem with upgrade from DVD to 12.3 with
system using mdadm

Hello all,

I have seen there is the same problem of the previous versions of
OpenSuSE also into 12.3. The problem is: If you try to upgrade from a
DVD an OpenSuSE with software raid (mdadm), the installer don't see the
previous version of openSuSE on the hard disk.

This is caused because the kernel don't recognize correctly the md
arrays. In example, if i have md0 (/ root file system), md1 (/var), md2
(/srv), the installer see this as md125, md126 and md127.

So, no DVD upgrade possible for this machines. I have tryied to edit
manually the fstab on the machine, adapting to what the installer see,
but after the upgrade the system becomes un-bootable.

Anyone have a good workaround for this problem?

Cordially,

Claudio.
----------------------------------------

this, too, may be of interest:

Bug 849752 - 13.1RC2 Cannot boot from RAID1 volume(s)
https://bugzilla.novell.com/show_bug.cgi?id=849752#c9

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: boot failure after 12.3 -> 13.1 upgrade if /boot is on RAID


body:
gcin is a input method framework for Chinese.
The package from 13.1 oss repo has a bad %post scriptlet that can't update
gtk2-immodule cache, so gcin can't switch to Chinese input mode to key in any
Chinese characters.
User have to run (with root)
gtk-query-immodules-2.0(-64) --update-cache
manually.
I've fix the bug,
update gcin from M17N repo can fix this problem.
and I want to issue an online update for gcin

Reproducible: Always

Steps to Reproduce:
1.install gcin : zypper in gcin
2.logout and login
3.launch firefox
4.click any textbox and press Ctrl+Space to input Chinese
Actual Results:
Can't input any Chinese characters

Expected Results:
gcin should switch to Chinese mode so you can input Chinese

summary: gcin input-method can't work in gtk2 applications


body:
https://bugzilla.novell.com/show_bug.cgi?id=851996

https://bugzilla.novell.com/show_bug.cgi?id=851996#c0

           Summary: SDL_mixer mikmod free corrution
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: x86-64
        OS/Version: openSUSE 13.1
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Sound
        AssignedTo: tiwai-at-suse.com
        ReportedBy: bwiedemann-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: Development
           Blocker: ---

When trying to start asc from the games repo
I found that it would show a free corruption
during initialization of SDL_mixer.

Debugging it further I traced it to
gdb asc
b sound.cpp:104
b mixer.c:440
b music.c:362
b music_mod.c:110

and located + successfully tested upstream fixes at
https://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/sdl_mixer

summary: SDL_mixer mikmod free corrution


body:
On my system the shutdown or reboot in a KVM System (clients) is never working.

When I make a reboot shutdown the clients are "killed", no suspend ore a
shutdown.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: KVM libvirtd Client killed on reboot shutdown


body:
running some programs e.g. yast - through xdg-su changes the owner of
/run/user/1000/pulse to root. This causes pulseaudio to fail with the message:

"Failed to create secure directory (/run/user/1000/pulse): Permission denied"

Application that use pulseaudio do not work when this has happened and output
the message above.

This occurs in the xfce environment after installing pulseaudio, no settings
changed.

This is the same problem as Bug 829076 in opensuse 12.3.

Reproducible: Always

Steps to Reproduce:
1. install pulseaudio in the xfce DE
2. run yast
3. try to run pulseaudio volume control
Actual Results:
Connection to pulseaudio failed message displayed

Expected Results:
Application working

summary: Pulseaudio fails to start after running yast or other xdg-su programs


body:
update-ca-certificates (from ca-certificates-1_201310161709-1.1.noarch) stores
certs in /var/lib/ca-certificates/ now.

This path is missing in /etc/apparmor.d/abstractions/ssl_certs

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: missing path for ssl-certs in apparmor-profiles package


body:
Stiching a panorama photo using hugin and enblend under openSUSE 13.1 fails due
to enblend crashing with the following message:

-------------------

summary: Error in `enblend': free(): invalid pointer


body:
From sr#208313, diff to 13.1 is:

-------------------------------------------------------------------
Sat Nov 16 18:51:58 UTC 2013 - hrvoje.senjan-at-gmail.com

- Update to version 9.2.3
 * st/mesa: move out of memory check in st_draw_vbo()
 * osmesa: fix broken triangle/line drawing when using float
   color buffer
 * Remove error when calling glGenQueries/glDeleteQueries while
   a query is active
 * Bump version to 9.2.3
 * i965: CS writes/reads should use I915_GEM_INSTRUCTION
 * i965: Fix texture buffer rendering after a whole buffer
   replacement.
 * i965: Emit post-sync non-zero flush before
   3DSTATE_GS_SVB_INDEX.
 * i965: Emit post-sync non-zero flush before
   3DSTATE_DRAWING_RECTANGLE.
 * i965: Also guard 3DSTATE_DRAWING_RECTANGLE with a
   flush in blorp.
 * i965: Move post-sync non-zero flush for 3DSTATE_MULTISAMPLE.
 * i965: Also emit HIER_DEPTH and STENCIL packets when
   disabling depth.
 * i965: Also emit HiZ and Stencil packets when
   disabling depth on Gen6.
 * wayland: Don't rely on static variable for
   identifying wl_drm buffers
 * radeonsi: fix blitting the last 2 mipmap levels of
   compressed textures
 * meta: enable vertex attributes in the context of the
   newly created array object
 * mesa: fixes for MSVC 2013

-------------------------------------------------------------------
Tue Nov 12 13:56:37 UTC 2013 - schwab-at-suse.de

- Add support for m68k

@Stefan, Maintenance team:
what do you say about online update for 13.1?

Reproducible: Always

summary: Mesa 9.2.3 bugfix available


body:
http://www.percona.com/doc/percona-xtrabackup/2.1/release-notes/2.1/2.1.6.h=
tml

stable upstream release

New Features

    Percona XtraBackup now supports logs created with the new log block
checksums option innodb_log_checksum_algorithm in Percona Server 5.6

    New innobackupex --force-non-empty-directories option has been implemen=
ted.
When specified, it makes innobackupex --copy-back option or innobackupex
--move-back option transfer files to non-empty directories. No existing fil=
es
will be overwritten. If --copy-back or --move-back has to copy a file from =
the
backup directory which already exists in the destination directory, it will
still fail with an error.

Bugs Fixed

    innobackupex --copy-back would fail if innodb_data_home_dir is empty. B=
ug
fixed #1049291.

    A fixed initialization vector (constant string) was used while encrypti=
ng
the data. This opened the encrypted stream/data to plaintext attacks among
others. Bug fixed #1185343.

    innobackupex --version-check is now on by default. Bug fixed #1227988.

    xtrabackup_slave_info didn=E2=80=99t contain any GTID information, whic=
h could
cause master_auto_position not to work properly. Bug fixed #1239670.

    xtrabackup_56 was using CRC32 as the default checksum algorithm. This c=
ould
cause error if the innodb_checksum_algorithm value was changed to strict_in=
nodb
value after a restore. Bug fixed #1247586.

    xtrabackup_56 binary didn=E2=80=99t store the server=E2=80=99s innodb_c=
hecksum_algorithm
value to backup-my.cnf. This value is needed because it affects the on-disk
data format. Bug fixed #1248065.

    Since Version Check is enabled by default in Percona XtraBackup 2.1.6, =
new
innobackupex --no-version-check option has been introduced to disable it. B=
ug
fixed #1248900.

    Percona XtraBackup now supports absolute paths in innodb_data_file_path
variable. Bug fixed #382742.

    innobackupex wasn=E2=80=99t able to perform backups to the NFS mount in=
 some NFS
configurations, because it was trying to preserve file ownership. Bug fixed
#943750.

    Percona XtraBackup wouldn=E2=80=99t back up the empty directory created=
 with mkdir
(i.e. test) outside of the server which could lead to inconsistencies during
the Percona XtraDB Cluster State Snapshot Transfer. Bug fixed #1217426.

    If the innodb_log_arch_dir variable was specified in the Percona Server
configuration file my.cnf Percona XtraBackup was unable to perform the back=
up.
Bug fixed #1227240.

    Race condition in start_query_killer child code could cause parent MySQL
connection to close. Bug fixed #1239728.

Reproducible: Didn't try

Steps to Reproduce:
1.
2.
3.

--=20
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=3Demail
-----

summary: Percona XtraBackup 2.1.6 maintenance release


body:
Installation or Upgrade to 13.1 from 12.3 stops if you select Turkish language.
After installation or upgrade with default english, Yast2 runs without
problems. But if you change the system language to Turkish with Yast, yast
stops again.
After editing /etc/sysconfig/language and setting it to en_US.utf8, yast start
working again.

Reproducible: Always

Steps to Reproduce:
1. Install opensuse-13.1 in English.
2. Change system languge to Turkish with yast.
3. Try Restart Yast.
Actual Results:
Yast2 hangs by "moving files to system" while installation or upgrade.
By running system, yast hangs with 50% CPU load.

Expected Results:
Should continue with automatic configuration.

Lowercase - Uppercase conversion in Turkish conflicts with English.
Perhaps the problem is related with this.
In Turkish: Capital of "dotless i" is "capital I", capital of "i" is "capital I
with dot above".

We have similar problems with php for example.

summary: Yast2 stops if you select Turkish as system language


body:
Icecast .service depends on syslog.target that doesn't exists any more.

# systemctl start icecast.service
Failed to issue method call: Unit syslog.target failed to load: No such file or
directory.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: icecast.service is broken


body:
Updated from openSuSE 12.3 to 13.1 and rdesktop segfaults when using the -P
option, worked fine in openSuSE 12.3.

Reproducible: Always

Steps to Reproduce:
1.rdesktop -u Administrator -p - -g 1024x768 -a 16 -x l -P WinBox <Address of
remote windows to connect to>
2.
3.
Actual Results:
Segmentation fault

Expected Results:
Connect to remote windows desktop

summary: Running rdesktop -P generates segmentation fault.


body:
Since upgrading to 13.1 applications using Phonon (I'm using the VLC backend)
often crash. This mostly happens when the system is under I/O load I think.

I reported the problem at KDE and the Phonon maintainer suspects a
multithreading issue in alsa.

Please see the KDE bug here: https://bugs.kde.org/show_bug.cgi?id=328087
That bug report contains a backtrace as well, but I can of course attach a new
one here as well if wanted.

I also want to add that I didn't have any crashes on 12.3 with exact the same
versions of KDE, Phonon, and VLC.

Reproducible: Sometimes

summary: Phonon-backend-vlc crashed often


body:
When an user switches to another user session, and goes back to the other user
session, the password is showed.

Reproducible: Always

Steps to Reproduce:
1. Login with an user
2. Switch to another user (without logging out the first user)
3. Try to switch back
4. The masked password will appear, click on show text.
Actual Results:
The user's password is showed

Expected Results:
The user password shouldn't be showed.

See the upstream bug report
https://bugzilla.gnome.org/show_bug.cgi?id=710456

And the report in the Red Hat's Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1034031

Footnote: In my case, I need to switch to anoter tty to reproduce this (a
little different of the original reports), maybe because I'm using the nVidia
proprietary drivers.

summary: GDM is showing passwords at user switching


body:
https://bugzilla.novell.com/show_bug.cgi?id=852524

https://bugzilla.novell.com/show_bug.cgi?id=852524#c0

           Summary: rdesktop: version 1.8.0 is broken
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Network
        AssignedTo: chris-at-computersalat.de
        ReportedBy: jengelh-at-inai.de
         QAContact: qa-bugs-at-suse.de
          Found By: Beta-Customer
           Blocker: ---

Trying to establish a connection a VirtualBox ends with some fancy error.

08:27 nakamura:~ > rdesktop localhost:33132 &
[1] 3938
08:27 nakamura:~ > Failed to negotiate protocol, retrying with plain RDP.
WARNING: Remote desktop changed from 800x600 to 1280x768.
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Resource id in failed request:  0x0
  Serial number of failed request:  38
  Current serial number in output stream:  43

The problem goes away if I simply change to rdesktop-1.7.1 (for example by use
of rpm2cpio to a separate directory) while keeping the remaining openSUSE 13.1
system as-is, including X11 libraries.

summary: rdesktop: version 1.8.0 is broken


body:
(3.10.1) Epiphany/3.10.1

Please see lp#1222742 [1]. To summarise, stellarium crashes whenever one clicks
on the tiny arrow marks in "ocular view". This is a severe bug and is solved by
update to version 0.12.4
https://launchpad.net/stellarium/+milestone/0.12.4
This update introduces this fix and a minor enhancement over version 0.12.3
released with 13.1, and I think it would be very useful to have a maintenance
update fixing this. I will make the necessary maintenance request if green
lighted here ;)

Thanks.

[1] https://bugs.launchpad.net/stellarium/+bug/1222742

Reproducible: Always

Steps to Reproduce:
1. Click any object (say the moon)
2. Select ocular view
3. Click on left or right arrow just beside "Ocular #0: Ocular 0".
Actual Results:
Clicking on left arrow immediately causes crashes, to produce crash by clicking
right arrow, one has to click thrice (until #3).

Expected Results:
No crash.

summary: Stellarium crashes when clicking on arrows in ocular view


body:
After installing openSUSE 13.1 from Gnome Live Image, all gnome-shell
extensions were deactivated whenever I rebooted, logged in, or otherwiser
reactivated the screen. After I cleaned the activated extensions key in dconf
(to remove the alternate status menu that isn't installed any more but was
still in dconf...) the extensions would remain activated on login and boot, but
they still disappear on unlock. restarting the shell brings them back (ALT+F2,
r)

Reproducible: Always

Steps to Reproduce:
1. leave screen inactive or lock screen
2. unlock screen
3.
Actual Results:
gnome-shell starts with all extensions deactivated

Expected Results:
gnome-shell starts with extensions activated

summary: gnome-shell extensions disabled on screen unlock