body:
(3.10.0) Epiphany/3.10.0

Nothing happens with "New Menu" "New Item" and "Properties" buttons are pressed
in Alacarte 3.10.
Here's the terminal output:

(alacarte:5342): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion
'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed

(alacarte:5342): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion
'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/Alacarte/MainWindow.py", line 256, in
on_new_item_button_clicked
    editor = LauncherEditor(self.main_window, file_path)
AttributeError: 'MainWindow' object has no attribute 'main_window'
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/Alacarte/MainWindow.py", line 242, in
on_new_menu_button_clicked
    editor = DirectoryEditor(self.main_window, file_path)
AttributeError: 'MainWindow' object has no attribute 'main_window'

Reproducible: Always

Steps to Reproduce:
1.open alacarte
2.Select any item
3. press "New Menu", "New Item", or ""Properties" buttons
Actual Results:
Nothing happens

Expected Results:
Separate dialogue windows should be opened to help the user create new items
and menus or view and edit the properties of any item

Factory Beta 1 with GNOME Factory Repo added. GNOME 3.10

summary: Can't create new menus and new items or view item properties in Alacarte


body:
(3.10.0) Epiphany/3.10.0

When displaying notifications, GNOME Music fails to display the album cover
art. The place where the cover should be is blank. Rhythmbox on the other hand
does display the cover art in the notifications.

Reproducible: Always

Steps to Reproduce:
1.launch gnome-music
2.wait for notifications or click on the gnome-music icon in the system tray
3. notice missing cover art on the left
Actual Results:
the area where the cover art should be is blank

Expected Results:
cover art to be displayed

GNOME 3.10 from GNOME Factory repo

summary: GNOME Music does not display the Album Cover art in the notifications


body:
The configuration files /etc/permissions and /etc/permissions.local from
package "permissions" (seen in permissions-2013.08.22.1339-3.3.x86_64.rpm)
still refer to the old (and now missing) program SuSEconfig:

# This file is used by SuSEconfig and chkstat to check or set the modes
# and ownerships of files and directories in the installation.

Instructions itself are correct:

# To change an entry copy the line to permissions.local, modify it
# to suit your needs and call "chkstat --system"

Reproducible: Always

summary: Comments in package "permissions" still refer to SuSEconfig


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

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

           Summary: On switching from text mode to graphical mode, systemd umounts some partitions.
    Classification: openSUSE
           Product: openSUSE 12.3
           Version: Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Usability
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: carlos.e.r-at-opensuse.org
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On switching from text mode to graphical mode (runlevel 3 to runlevel 5),
systemd umounts two encrypted partitions I have manually mounted.

Component: SYSTEM-D  - please ignore Bugzilla component, there is no
appropriate one.

Copied from an email thread in the opensuse-at-opensuse.org mail list=20
(Subject: Re: [opensuse] On switching from runlevel 3 to 5, two partitions =
are
umounted (by systemd??))

I boot this system in level 3, text mode with network. Some times I
manually mount two encrypted partitions there, as root. Then I switch to
runlevel 5, and log in.

Eventually, I noticed that those two partitions were not mounted. I
thought that perhaps I did not mount them. So this time I checked. I
mounted them, and verified that the content was available. I then started
level 5 (init 5). I typed ctrl-alt-f1, and listed the content of those
partitions: not mounted. Not only that, but the "/dev/mapper/..." device
had disappeared as well.

This is 12.3.

Problem happens on every boot.

Log entries proving this:

<10.5> 2013-09-25 01:24:41 Telcontar login - - -  ROOT LOGIN ON tty1
<3.6> 2013-09-25 01:25:35 Telcontar systemd 1 - -  Found device
/dev/disk/by-uuid/8a177751-d9ba-472c-9d5d-d868ca5407d8.
<3.6> 2013-09-25 01:25:35 Telcontar systemd 1 - -  Found device
/dev/disk/by-label/other.
<3.6> 2013-09-25 01:25:35 Telcontar systemd 1 - -  Found device
/dev/disk/by-id/dm-uuid-CRYPT-LUKS1-35ddcabc7e6f4ffeb5e573a942da6425-cr_oth=
er.
<3.6> 2013-09-25 01:25:35 Telcontar systemd 1 - -  Found device
/dev/disk/by-id/dm-name-cr_other.
<3.6> 2013-09-25 01:25:35 Telcontar systemd 1 - -  Found device /dev/dm-1.
<3.6> 2013-09-25 01:25:35 Telcontar systemd 1 - -  Found device
/sys/devices/virtual/block/dm-1.
<3.6> 2013-09-25 01:25:35 Telcontar systemd 1 - -  Starting Cryptography Se=
tup
for cr_other...
<3.6> 2013-09-25 01:25:35 Telcontar systemd-cryptsetup 4100 - -  Volume
cr_other already active.
<3.6> 2013-09-25 01:25:35 Telcontar systemd 1 - -  Started Cryptography Set=
up
for cr_other.
<3.6> 2013-09-25 01:25:38 Telcontar systemd 1 - -  Found device
/dev/disk/by-uuid/0c698c18-157e-4a9f-ad39-054228b372c6.
<3.6> 2013-09-25 01:25:38 Telcontar systemd 1 - -  Found device
/dev/disk/by-label/Datum.
<3.6> 2013-09-25 01:25:38 Telcontar systemd 1 - -  Found device
/dev/disk/by-id/dm-uuid-CRYPT-LUKS1-39334baa941f42aba0a47c20a427aff2-cr_Dat=
um.
<3.6> 2013-09-25 01:25:38 Telcontar systemd 1 - -  Found device
/dev/disk/by-id/dm-name-cr_Datum.
<3.6> 2013-09-25 01:25:38 Telcontar systemd 1 - -  Found device /dev/dm-2.
<3.6> 2013-09-25 01:25:38 Telcontar systemd 1 - -  Found device
/sys/devices/virtual/block/dm-2.
<3.6> 2013-09-25 01:25:38 Telcontar systemd 1 - -  Starting Cryptography Se=
tup
for cr_Datum...
<3.6> 2013-09-25 01:25:38 Telcontar systemd-cryptsetup 4142 - -  Volume
cr_Datum already active.
<3.6> 2013-09-25 01:25:38 Telcontar systemd 1 - -  Started Cryptography Set=
up
for cr_Datum.
<0.5> 2013-09-25 01:25:39 Telcontar kernel - - - [  208.540714] XFS (dm-1):
Mounting Filesystem
<0.6> 2013-09-25 01:25:40 Telcontar kernel - - - [  208.665690] XFS (dm-1):
Ending clean mount
<0.5> 2013-09-25 01:25:40 Telcontar kernel - - - [  208.682251] XFS (dm-2):
Mounting Filesystem
<0.6> 2013-09-25 01:25:40 Telcontar kernel - - - [  208.821286] XFS (dm-2):
Ending clean mount
<3.6> 2013-09-25 01:26:10 Telcontar systemd 1 - -  Unmounting /data/Datum..=
=20=20=20
                  <=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
<3.6> 2013-09-25 01:26:10 Telcontar systemd 1 - -  Stopping
/sys/devices/virtual/block/dm-2.      <=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
<3.6> 2013-09-25 01:26:10 Telcontar systemd 1 - -  last message repeated 5
times
<3.6> 2013-09-25 01:26:10 Telcontar systemd 1 - -  Stopping Cryptography Se=
tup
for cr_Datum...    <=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
<3.6> 2013-09-25 01:26:10 Telcontar systemd 1 - -  Unmounting /data/other...
<3.6> 2013-09-25 01:26:10 Telcontar systemd 1 - -  Stopping
/sys/devices/virtual/block/dm-1.      <=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
<3.6> 2013-09-25 01:26:10 Telcontar systemd 1 - -  last message repeated 4
times
<3.6> 2013-09-25 01:26:10 Telcontar systemd 1 - -  Stopping Authorization
Manager...
<3.6> 2013-09-25 01:26:10 Telcontar systemd 1 - -  Stopping Console Manager=
..
<3.6> 2013-09-25 01:26:10 Telcontar systemd 1 - -  Stopping CUPS Printing
Service...

The response to the command "systemctl show systemd-cryptsetup@cr_other.ser=
vice
-p IgnoreOnIsolate" is

IgnoreOnIsolate=3Dno

Andrey Borzenkov tells me to report in bugzilla.
Cristian Rodr=C3=ADguez says that this commit:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=3D4469ff4adebbed4778=
e7fe767f0165776c1ba62a

corrects the issue in 13.1.

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


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

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

           Summary: aaa_base: commit 4459f20 unexpected behavior
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: werner-at-suse.com
        ReportedBy: lnussel-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: fcrozat-at-suse.com
          Found By: ---
           Blocker: ---

Commit 4459f20 apparently was intended to make systemd know about freshly
installed initscripts by transparently re-loading the daemon. The code however
seems to actually enable the script when just calling e.g. "status".

+      systemctl daemon-reload
+      systemctl --no-reload enable "${_rc_base}.service" 2> /dev/null


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

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

           Summary: sysconfig: blacklist for sk98lin no longer needed
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: mt-at-suse.com
        ReportedBy: mmarek-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Please remove this part:

# This driver is obsolete and should never be loaded as default.
# See https://bugzilla.novell.com/show_bug.cgi?id=146930
blacklist sk98lin

because the sk98lin driver has been dropped from the kernel in 2.6.26:
$ git describe --contains 548c36e983f346621b5cb9ab031e4383e9996576
v2.6.26-rc1~1138^2~390^2~34


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

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

           Summary: sysconfig: remove blacklist of dropped drivers
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: mt-at-suse.com
        ReportedBy: mmarek-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Several drivers are blacklisted in /etc/modprobe.d/50-blacklist.conf, but have
been dropped from the upstream kernel:

stradis
  dropped in 2.6.38 (39c3d48)
eepro100
  dropped in 2.6.29 (6b1abba)
slamr, slusb
  OK, these are not mainline drivers, but 10.3 was the last release to ship
  smartlink-softmodem-kmp
ich2rom
  replaced with ichxrom in 2.6.12 (304aa41). BTW, is there a bugzilla
  explaining why these drivers are blacklisted?
eth1394
  dropped in 2.6.37 (66fa12c)
uhci
  both uhci and usb-uhci were dropped in 2.5.27


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

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

           Summary: VUL-0: root occasionaly gets group=100(users)
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: meissner-at-suse.com
        ReportedBy: meissner-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: coolo-at-suse.com, security-team-at-suse.de,
                    crrodriguez-at-opensuse.org
          Found By: ---
           Blocker: ---

root occasionaly gets group=100(users) instead of group=0(root)
which is a security problem.

It is unclear how this happens.

New installs of 13.1 Beta do not seem to do that.

Upgrades / Updates seem to do it, but it is unclear which ones do.


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

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

           Summary: package bash: installation error
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Installation
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: comes-at-naic.edu
         QAContact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

After a default installation I found this error in /var/log/zypp/history:

# 2013-09-19 14:13:27 libgcc43-4.3.4_20091019-18.3.x86_64.rpm installed ok
# Additional rpm output:
# /bin/sh: error while loading shared libraries: libreadline.so.6: cannot open
shared object file: No such file or directory
# warning: %post(libgcc43-4.3.4_20091019-18.3.x86_64) scriptlet failed, exit
status 127
#
2013-09-19
14:13:27|install|libgcc43|4.3.4_20091019-18.3|x86_64||openSUSE-13.1-1.19|4231fbd596877ff9929071840941a850f5e6a6c39c147140950fd699cc2393fa|
------------------------------------------------------------------------------------------
# 2013-09-19 14:14:00 libstdc++6-4.8.1_20130909-2.1.x86_64.rpm installed ok
# Additional rpm output:
# /bin/sh: error while loading shared libraries: libreadline.so.6: cannot open
shared object file: No such file or directory
# warning: %post(libstdc++6-4.8.1_20130909-2.1.x86_64) scriptlet failed, exit
status 127
#
2013-09-19
14:14:00|install|libstdc++6|4.8.1_20130909-2.1|x86_64||openSUSE-13.1-1.19|6e94dd2821ece8580004b9c6c8c2eab25c4a0bce0cc35e60b10bbd0d318e6424|

The problem is that when libstdc++6 and libgcc43 are installed bash is already
installed but libreadline6 it is not yet.

A possible fix is to add two lines in bash.spec:

 BuildRequires:  ncurses-devel
 BuildRequires:  patchutils
 BuildRequires:  screen
+PreReq:         libreadline6
+PreReq:         libncurses5
 %define         bash_vers 4.2
 %define         rl_vers   6.2
 %define         extend    ""

It is necessary to add not only libreadline6 but also libncurses5. If only
libreadline6 is added then after an installation that uses the modifyed bash
rpm this error message appears in in /var/log/zypp/history:

# 2013-09-19 19:33:16 libgcc43-4.3.4_20091019-18.3.x86_64.rpm installed ok
# Additional rpm output:
# /bin/sh: error while loading shared libraries: libtinfo.so.5: cannot open
shared object file: No such file or directory
# warning: %post(libgcc43-4.3.4_20091019-18.3.x86_64) scriptlet failed, exit
status 127
#
2013-09-19
19:33:16|install|libgcc43|4.3.4_20091019-18.3|x86_64||openSUSE-13.1-1.19|4231fbd596877ff9929071840941a850f5e6a6c39c147140950fd699cc2393fa|
------------------------------------------------------------------------------------------
# 2013-09-19 19:33:16 libstdc++6-4.8.1_20130909-2.1.x86_64.rpm installed ok
# Additional rpm output:
# /bin/sh: error while loading shared libraries: libtinfo.so.5: cannot open
shared object file: No such file or directory
# warning: %post(libstdc++6-4.8.1_20130909-2.1.x86_64) scriptlet failed, exit
status 127
#
2013-09-19
19:33:16|install|libstdc++6|4.8.1_20130909-2.1|x86_64||openSUSE-13.1-1.19|6e94dd2821ece8580004b9c6c8c2eab25c4a0bce0cc35e60b10bbd0d318e6424|

meaning that libncurses5 is needed as well.

summary: package bash: installation error


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

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

           Summary: middle-button trackpoint-scrolling no longer works on thinkpad
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
        AssignedTo: bnc-team-xorg-bugs-at-forge.provo.novell.com
        ReportedBy: seife-at-novell.slipkontur.de
         QAContact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: Third Party Developer/Partner
           Blocker: ---

after todays Factory update, middle-button + trackpoint scrolling no longer
works on thinkpad X200s.

to reenable, I need to

ID=$(xinput list --id-only "TPPS/2 IBM TrackPoint")
xinput set-int-prop $ID "Evdev Wheel Emulation" 8 1
xinput set-int-prop $ID "Evdev Wheel Emulation Button" 8 2

it might of course be a new instance of "drop all useful functionality", in
this case, just close this bug as invalid.

But I hope this is simply an bug and will be fixed before 13.1 :-)


body:
I need to run 3rd-party provided Commercial application (IBM Notes) which
provides its own java version. On OpenSUSE 13.1 beta1 application stopped
working, it was working fine with OpenSUSE 12.3. I then tested different 32-bit
java runtime environments, and all of them crashed with the same or similar
error.

Reproducible: Always

Steps to Reproduce:
1. download 32-bit java jre from Oracle web site, and extract it
2. try to run any java application with 32-bit jre (I usedh
ttp://sourceforge.net/projects/briss/)
Actual Results:
#  SIGSEGV (0xb) at pc=0xf7634e95, pid=24567, tid=4135324480
#
# JRE version:  (7.0_40-b43) (build )
# Java VM: Java HotSpot(TM) Server VM (24.0-b56 mixed mode linux-x86 )
# Problematic frame:
# C  [libc.so.6+0x12ee95]  __strstr_sse42+0x355

Expected Results:
Application should run.

summary: 32-bit java in 64-bit OpenSUSE 13.1 crashes with error related to libc.so.6


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

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

           Summary: femon uses wrong unit for SNR
    Classification: openSUSE
           Product: openSUSE 12.3
           Version: Final
          Platform: x86-64
        OS/Version: openSUSE 12.3
            Status: ASSIGNED
          Severity: Normal
          Priority: P5 - None
         Component: Other
        AssignedTo: jdelvare-at-suse.com
        ReportedBy: jdelvare-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: Community User
           Blocker: ---

The SNR is reported by most DVB frontend drivers in 0.1 dB units. However femon
displays the SNR as % of a 16-bit scale. For compliant drivers, this results in
0% SNR all the time, which isn't useful at all. The SNR should be displayed in
dB for these drivers.

summary: femon uses wrong unit for SNR


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

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

           Summary: femon complains about operation not supported
    Classification: openSUSE
           Product: openSUSE 12.3
           Version: Final
          Platform: x86-64
        OS/Version: openSUSE 12.3
            Status: ASSIGNED
          Severity: Normal
          Priority: P5 - None
         Component: Other
        AssignedTo: jdelvare-at-suse.com
        ReportedBy: jdelvare-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: Community User
           Blocker: ---

femon assumes that all frontend drivers implement all monitoring callbacks.
They don't have to, and as a matter of fact, some do not. For example, with the
DRXK frontend doesn't report the bit error rate. This leads to the following
output:

FE: DRXK DVB-T (DVBT)
Problem retrieving frontend information: Operation not supported
status SCVYL | signal 100% | snr   0% | ber -1302745961 | unc 0 | FE_HAS_LOCK
Problem retrieving frontend information: Operation not supported
status SCVYL | signal 100% | snr   0% | ber -1302745961 | unc 0 | FE_HAS_LOCK

That's not user-friendly and should be improved.


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

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

           Summary: question: network.service enablement (network:wicked:factory/wicked -> factory)
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
        AssignedTo: fcrozat-at-suse.com
        ReportedBy: mt-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: aj-at-suse.com, ohering-at-suse.com, werner-at-suse.com,
                    security-team-at-suse.de, mfilka-at-suse.com,
                    kmroz-at-suse.com, pwieczorkiewicz-at-suse.com
          Found By: ---
           Blocker: ---

Until now, the sysconfig network service were enabling itself by default
at installation time.

Frederic: How should we handle this with wicked?
Should we use systemd-presets[-branding-openSUSE] or enable it as before
with sysconfig?

Currently wicked.spec enables itself if the network.service link (is unset)
or points to wicked.service or network.service [=syscofig], that is when it
migrates from/replaces sysconfig-network.

In a normal installation yast2-network network service is changing to the
network service as needed / as specified by the user.

But on update or additional install of wicked, yast2-network is not involved
and when the spec file does not enable itself as above, there would be no
network enabled after reboot...

See also obs rq #201154.


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

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

           Summary: ImageMagick build fails
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: BigEndian
        OS/Version: openSUSE 12.3
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: pgajdos-at-suse.com
        ReportedBy: dvaleev-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

ImageMagic test fails on powerpc, though build fails.

Failing test is a part of t/read.t
MAT (MatLab gray 64-bit LSB double) ...
mean-error=0.210660069835285, maximum-error=1
not ok 13

summary: ImageMagick build fails


body:
Due to lack of "GTK3_IM_MODULE=gcin" in /etc/X11/xim.d/gcin, it can't input in
firefox.

Just need a bugzilla ID for myself to prepare an update for 12.2/12.3

Reproducible: Always

summary: gcin: can use in firefox!


body:
Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majori=
ty
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 50 security fixes. Below, we highlight some fixes that
were either contributed by external researchers or particularly interesting.
Please see the Chromium security page for more information.=20

[$2500][223962][270758][271161][284785][284786] Medium CVE-2013-2906: Races=
 in
Web Audio. Credit to Atte Kettunen of OUSPG.
[260667] Medium CVE-2013-2907: Out of bounds read in Window.prototype objec=
t.
Credit to Boris Zbarsky.
[$500][265221] Medium CVE-2013-2908: Address bar spoofing related to the =
=E2=80=9C204
No Content=E2=80=9D status code. Credit to Chamal de Silva.
[$4000][265838][279277] High CVE-2013-2909: Use after free in inline-block
rendering. Credit to Atte Kettunen of OUSPG.=20
[$500][269753] Medium CVE-2013-2910: Use-after-free in Web Audio. Credit to=
=20
Byoungyoung Lee of Georgia Tech Information Security Center (GTISC).
[$1000][271939] High CVE-2013-2911: Use-after-free in XSLT. Credit to Atte
Kettunen of OUSPG.
[$1000][276368] High CVE-2013-2912: Use-after-free in PPAPI. Credit to Cham=
al
de Silva and 41.w4r10r(at)garage4hackers.com.
[$1000][278908] High CVE-2013-2913: Use-after-free in XML document parsing.
Credit to cloudfuzzer.=20
[$1000][279263] High CVE-2013-2914: Use after free in the Windows color cho=
oser
dialog. Credit to Khalil Zhani.=20
[280512] Low CVE-2013-2915: Address bar spoofing via a malformed scheme. Cr=
edit
to Wander Groeneveld.=20
[$2000][281256] High CVE-2013-2916: Address bar spoofing related to the =E2=
=80=9C204 No
Content=E2=80=9D status code. Credit to Masato Kinugawa.
[$500][281480] Medium CVE-2013-2917: Out of bounds read in Web Audio. Credi=
t to
Byoungyoung Lee and Tielei Wang of Georgia Tech Information Security Center
(GTISC).=20
[$1000][282088] High CVE-2013-2918: Use-after-free in DOM. Credit to
Byoungyoung Lee of Georgia Tech Information Security Center (GTISC).=20
[$1000][282736] High CVE-2013-2919: Memory corruption in V8. Credit to Adam
Haile of Concrete Data.=20
[285742] Medium CVE-2013-2920: Out of bounds read in URL parsing. Credit to
Atte Kettunen of OUSPG.
[$1000][286414] High CVE-2013-2921: Use-after-free in resource loader. Cred=
it
to Byoungyoung Lee and Tielei Wang of Georgia Tech Information Security Cen=
ter
(GTISC).=20
[$2000][286975] High CVE-2013-2922: Use-after-free in template element. Cre=
dit
to Jon Butler.=20

As usual, our ongoing internal security work responsible for a wide range of
fixes:
[299016] CVE-2013-2923: Various fixes from internal audits, fuzzing and oth=
er
initiatives (Chrome 30).
[275803] Medium CVE-2013-2924: Use-after-free in ICU. Upstream bug here.

We would also like to thank Atte Kettunen, cloudfuzzer and miaubiz for work=
ing
with us during the development cycle to prevent security bugs from ever
reaching the stable channel. $8000 in additional rewards were issued.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

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

summary: Chrome 30.0.1599.69 was released !


body:
From http://lists.gnupg.org/pipermail/gnupg-announce/2013q4/000333.html

What's New in 2.0.22
====================

 * Fixed possible infinite recursion in the compressed packet
   parser. [CVE-2013-4402]
 * Improved support for some card readers.
 * Prepared building with the forthcoming Libgcrypt 1.6.
 * Protect against rogue keyservers sending secret keys.

Also GnuPG 1.4.15 contains the fix.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: GnuPG 2.0.22 and 1.4.15 fix denial of service through infinite recursion in the compressed packet parser CVE-2013-4402


body:
Startup messages:

2013-10-05T21:22:10.822326+02:00 lisa-neu systemd[1]: Starting ProFTPd FTP
server...
2013-10-05T21:22:10.827515+02:00 lisa-neu systemd[1]: Started ProFTPd FTP
server.
2013-10-05T21:22:10.842965+02:00 lisa-neu proftpd[32506]: xxxx proftpd[32506]:
unable to bind to Unix domain socket at '/var/run/proftpd/test.sock': No such
file or directory
2013-10-05T21:22:10.864765+02:00 lisa-neu proftpd[32506]: xxxx proftpd[32506]:
processing configuration directory '/etc/proftpd/conf.d'
2013-10-05T21:22:10.876996+02:00 lisa-neu proftpd[32506]: xxxx proftpd[32506]
lisa-neu: mod_delay/0.7: error opening DelayTable
'/var/run/proftpd/proftpd.delay': No such file or directory
2013-10-05T21:22:11.030690+02:00 lisa-neu proftpd[32506]: xxxx proftpd[32506]
lisa-neu: error opening scoreboard: Operation not permitted

I think the systemd configuration should create the directory as well as the
old systemV script does.

Reproducible: Always

Steps to Reproduce:
1. reboot
2.
3.
Actual Results:
proftpd does not start

Expected Results:
should start

Easy to fix

summary: proftpd fails to start due to missing /var/run/proftpd


body:
In the default configuration the new openSUSE KDM theme has no field to enter a
user name, but just the user list.
I'm using NIS for user authentication and the user list is only populated with
user names that have logged in to the system before.
Because the user list does not contain users that have not logged in to this
machine one can not log in with another user that has not logged in before.
And after a fresh installation you can't even log in with any user, because the
user list is empty.

Therefore please add a user name field to the theme in the standard
configuration.

Reproducible: Always

summary: KDM Theme: No user name field


body:
Firefox/24.0

wrmsr executable included in msr-tools-1.2-43.4.x86_64.rpm cannot write 64b=
it
value to MSR. Only low 32bits are written.

Disassembled code for wrmsr :

  400aca:       e8 41 fe ff ff          call   400910 <strtoull@plt>
  400acf:       41 83 fc ff             cmp    r12d,0xffffffff
  400ad3:       4c 63 e8                movsxd r13,eax      -> return value
from strtoull() is treated as 32bits (eax instead of rax). This is where
truncation occurs.
  400ad6:       74 10                   je     400ae8 <__sprintf_chk@plt+0x=
148>
  400ad8:       44 89 e2                mov    edx,r12d
  400adb:       4c 89 ee                mov    rsi,r13      -> truncated va=
lue
is passed to wrmsr_on_cpu()
  400ade:       44 89 ff                mov    edi,r15d
400ae1:       e8 9a 01 00 00          call   400c80 <__sprintf_chk@plt+0x2e=
0>

It seems like OpenSuse packager of msr-tools has a wrong prototype of
strtoull() or they do not even have a prototype declared.

Reproducible: Always

Steps to Reproduce:
Example :
Try setting CQoS per core// Successful
# wrmsr =E2=80=93p 1 0xc8f 1
# rdmsr =E2=80=93p 1 0xc8f
1

Try setting CQoS, second attempt //Unsuccessful=20
# wrmsr =E2=80=93p 0 0xc8f 0x10000000
# rdmsr =E2=80=93p 0 0xc8f
0

Expected Results:=20=20
0x10000000

msr-tools are moved to 01.org/msr-tools, which directs to the latest (versi=
on
1.3) source code repository at github.com/01org/msr-tools .
Version 1.3 added cpuid utility. Please update with the latest code.

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

summary: wrmsr in msr-tools fails to write whole 64 bits value


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

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

           Summary: inst_prepdisk fails when instaling
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: YaST2
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: behlert-at-suse.com
         QAContact: jsrain-at-suse.com
          Found By: Customer
           Blocker: ---

Installation on a Laptop with two hard drives failes with
"Calling the YaST module `inst_prepdisk has failed."

The corresponding error line in yast2log:

=======================
yast/wfm.rb:86 Client call failed with bignum too big to convert into `long
long' and backtrace ["/usr/lib64/ruby/vendor_ruby/2.0.0/yast/scr.rb:50:in
`call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/scr.rb:50:in
`call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/scr.rb:12:in
`Write'", "/mounts/mp_0001/usr/share/YaST2/clients/inst_prepdisk.rb:52:in
`main'", "/mounts/mp_0001/usr/share/YaST2/clients/inst_prepdisk.rb:195:in `<top
(required)>'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin_wrapper'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:71:in `CallFunction'",
"/mounts/mp_0001/usr/share/YaST2/modules/ProductControl.rb:1513:in `RunFrom'",
"/mounts/mp_0001/usr/share/YaST2/clients/inst_mode.rb:326:in `main'",
"/mounts/mp_0001/usr/share/YaST2/clients/inst_mode.rb:532:in `<top
(required)>'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin_wrapper'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:71:in `CallFunction'",
"/mounts/mp_0001/usr/share/YaST2/modules/ProductControl.rb:1513:in `RunFrom'",
"/mounts/mp_0001/usr/share/YaST2/modules/ProductControl.rb:1691:in `Run'",
"/mounts/mp_0001/usr/share/YaST2/clients/inst_worker_initial.rb:108:in `main'",
"/mounts/mp_0001/usr/share/YaST2/clients/inst_worker_initial.rb:129:in `<top
(required)>'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin_wrapper'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:71:in `CallFunction'",
"/mounts/mp_0001/usr/share/YaST2/clients/installation.rb:67:in `main'",
"/mounts/mp_0001/usr/share/YaST2/clients/installation.rb:93:in `<top
(required)>'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval'",
"/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client'"]

=================

Full yast2logs are coming in the next minute.

summary: inst_prepdisk fails when instaling


body:
Recently in /etc/amavisd.conf /var/run used with clamav was replaced by /run,
however there are other locations in that file that sill have /var/run in it.
Shouldn't these be replaced as well?

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: amavis received a change where /var/run was replaced with /run still /var/run is present


body:
Hello,

I tried my 12.3 autoyast script and some features did not work.

1) Firewall settings not respected.

Even with:

  <firewall>
    <enable_firewall config:type=3D"boolean">false</enable_firewall>
    <start_firewall config:type=3D"boolean">false</start_firewall>
  </firewall>

When running installation, at the point that I'm able to configure the setu=
p,
firewall will apear as enable.

2) Defined root password is forgot:

This question apears correcly. However, when running installation, at the p=
oint
that I'm able to configure the setup, root is shown as without password. If
installed, root does not have a password.

The msgs are in pt_BR and they mean:
"Senha do root" "Root password"
"Digite a senha do root:" "Type the root password:"
"Digite a senha que vai ser utilizada pelo usu=C3=A1rio root." "Type the pa=
ssword
that user root will use."

I kept them in pt_BR because it could be something regard utf8.=20

    <ask-list config:type=3D"list">
      <ask>
        <title>Senha do root</title>
        <pathlist config:type=3D"list">
            <path>users,0,user_password</path>
        </pathlist>
        <question>Digite a senha do root:</question>
        <stage>initial</stage>
        <help>Digite a senha que vai ser utilizada pelo usu=C3=A1rio root.<=
/help>
        <password config:type=3D"boolean">true</password>
      </ask>
   </ask-list>
(...)
  <users config:type=3D"list">
    <user>
      <fullname>root</fullname>
      <gid>0</gid>
      <home>/root</home>
      <shell>/bin/bash</shell>
      <uid>0</uid>
      <username>root</username>
    </user>
</users>

3) sysconfig confs are not applied:

I use the configs bellow. None of them got applied after installation.

  <sysconfig config:type=3D"list">
    <sysconfig_entry>
      <sysconfig_key>DISPLAYMANAGER</sysconfig_key>
      <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path>
      <sysconfig_value>kdm</sysconfig_value>
    </sysconfig_entry>
    <sysconfig_entry>
      <sysconfig_key>DISPLAYMANAGER_KDM_THEME</sysconfig_key>
      <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path>
      <sysconfig_value>xxx</sysconfig_value>
    </sysconfig_entry>
    <sysconfig_entry>
      <sysconfig_key>DISPLAYMANAGER_ROOT_LOGIN_LOCAL</sysconfig_key>
      <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path>
      <sysconfig_value>yes</sysconfig_value>
    </sysconfig_entry>
  </sysconfig>

kdm is installed correctly (package selecion works) but DISPLAYMANAGER is e=
mpty
after the installation. I got an old xdm screen.

4) No second stage:

I use this mode setup:

    <mode>
      <confirm config:type=3D"boolean">true</confirm>
      <final_halt config:type=3D"boolean">false</final_halt>
      <final_reboot config:type=3D"boolean">true</final_reboot>
      <halt config:type=3D"boolean">false</halt>
      <second_stage config:type=3D"boolean">true</second_stage>
    </mode>

But no second stage apears. So, my second stage scripts did not run.

5) proxy settings is not read

I use these settings:

  <proxy>
    <enabled config:type=3D"boolean">true</enabled>
    <ftp_proxy>http://proxy.xxx:3128</ftp_proxy>
    <http_proxy>http://proxy.xxx:3128</http_proxy>
    <https_proxy>http://proxy.xxx:3128</https_proxy>
    <no_proxy>localhost, 127.0.0.1</no_proxy>
    <proxy_password></proxy_password>
    <proxy_user></proxy_user>
  </proxy>

But no proxy is defined in /etc/sysconfig/proxy after installation.

Reproducible: Always

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

summary: Autoyast is missing features from OS12.3


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

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

           Summary: PPC64: generic glibc should not be built with POWER4 optimizations
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: PowerPC-64
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: schwab-at-suse.com
        ReportedBy: agraf-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: dvaleev-at-suse.com
          Found By: ---
           Blocker: ---

The non-optimized version of glibc gets built with POWER4 optimizations:

%ifarch ppc ppc64
 %define optimize_power 1
 %ifarch ppc
 %define powerpc_optimize_base power3
 %define powerpc_optimize_tune power3
 %define powerpc_optimize_cpu_power4 %{normal_build}
 %else
 %define powerpc_optimize_base power4
 %define powerpc_optimize_tune power5
 %define powerpc_optimize_cpu_power4 0
 %endif

which ends up enabling the following code path in memset:

$ grep 128 glibc-2.18/sysdeps/powerpc/powerpc64/power4/*
glibc-2.18/sysdeps/powerpc/powerpc64/power4/memset.S:/* Clear lines of memory
in 128-byte chunks.  */
glibc-2.18/sysdeps/powerpc/powerpc64/power4/memset.S:    li      rCLS,128  /*
cache line size is 128 */

This breaks on FSL e5500 and PA-Semi PA6T CPUs which are capable of execution
PPC64 code, but only have 64 byte cache line size. I see two ways out of this:

  1) Compile glibc without any specific IBM POWER optimizations
  2) Remove the POWER4 memset(0) optimization to do the normal dynamic code
generic code has:

$ diff -u glibc-2.18/sysdeps/powerpc/powerpc64/memset.S
glibc-2.18/sysdeps/powerpc/powerpc64/power4/memset.S
-


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

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

           Summary: gnome build 0038 lacks branded wallpaper
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 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: lnussel-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

gnome in build 0038 lacks a branded wallpaper. It only has a gray background.


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

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

           Summary: mnemonics cannot be disabled in gnome-terminal - Highly annoying
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: GNOME
        AssignedTo: bnc-team-gnome-at-forge.provo.novell.com
        ReportedBy: aj-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: dimstar-at-opensuse.org
          Found By: Product Management
           Blocker: ---

Pressing Alt-F (while editing my bash command line) in gnome-terminal opens the
menu - but I disabled the mnemonics option.

It looks like we need this patch:
https://mail.gnome.org/archives/commits-list/2013-September/msg08712.html


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

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

           Summary: screen lock does not ask for password
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: GNOME
        AssignedTo: bnc-team-gnome-at-forge.provo.novell.com
        ReportedBy: aj-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: dimstar-at-opensuse.org
          Found By: Product Management
           Blocker: ---

I'm using NIS for password authentification and when I lock my screen, it goes
dark - but then I press ESC and it unlocks without asking for a password.

Related bug reports:
https://bugzilla.redhat.com/show_bug.cgi?id=1013721
https://bugs.freedesktop.org/show_bug.cgi?id=70005

This is a security relevant regressions, thus marking as Critical

summary: screen lock does not ask for password


body:
From 13.1, ibus's translation files are separated into a sub package,
ibus-lang. However, since main package of ibus does not have "Recommends:
ibus-lang", ibus-lang is not installed automatically.

Note that this problem have been already fixed on M17N and Factory
(ibus-1.5.4).

https://build.opensuse.org/package/show/home:ftake:branches:openSUSE:13.1/ibus

Reproducible: Always

Steps to Reproduce:
1. Install openSUSE 13.1 Beta 1 in Japanese
2. Log in KDE
3. Run ibus-set-up

summary: IBus's UI is not translated


body:
Backup scripts rely heavily on ssh. On openSUSE 12.3, the sshd hangs when the
remote hosts's rsync-target disk is full.

local:# rsync ... localdir remote:/backup

On remote:, rsync completes successfully and exits. sshd does not exit:

remote# ps aux|grep sshd
root    1627  0.0  0.0  44152   876 ?    Ss   Oct08   0:00 /usr/sbin/sshd -D
root   28419  3.4  0.1 101752  7644 ?    Ss   02:23  17:58 sshd: root@notty

There are no leftovers from updated packages:
remote# zypper ps
No processes using deleted files found.

remote# lsof -p 28419
sshd  28419 root    2u  unix 0xffff880134ac0140   0t0    11550 socket
sshd  28419 root    3u  IPv4        2325057   0t0      TCP
remote:ssh->local:36368 (ESTABLISHED)
sshd  28419 root    4u  unix 0xffff8800127f8b40   0t0 2325134 socket
sshd  28419 root    5r  FIFO            0,8   0t0 2325155 pipe
sshd  28419 root    6w  FIFO            0,8   0t0 2325155 pipe
sshd  28419 root    7w  FIFO           0,16   0t0 2325137
/run/systemd/sessions/168.ref
sshd  28419 root   10r  FIFO            0,8   0t0 2325157 pipe

remote# lsof -p 1627
sshd  1627 root    0r    CHR           1,3  0t0   1568 /dev/null
sshd  1627 root    1u  unix 0xffff880134ac0140  0t0  11550 socket
sshd  1627 root    2u  unix 0xffff880134ac0140  0t0  11550 socket
sshd  1627 root    3u  IPv4         11592  0t0    TCP *:ssh (LISTEN)
sshd  1627 root    4u  IPv6         11602  0t0    TCP *:ssh (LISTEN)

remote# d /proc/28419/fd/
dr-x----

summary: ssh hangs on full disk


body:
Hi,

updating from 12.3 to recent factory-snapshot adds a comment line to
/etc/SuSE-release which is not correctly parsed by lsb_release. IMO this is a
cosmetical show stopper for 13.1 release

$ cat /etc/SuSE-release
# /etc/SuSE-release is deprecated and will be removed in the future, use
/etc/os-release instead
openSUSE 13.1 (x86_64)
VERSION = 13.1
CODENAME = Bottle

$ lsb_release -a
LSB Version:
core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
Distributor ID:
#/etc/SuSE-releaseisdeprecatedandwillberemovedinthefuture,use/etc/os-releaseinstead
Description:    # /etc/SuSE-release is deprecated and will be removed in the
future, use /etc/os-release instead
Release:        n/a
Codename:       n/a

And this is also related to update-bootloader bug #833962 because it makes it
into the grub boot menu:
$ grep title  /boot/grub/menu.lst
title Desktop

summary: update breaks lsb_release and /etc/SuSE-release


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

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

           Summary: xfce4-session can't logout/restart/shutdown
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: x86-64
        OS/Version: SUSE Other
            Status: ASSIGNED
          Severity: Major
          Priority: P5 - None
         Component: Xfce
        AssignedTo: gber-at-opensuse.org
        ReportedBy: rmilasan-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: L3
           Blocker: ---

Running currently up to date Xfce 4.10.1 x86_64 on openSUSE 13.1. While
everything works, when logged in Xfce, the user can't logout, restart,
shutdown.

First try to logout, nothing happens, second try an error message pops up:

Received error while trying to log out
Session manager must be in idle state when requesting a shutdown

I've googled a bit the issue, but this shouldn't happen in 4.10.1, but in older
version (at least according to what I found online).

I'll attach a screenshot of the error, might help a bit.

NOTE: trying manually with xfce4-session-logout -l, -r or -h ends up in the
same error.

Just to be on the safe side, don't know if matters, tried using gdm as a DM and
its still the same, so it happens with both lightdm and gdm.


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

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

           Summary: lightdm 1.8.0 potential crashes
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: Other
               URL: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug
                    /1207935
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
        AssignedTo: gber-at-opensuse.org
        ReportedBy: gber-at-opensuse.org
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

lightdm 1.8.0 may crash because it does not remove a timeout callback when
unref'ing process objects which subsequently tries to access the free'd object.
See upstream bug fro further details.

summary: lightdm 1.8.0 potential crashes


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

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

           Summary: lightdm-gtk-greeter crashes when its state file refers to a session no longer available
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: Other
               URL: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/11
                    61883
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
        AssignedTo: gber-at-opensuse.org
        ReportedBy: gber-at-opensuse.org
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

lightdm-gtk-greeter crashes when its state file refers to a session no longer
available. See the upstream bug for further details.


body:
If I start KDE4 it lasts extremely long until the plasma desktop panel appears
(5 minutes?); likewise it also lasts extremely long to start dolphin; even
starting kde3-konqueror from an xchroot-environment lasts longer than expected.
Possibly a dbus or even more likely a kernel issue (see also: bug 845284).

Reproducible: Always

summary: launching new applications lasts extremely long (beta1)


body:
On a System with following patterns installed:
      x11
      kde4
      yast2_basis
      kde4_basis
      enhanced_base
      base
      fonts

After installing nfs-kernel-server the systemd nfsserver.service file can not
be found. Which should be clear, as the nfs server should be started with
fallback to the sysvinit script.

test-vm:/etc/sysconfig/network # zypper in nfs-kernel-server
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW package is going to be installed:
  nfs-kernel-server

1 new package to install.
Overall download size: 112.0 KiB. After the operation, additional 429.7 KiB
will be used.
Continue? [y/n/?] (y):
Retrieving package nfs-kernel-server-1.2.8-4.1.2.i586

(1/1), 112.0 KiB (429.7 KiB unpacked)
Retrieving: nfs-kernel-server-1.2.8-4.1.2.i586.rpm
.......................................................................................................................................................................................................[done
(312.7 KiB/s)]
(1/1) Installing: nfs-kernel-server-1.2.8-4.1.2
........................................................................................................................................................................................................................[done]
test-vm:/etc/sysconfig/network # systemctl start nfsserver.service
Failed to issue method call: Unit nfsserver.service failed to load: No such
file or directory. See system logs and 'systemctl status nfsserver.service' for
details.
test-vm:/etc/sysconfig/network # systemctl status nfsserver.service
nfsserver.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
test-vm:/etc/sysconfig/network # /etc/init.d/nfsserver status
Checking for kernel based NFS server: idmapd

                    unused
 mountd

                    unused
 statd

                    unused
 nfsd

                    unused
nfsserver.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

test-vm:/etc/sysconfig/network # /etc/init.d/nfsserver start
redirecting to systemctl start nfsserver
Failed to issue method call: Unit nfsserver.service failed to load: No such
file or directory. See system logs and 'systemctl status nfsserver.service' for
details.

Reproducible: Always

Steps to Reproduce:
1. Install nfs-kernel-server
2. Start nfsserver with rcnfsserver start, /etc/init.d/nfsserver start or
systemctl start nfsserver.service

Actual Results:
/etc/init.d/nfsserver start
redirecting to systemctl start nfsserver
Failed to issue method call: Unit nfsserver.service failed to load: No such
file or directory. See system logs and 'systemctl status nfsserver.service' for
details.

Expected Results:
The NFS server should start

The installation was done from the openSUSE_13.1 online repository 11. Oct 2013
08:00 UTC

summary: No systemd unit file fount for nfs-kernel-server


body:
After installation from KDE live DVD 32 bit, the date command and the clock in
the system tray always show UTC rather than local time.

This is caused by a broken link created by the Date and Time module of YaST2.
/etc/localtime points to ../../Europe/Berlin, which can't work. After setting
the link manually to /usr/share/zoneinfo/Europe/Berlin, local time is displayed
as expected.

Reproducible: Always

summary: UTC displayed rather than local time in OS13.1 RC1


body:
When clicking the Add button in the Network Settings module to assign an
additional IP address to an interface, a message box "Internal error. Please
report a bug" is displayed and the module terminates.

As far as I remember, this problem did not occur in OS 13.1 Beta.

Reproducible: Always

Installation was done from KDE Live DVD 32 bit.

summary: YaST2 Network Settings crash in OS 13.1 RC1


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

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

           Summary: console fonts messed up in live medium
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Live Medium
        AssignedTo: coolo-at-suse.com
        ReportedBy: lnussel-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

the consolefonts are messed up in the live boot. My guess is that
langset.service runs after systemd-vconsole-setup.service as manually calling
systemd-vconsole-setup fixes the issues. I don't know where langset comes from
though...

summary: console fonts messed up in live medium


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

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

           Summary: libvirtd segfaulting on start in current Factory
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: KVM
        AssignedTo: kvm-bugs-at-forge.provo.novell.com
        ReportedBy: seife-at-novell.slipkontur.de
         QAContact: jdouglas-at-suse.com
          Found By: Third Party Developer/Partner
           Blocker: ---

Current factory;
susi:~ # rpm -qa libvirt*
libvirt-python-1.1.2-4.1.x86_64
libvirt-daemon-driver-nwfilter-1.1.2-4.1.x86_64
libvirt-daemon-driver-nodedev-1.1.2-4.1.x86_64
libvirt-daemon-driver-qemu-1.1.2-4.1.x86_64
libvirt-daemon-config-nwfilter-1.1.2-4.1.x86_64
libvirt-daemon-driver-network-1.1.2-4.1.x86_64
libvirt-daemon-driver-xen-1.1.2-4.1.x86_64
libvirt-daemon-1.1.2-4.1.x86_64
libvirt-daemon-driver-lxc-1.1.2-4.1.x86_64
libvirt-daemon-driver-secret-1.1.2-4.1.x86_64
libvirt-daemon-driver-vbox-1.1.2-4.1.x86_64
libvirt-daemon-driver-uml-1.1.2-4.1.x86_64
libvirt-1.1.2-4.1.x86_64
libvirt-daemon-driver-libxl-1.1.2-4.1.x86_64
libvirt-daemon-driver-storage-1.1.2-4.1.x86_64
libvirt-client-1.1.2-4.1.x86_64
libvirt-daemon-driver-interface-1.1.2-4.1.x86_64
susi:~ # libvirtd --listen
Caught Segmentation violation dumping internal log buffer:

    ====== start of log =====

2013-10-11 15:05:00.146+0000: 23589: debug : virLogParseOutputs:1336 :
outputs=3:stderr
2013-10-11 15:05:00.146+0000: 23589: debug : virObjectNew:199 : OBJECT_NEW:
obj=0x7fe403ac6a20 classname=virAccessManagerClass
2013-10-11 15:05:00.146+0000: 23589: debug : virAccessManagerNewDriver:105 :
Initialized with stack
2013-10-11 15:05:00.146+0000: 23589: debug : virObjectNew:199 : OBJECT_NEW:
obj=0x7fe403aca200 classname=virAccessManagerClass
2013-10-11 15:05:00.146+0000: 23589: debug : virAccessManagerNewDriver:105 :
Initialized with none
2013-10-11 15:05:00.146+0000: 23589: debug : virObjectRef:293 : OBJECT_REF:
obj=0x7fe403ac6a20
2013-10-11 15:05:00.146+0000: 23589: debug : virObjectUnref:256 : OBJECT_UNREF:
obj=0x7fe403ac6a20
2013-10-11 15:05:00.146+0000: 23589: debug : main:1295 : Decided on pid file
path '/var/run/libvirtd.pid'
2013-10-11 15:05:00.146+0000: 23589: debug : main:1305 : Decided on socket
paths '/var/run/libvirt/libvirt-sock' and '/var/run/libvirt/libvirt-sock-ro'
2013-10-11 15:05:00.146+0000: 23589: debug : main:1341 : Ensuring run dir
'/var/run/libvirt' exists
2013-10-11 15:05:00.146+0000: 23589: debug : virFileMakePathHelper:2011 :
path=/var/run/libvirt mode=0777
2013-10-11 15:05:00.146+0000: 23589: debug : virNetlinkStartup:136 : Running
global netlink initialization
2013-10-11 15:05:00.146+0000: 23589: debug : virObjectNew:199 : OBJECT_NEW:
obj=0x7fe403aca600 classname=virNetServer
2013-10-11 15:05:00.146+0000: 23589: debug : virEventRegisterDefaultImpl:230 :
registering default event implementation
2013-10-11 15:05:00.146+0000: 23589: debug : virEventPollAddHandle:111 : Used 0
handle slots, adding at least 10 more
2013-10-11 15:05:00.146+0000: 23589: debug : virEventPollInterruptLocked:710 :
Skip interrupt, 0 0
2013-10-11 15:05:00.146+0000: 23589: debug : virEventPollAddHandle:136 :
EVENT_POLL_ADD_HANDLE: watch=1 fd=5 events=1 cb=0x7fe401e56410 opaque=(nil)
ff=(nil)
2013-10-11 15:05:00.146+0000: 23589: debug : virEventRegisterImpl:203 :
addHandle=0x7fe401e56a60 updateHandle=0x7fe401e56da0
removeHandle=0x7fe401e56450 addTimeout=0x7fe401e565b0
updateTimeout=0x7fe401e56780 removeTimeout=0x7fe401e56900
2013-10-11 15:05:00.146+0000: 23589: debug : main:1381 : Dropping privileges
(if required)
2013-10-11 15:05:00.146+0000: 23589: debug : virDriverModuleInitialize:53 :
Module dir /usr/lib64/libvirt/connection-driver
2013-10-11 15:05:00.146+0000: 23589: debug : virDriverLoadModule:66 : Module
load network
2013-10-11 15:05:00.147+0000: 23589: debug : virRegisterNetworkDriver:611 :
registering Network as network driver 3
2013-10-11 15:05:00.147+0000: 23589: debug : virDriverLoadModule:66 : Module
load storage
2013-10-11 15:05:00.147+0000: 23589: debug : virRegisterStorageDriver:665 :
registering storage as storage driver 3
2013-10-11 15:05:00.147+0000: 23589: debug : virDriverLoadModule:66 : Module
load nodedev
2013-10-11 15:05:00.148+0000: 23589: debug : udevNodeRegister:1823 :
Registering udev node device backend
2013-10-11 15:05:00.148+0000: 23589: debug : virRegisterNodeDeviceDriver:692 :
registering udevNodeDeviceDriver as device driver 3
2013-10-11 15:05:00.148+0000: 23589: debug : virDriverLoadModule:66 : Module
load secret
2013-10-11 15:05:00.148+0000: 23589: debug : virRegisterSecretDriver:719 :
registering secret as secret driver 3
2013-10-11 15:05:00.148+0000: 23589: debug : virDriverLoadModule:66 : Module
load nwfilter
2013-10-11 15:05:00.149+0000: 23589: debug : virRegisterNWFilterDriver:746 :
registering nwfilter as network filter driver 3
2013-10-11 15:05:00.149+0000: 23589: debug : virDriverLoadModule:66 : Module
load interface

     ====== end of log =====

Segmentation fault


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

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

           Summary: [bluez5] NM fails to create NAP connections
    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
            Blocks: 844041
          Found By: ---
           Blocker: ---

NM 0.9.8.6, as shipped in RC1, fails to create NAP connections over bluez5;

NM 0.9.8.8 has been released with fixes around Bluez5 support. The NEWS file
says:

+This is a new stable release of NetworkManager. Notable changes include:
+
+* Fixes to the BlueZ code
+* A few memory leak fixes
+* Minor docs fixes


body:
Building the kiwi images from the descriptions in the package
"kiwi-config-openSUSE" fails.

Reproducible: Always

Steps to Reproduce:
1. Install the kiwi build system and the package kiwi-config-openSUSE
2. $ kiwi -p /usr/share/openSUSE-kiwi/livecd-x11 -r /tmp/kiwiroot
Actual Results:
> Problem: package-lists-openSUSE-X11-cd-11.4-27.1.x86_64 requires branding-openSUSE, but this requirement cannot be provided
>   uninstallable providers: branding-openSUSE-13.1-10.3.6.noarch[http:__download.opensuse.org_distribution_13.1_repo_oss]
>  Solution 1: Following actions will be done:
>   deinstallation of branding-basedonopensuse-13.1-3.1.4.x86_64
>   deinstallation of systemd-presets-branding-basedonopensuse-13.1-3.1.4.x86_64
>  Solution 2: do not install package-lists-openSUSE-X11-cd-11.4-27.1.x86_64
>  Solution 3: break package-lists-openSUSE-X11-cd-11.4-27.1.x86_64 by ignoring some of its dependencies

livecd-kde generates a similar error.  I tested on 64bit architecture, within a
VirtualBox.

summary: kiwi-config-openSUSE live images fails to build, due to package conflicts


body:
According to http://en.opensuse.org/openSUSE:Package_group_guidelines
Haskell libraries needed by applications should be in group System/Libraries
not Development/Languages/Other. Likewise devel packages for those
Haskell libraries should be in Development/Libraries/Other.

Reproducible: Always

Steps to Reproduce:
1. read metadata for ghc-base and ghc-base-devel
2.
3.
Actual Results:
In both cases Group Development/Languages/Other

Expected Results:
System/Libraries for ghc-base
Development/Libraries/Other

Thanks to Scott Bahling for pointing this out and for sending a patch for
ghc-rpm-macros.

The issue currently applies only libraries that come with the Haskell compiler
ghc.

Scott's patch will also allow us to build Haskell packages on SLE again.

summary: Haskell shared libraries wring metadata in rpms (wrong package group)


body:
..as summarized...

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Expected Results:
kde-gtk-config should be present on the system

summary: No application for changing GTK themes is installed on system


body:
found in: openSUSE 13.1 RC1, 32bit, installed from DVD image

When I run the YaST2 snapper module, it crashes with signal 11 when/after
reading the list of snapshots:

lthendrik:/home/hendrik #YaST2 snapper
YaST got signal 11 at YCP file /usr/share/YaST2/modules/Snapper.rb:181
/sbin/YaST2: line 375:  1629 Segmentation fault      $ybindir/y2base $module
"$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

Reproducible: Always

Steps to Reproduce:
1. Start the YaST2 snapper modul
2.
3.

summary: YaST2 snapper: Segmentation fault in /usr/share/YaST2/modules/Snapper.rb:181


body:
According to https://bugs.kde.org/show_bug.cgi?id=325909 Okular crashes because
of a bug in libepub 0.2.1 and I could reproduce the crash with current 13.1
repo.

According to http://sourceforge.net/projects/ebook-tools/ version 0.2.2 has
long been available, so it should be a safe update.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: Please update libepub to 0.2.2


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

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

           Summary: openstack-db not working
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
        AssignedTo: dmueller-at-suse.com
        ReportedBy: aj-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: Product Management
           Blocker: ---

Using Cloud:OpenStack:Havana, openstack-db is not working:

controller:~ # openstack-db --init --service keystone --password
KEYSTONE_DBPASS
mysql-server is not installed.  Would you like to install it now? (y/n): y
/usr/bin/openstack-db: line 91: yum: command not found
mysqld is not running.  Would you like to start it now? (y/n):

I have mysql-community-server installed and running, the scripts seem to miss
some support for openSUSE.

summary: openstack-db not working


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

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

           Summary: Yast cannot be launched twice from gnome-control-center
    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
          Found By: ---
           Blocker: ---

Launchin g-c-c and then yast works fine, but relaunching yast without first
entering any of the other panels fails.


body:
After solving the problem of broken virtual machine manager (VMM) in case of
not runnimg libvirtd, because qemu has not been installed by yast, I tried to
install a test-instance OS13.1RC1, using VMM. After doing the configuration and
short after starting the installation, I got an errormessage ( see picture
Error2.png).
Hardware-Info : Notebook with 16 GB Core, Intel(R) Core(TM) i7-3630QM CPU @
2.40GHz, 500GB ssd plis 700GB SATA HD, Realtek RTL8111/8168B PCI Express
Gigabit Ethernet controller, Intel VGA compatible controller plus NVIDIA
Corporation Device 11a7.

Reproducible: Always

Steps to Reproduce:
1.installing qemu - Universal CPU emulator, libvirt-daemon-qemu,
libvirt-daemon-driver-qemu and other packages needed for libvirtd.
2.starting virtual machine manager, click VM-Install, click Forward to install
operating system openSUSE 13 and configuring hardware requirements.
3.two or three seconds after pressing the OK butten I got the errormessage.
Actual Results:
Installation of VM stopped as you see at the screenshot.
Ahter pressing the OK button of the error message, you fall back into the
configuration menue.

Expected Results:
written Configfile in /etc/xen/vm :
name="OS13.1RC1"
description="Test"
uuid="1cff93f1-e177-d55e-d87c-b4e6286c084f"
memory=2048
maxmem=2048
vcpus=2
on_poweroff="destroy"
on_reboot="destroy"
on_crash="destroy"
localtime=0
keymap="de"
builder="linux"
kernel="/tmp/kernel.PDLID9"
ramdisk="/tmp/install-initrd.IlthEQ"
extra=" install=hd:/dev/xvdb "
disk=[ 'file:/var/lib/xen/images/OS_13.1_RC1.raw,xvda,w',
'file:/var/lib/xen/images/openSUSE-13.1-DVD-Build0041-x86_64.iso,xvdb:cdrom,r',
]
vif=[ 'mac=00:16:3e:22:03:7e,bridge=br0', ]
vfb=['type=vnc,vncunused=1']

Starting this config  with command :xl create OS13.1RC1
gives the result :
 Parsing config from OS13.1RC1
libxl: error: libxl_dom.c:353:libxl__build_pv: xc_dom_kernel_file failed: No
such file or directory
libxl: error: libxl_create.c:900:domcreate_rebuild_done: cannot (re-)build
domain: -3

summary: libxenlight failed to create new domain


body:
Although GNOME's keyboard indicator now shows local modes of each engine, but,
for other DEs, ibus-ui-gtk3 shows only the icon of an active engine. Users
thereby cannot understand the current input mode of the engine at a glance. It
is really annoying to type a key in order to see the current mode.

I have reported this problem to the upstream. The upstream developers had
recognized this problem, but they are still implementing a new indicator for
KDE, XFCE, and etc to fix this problem.

http://code.google.com/p/ibus/issues/detail?id=1659

A workaround for this problem is showing input mode icons that was used for
IBus's toolbar on 12.3 by a patch. Unfortunately, as far as I know, only
ibus-mozc has such icons. For other ibus-*, symbol characters assigned to input
modes as GNOME Shell does, but we need a more complicated patch since
Gtk.StatusIcon does not have APIs to print a character string on a status icon.

Patched packages are available from:
home:ftake:branches:openSUSE:13.1 (1.5.3) and M17N (1.5.4)

Reproducible: Always

summary: Cannot see the current input mode of IBus on KDE and XFCE


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

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

           Summary: SELinux policy issues with netconfig
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
        AssignedTo: vcizek-at-suse.com
        ReportedBy: vcizek-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

1) /dev/.sysconfig/network should be labeled with the correct type, otherwise
it will default to device_t. Running restorecon after creating that directory
will solve this.

2) Calling init scripts directly from netconfig scripts will get denied by the
policy. Prefer using systemctl where available.

summary: SELinux policy issues with netconfig


body:
If you enter "Configure Desktop"->"Login Screen" on a fresh installation, the
Bootloader setting is set to "None" (that's the kcm's hardcoded default).

Therefore if you change something else (like the theme f.e.) and save, the
Bootloader setting is saved as "None".
This in turn causes the "Restart" options, where you can select which OS to
boot, to be gone.

Reproducible: Always

summary: KDM's kcm resets Bootlader setting to "None"


body:
If during the installation I select to install the package libvirt-daemon , I
found this error in /var/log/zypp/history:

# 2013-10-13 18:00:10 libvirt-daemon-1.1.2-2.2.1.x86_64.rpm installed ok
# Additional rpm output:
# warning: user qemu does not exist - using root
# warning: group qemu does not exist - using root
# warning: user qemu does not exist - using root
# warning: group qemu does not exist - using root
# warning: user qemu does not exist - using root
# warning: group qemu does not exist - using root
# warning: user qemu does not exist - using root
# warning: group qemu does not exist - using root
# Updating /etc/sysconfig/libvirtd...
# Updating /etc/sysconfig/virtlockd...
#
2013-10-13
18:00:11|install|libvirt-daemon|1.1.2-2.2.1|x86_64||openSUSE-13.1-1.3|56745b18332e9af5e8f76c271736534e1351ea5270636cdc6a3b0c300709fe10|

The problem is that some files in libvirt-daemon package belongs to qemu:qemu
but at the time libvirt-daemon is installed user qemu and group qemu do not
exist. A possible fix is to add a preinstall scriplet that creates user and
group qemu or make libvirt-daemon PreReq a package that creates such user/group

Reproducible: Always

Steps to Reproduce:
1.Install 13.1 RC 1 adding the libvirt-daemon package
2.
3.
Actual Results:
There is a message in /var/log/zypp/history about user qemu does not exist -
using root and group qemu does not exist - using root

Expected Results:
no error message

summary: package libvirt-daemon: installation error


body:
If during the installation I select to install the package scim-gtk-32bit, I
found this error in /var/log/zypp/history:

# 2013-10-13 17:42:54 scim-gtk-32bit-1.4.14-7.1.3.x86_64.rpm installed ok
# Additional rpm output:
# /var/tmp/rpm-tmp.Z2OJjb: line 2: /etc/gtk-2.0/gtk.immodules: No such file or
directory
# warning: %post(scim-gtk-32bit-1.4.14-7.1.3.x86_64) scriptlet failed, exit
status 1
#
2013-10-13
17:42:54|install|scim-gtk-32bit|1.4.14-7.1.3|x86_64||openSUSE-13.1-1.3|8d537090edaff01902440c3aebc9f4dfb319dd7cb4ae09f81beb8ca982853844|

The problem is that scim-gtk-32bit execute the following postinstall scriptlet:
  /usr/bin/gtk-query-immodules-2.0 > /etc/gtk-2.0/gtk.immodules
which was ok for 12.3 but it is wrong for 13.1
The correct scriplet is (from libgtk-2_0-0-32bit):
  /usr/bin/gtk-query-immodules-2.0 --update-cache

Reproducible: Always

Steps to Reproduce:
1.Install 13.1 RC 1 adding the scim-gtk-32bit package
2.
3.
Actual Results:
There is a message in /var/log/zypp/history about postinstall scriptlet failed

Expected Results:
no error message

pkgs: fcitx ibus scim uim

summary: package scim-gtk-32bit: installation error


body:
Wrong apparmor profile.
My openSUSE 13.1 version apparmor-profiles-2.8.2-7.1.noarch &
samba-4.1.0-7.1.x86_64.
When I try to start smbd I get this error message:
type=1400 audit(1381780650.562:109): apparmor="DENIED" operation="open"
parent=23571 profile="/usr/sbin/smbd"
name="/usr/share/samba/codepages/upcase.dat" pid=23572 comm="smbd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
type=1400 audit(1381780650.562:110): apparmor="DENIED" operation="open"
parent=23571 profile="/usr/sbin/smbd"
name="/usr/share/samba/codepages/lowcase.dat" pid=23572 comm="smbd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
type=1400 audit(1381780650.564:111): apparmor="DENIED" operation="file_mmap"
parent=1 profile="/usr/sbin/smbd" name="/usr/lib64/samba/pdb/tdbsam.so"
pid=23573 comm="smbd" requested_mask="m" denied_mask="m" fsuid=0 ouid=0

Reproducible: Always

Steps to Reproduce:
1. systemctl start smb
2.
3.

summary: Samba error in apparmor profile


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

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

           Summary: console-kit-log-system-start.service fails to start - /var/log/ConsoleKit/ missing
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: Other
        OS/Version: openSUSE 12.3
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: suse-beta-at-cboltz.de
         QAContact: qa-bugs-at-suse.de
          Found By: Beta-Customer
           Blocker: ---

While checking the "systemctl --failed" output on a new server, I noticed that
console-kit-log-system-start.service fails to start because the directory
/var/log/ConsoleKit/ doesn't exist.

After   mkdir /var/log/ConsoleKit   I can start it without problems.

Version history of the affected system:
- fresh 12.3 installation
- zypper dup to 13.1 beta
- zypper dup to 13.1 rc1 (or whatever the 13.1 repo contains today)

Status output _before_ the mkdir call:
# systemctl status -l console-kit-log-system-start.service
console-kit-log-system-start.service - Console System Startup Logging
   Loaded: loaded
(/usr/lib/systemd/system/console-kit-log-system-start.service; static)
   Active: failed (Result: exit-code) since Mo 2013-10-14 22:42:51 CEST; 1min
42s ago
  Process: 1336 ExecStart=/usr/sbin/ck-log-system-start (code=exited,
status=1/FAILURE)
 Main PID: 1336 (code=exited, status=1/FAILURE)

Okt 14 22:42:51 karawane3 ck-log-system-start[1336]: ** (process:1336): WARNING
**: Couldn't create log file /var/log/ConsoleKit/history (No such file or
directory)
Okt 14 22:42:51 karawane3 systemd[1]: console-kit-log-system-start.service:
main process exited, code=exited, status=1/FAILURE
Okt 14 22:42:51 karawane3 systemd[1]: Failed to start Console System Startup
Logging.
Okt 14 22:42:51 karawane3 systemd[1]: Unit console-kit-log-system-start.service
entered failed state.


body:
Hello,

If I enter yast2 samba-client and save (without changes), my config is
preserved. Just minor formatting is changed. However, if I run:

 yast2 samba-client winbind enable

My smb.conf is changed like this:

 [global]
        include = /etc/samba/dhcp.conf
        workgroup = MYDOMAIN
-       realm = MYDOMAIN.ORG
-       security = ADS
+       security = domain
        winbind use default domain = yes
        kerberos method = secrets and keytab
        passdb backend = tdbsam
@@ -13,7 +12,6 @@
        idmap uid = 10000-20000
        template shell = /bin/bash
        winbind offline logon = yes
-       winbind refresh tickets = yes
        domain master = No
        domain logons = No

Reproducible: Always

Steps to Reproduce:
1.Configure domain seciruty as ADS
2.run yast2 samba-client winbind enable

Actual Results:
3. security is changed to domain. Realm and "winbind refresh tickets" is
removed.

Expected Results:
4. winbind should keep my settings, while enabling it. If needed, it could
change/add settings required for winbind but not what it did here.

summary: "yast2 samba-client winbind enable"  changes security to domain


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

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

           Summary: YaST2 modules don't open on 32-bit
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: x86
        OS/Version: SUSE Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: YaST2
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: jmason-at-suse.com
         QAContact: jsrain-at-suse.com
          Found By: Community User
           Blocker: ---

Installed from the 32-bit Live GNOME image of 13.1 RC1;

YaST2 launcher opens, but none of the modules will open.

Steps to reproduce:
Start YaST2 from gnome-shell
Click any YaST module icon
(observe the module *not* opening)

Alternate steps (CLI)
su --session-command YaST2 sw_single
(no response)

Modules work fine in as ncurses.

summary: YaST2 modules don't open on 32-bit


body:
I've defined a VPN connection based on OpenConnect - just the gateway is filled
in.

If I try to connect from the Network Management applet, nothing happens.

The only relevant bit that I see in the /var/log/NetworkManager is:

    <warn> connection /org/freedesktop/NetworkManager/Settings/2 failed to
activate: (2) The VPN service 'org.freedesktop.NetworkManager.openconnect' was
not installed.

Both openconnect and nm-plasma-openconnect are installed:

    openconnect-4.08-2.1.2.x86_64
    plasma-nm-openconnect-0.9.3.0-2.1.x86_64

Connecting using the CLI works fine.

Reproducible: Always

summary: VPN connection can not be started from plasma-nm-openconnect


body:
A 3rd party application which links to qt3 hangs after app. 15 hours of
running.
The application is multithreaded.
The stacktrace show that it blocks inside libxcb1.

Any help, how to fix this issue is highly appreciated :-)

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: GUI application blocks after 15 hours of running


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

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

           Summary: fontpackages rpm macro causes error at updating multiple packages
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
        AssignedTo: pgajdos-at-suse.com
        ReportedBy: tiwai-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When multiple packages calling %reconfigure_fonts_scriptlets are updated at the
same time, it eventually gets an error indicating "rm
/var/run/fontpackages/reconfigure-fonts-cjk" failed.

For example,

sudo zypper in -f vlgothic-fonts-20120325-21.6.noarch
x11-japanese-bitmap-fonts-20020904-1306.6.noarch
Loading repository data...
Warning: Repository 'repo-update-non-oss' appears to outdated. Consider using a
different mirror or server.
Reading installed packages...
Forcing installation of 'vlgothic-fonts-20120325-21.6.noarch' from repository
'M17N-fonts'.
Forcing installation of 'x11-japanese-bitmap-fonts-20020904-1306.6.noarch' from
repository 'M17N-fonts'.
Resolving package dependencies...

The following packages are going to be reinstalled:
  vlgothic-fonts x11-japanese-bitmap-fonts

2 packages to reinstall.
Overall download size: 13.8 MiB. No additional space will be used or freed
after the operation.
Continue? [y/n/?] (y):
Retrieving package vlgothic-fonts-20120325-21.6.noarch
                                           (1/2),   2.1 MiB (  7.6 MiB
unpacked)
Retrieving: vlgothic-fonts-20120325-21.6.noarch.rpm
.....................[done]
Retrieving package x11-japanese-bitmap-fonts-20020904-1306.6.noarch
                                           (2/2),  11.7 MiB ( 15.2 MiB
unpacked)
Retrieving: x11-japanese-bitmap-fonts-20020904-1306.6.noarch.rpm
........[done]
(1/2) Installing: vlgothic-fonts-20120325-21.6
..........................[done]
(2/2) Installing: x11-japanese-bitmap-fonts-20020904-1306.6
.............[done]
Running: vlgothic-fonts-20120325-21.6-reconfigure-fonts-cjk  (vlgothic-fonts,
/var/adm/update-scripts)
Running: vlgothic-fonts-20120325-21.6-reconfigure-fonts-cjk
(vlgothic-fon[done]
Running: vlgothic-fonts-20120325-21.6-reconfigure-fonts  (vlgothic-fonts,
/var/adm/update-scripts)
Creating fonts.{scale,dir} files ..........
/usr/share/fonts-config/conf.avail/12-suse-hinting-bc.conf unchanged
/usr/share/fonts-config/conf.avail/17-suse-bitmaps.conf unchanged
Creating cache files for fontconfig
..........................................................................
Creating 32bit cache files for fontconfig
..........................................................................
generating java font setup
Warning: cannot find a sans serif simplified Chinese font. Simplified Chinese
in Java might not work.
Warning: cannot find a serif simplified Chinese font. Simplified Chinese in
Java might not work.
Warning: cannot find a sans serif traditional Chinese font. Traditional Chinese
in Java might not work.
Warning: cannot find a serif traditional Chinese font. Traditional Chinese in
Java might not work.
Warning: cannot find a sans serif Korean font. Korean in Java might not work.
Warning: cannot find a serif Korean font. Korean in Java might not work.
writing /usr/lib64/jvm/jre/lib/fontconfig.SuSE.properties
Running: vlgothic-fonts-20120325-21.6-reconfigure-fonts  (vlgothic-fonts,
[done]
Running: x11-japanese-bitmap-fonts-20020904-1306.6-reconfigure-fonts-cjk
(x11-japanese-bitmap-fonts, /var/adm/update-scripts)
Running: x11-japanese-bitmap-fonts-20020904-1306.6-reconfigure-fonts-cjk
[done]
Running: x11-japanese-bitmap-fonts-20020904-1306.6-reconfigure-fonts
(x11-japanese-bitmap-fonts, /var/adm/update-scripts)
rm: cannot remove '/var/run/fontpackages/reconfigure-fonts-cjk': No such file
or directory
Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a):


body:
As discussed at
http://lists.opensuse.org/opensuse-factory/2013-10/msg00339.html , plasma-nm
has replaced NetworkManager-kde4 on 13.1 RC1 after a zypper dup, and this is
unintended.

Reproducible: Always

pkgs: libNetworkManagerQt plasma-nm

summary: plasma-nm incorrectly present in 13.1 post RC1


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

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

           Summary: dhcpcd is exiting when system configured using ifup
    Classification: openSUSE
           Product: openSUSE 12.3
           Version: Final
          Platform: x86-64
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
        AssignedTo: mt-at-suse.com
        ReportedBy: cwh-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I have a newly installed (not updated) 13.1 RC1 here.
It's configured to use ifup, not NetworkManager.

On reboot as well as 'rcnetwork restart' it fails to get a IPv4 address via
dhcp.
/var/log messages states:

enp2s0: dhcpcd not running
enp2s0: exiting

If I call

> ifup-dhcp enp2s0

it's working as expected: got IPv4 address, routes and DNS.

Any hints how to debug this?


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

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

           Summary: Too narrow window in fcitx-config-gtk3 input method addition dialog
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
        AssignedTo: i-at-marguerite.su
        ReportedBy: tiwai-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The input method selection dialog of fcitx-config-gtk3 gives a very narrow list
that can show up to two lines, and it's pretty nasty to choose from a long
list.
I tested on XFCE4.

- Open the config dialog from "Config" in the right pulldown menu on panel
icon.
- Open "Add input method" dialog via clicking "+" button at the bottom.
- The dialog has a list selection window of two lines.  See the screenshot.

I don't remember such an issue on 12.3, so it must be a regression in the
recent updates.

Marguerite, could you take a look?  Thanks.


body:
Hello,

The default profile is not allowing samba to work properly:

For winbind (for smb.conf.tresc, I use a symlink smb.conf -> smb.conf.tresc) :

type=1400 audit(1381783806.863:33): apparmor="DENIED" operation="open"
parent=2024 profile="/usr/sbin/winbindd"
name="/usr/share/samba/codepages/upcase.dat" pid=2025
type=1400 audit(1381783806.863:34): apparmor="DENIED" operation="open"
parent=2024 profile="/usr/sbin/winbindd"
name="/usr/share/samba/codepages/lowcase.dat" pid=2025 comm="winbindd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
type=1400 audit(1381783806.974:35): apparmor="DENIED" operation="open"
parent=2024 profile="/usr/sbin/winbindd" name="/etc/samba/smb.conf.tresc"
pid=2025 comm="winbindd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
type=1400 audit(1381784934.834:46): apparmor="DENIED" operation="rename_src"
parent=1 profile="/usr/sbin/winbindd"
name="/var/lib/samba/winbindd_cache.tdb.bak" pid=4664 comm="winbindd"
requested_mask="rwd" denied_mask="rwd" fsuid=0 ouid=0
type=1400 audit(1381784934.835:47): apparmor="DENIED" operation="mknod"
parent=1 profile="/usr/sbin/winbindd"
name="/var/lib/samba/winbindd_cache.tdb.bak.tmp" pid=4664 comm="winbindd"
requested_mask="c" denied_mask="c" fsuid=0 ouid=0
type=1400 audit(1381784934.835:48): apparmor="DENIED" operation="open" parent=1
profile="/usr/sbin/winbindd" name="/var/cache/samba/netsamlogon_cache.tdb"
pid=4664 comm="winbindd" requested_mask="rwc" denied_mask="rwc" fsuid=0 ouid=0
type=1400 audit(1381784934.835:49): apparmor="DENIED" operation="truncate"
parent=1 profile="/usr/sbin/winbindd"
name="/var/cache/samba/netsamlogon_cache.tdb" pid=4664 comm="winbindd"
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
type=1400 audit(1381784934.835:50): apparmor="DENIED" operation="open" parent=1
profile="/usr/sbin/winbindd" name="/var/cache/samba/netsamlogon_cache.tdb"
pid=4664 comm="winbindd" requested_mask="rwc" denied_mask="rwc" fsuid=0 ouid=0
type=1400 audit(1381784934.866:51): apparmor="DENIED" operation="mkdir"
parent=1 profile="/usr/sbin/winbindd" name="/var/run/samba/winbindd/" pid=4664
comm="winbindd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0

For smbd (specially tdbsam.so is fatal):

type=1400 audit(1381784615.634:37): apparmor="DENIED" operation="open"
parent=4321 profile="/usr/sbin/smbd"
name="/usr/share/samba/codepages/upcase.dat" pid=4322 comm="smbd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
type=1400 audit(1381784615.634:38): apparmor="DENIED" operation="open"
parent=4321 profile="/usr/sbin/smbd"
name="/usr/share/samba/codepages/lowcase.dat" pid=4322 comm="smbd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
type=1400 audit(1381784615.727:39): apparmor="DENIED" operation="file_mmap"
parent=1 profile="/usr/sbin/smbd" name="/usr/lib64/samba/pdb/tdbsam.so"
pid=4323 comm="smbd" requested_mask="m" denied_mask="m" fsuid=0 ouid=0

And nmbd

type=1400 audit(1381784935.224:52): apparmor="DENIED" operation="open"
parent=4764 profile="/usr/sbin/nmbd"
name="/usr/share/samba/codepages/upcase.dat" pid=4765 comm="nmbd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
type=1400 audit(1381785084.057:64): apparmor="DENIED" operation="open" parent=1
profile="/usr/sbin/nmbd" name="/var/cache/samba/gencache.tdb" pid=4766
comm="nmbd" requested_mask="rwc" denied_mask="rwc" fsuid=0 ouid=0
type=1400 audit(1381841171.493:34): apparmor="DENIED" operation="open"
parent=1351 profile="/usr/sbin/nmbd"
name="/usr/share/samba/codepages/lowcase.dat" pid=1352 comm="nmbd"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0

Reproducible: Always

Steps to Reproduce:
1.Disable apparmor
2.Configure samba
3.Enable apparmor
4.Restart samba
Actual Results:
5.Samba fails to run with multiple "access denied"

Expected Results:
5.Normal usage should be allowed in default apparmor

summary: Default samba apparmor profile denies its usage


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

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

           Summary: install onto nfsroot, chown fails
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Network
        AssignedTo: nfbrown-at-suse.com
        ReportedBy: ohering-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: Outsourced Testing
           Blocker: ---

while attempting to install 13.1rc1 onto an existing nfsshare (finding a case
for bnc#820407), rpm fails to change ownership.

host is bax.arch.suse.de, running sles11sp3:
/olaf_xenimages *(rw,async,no_root_squash,no_subtree_check,insecure)

guest is a hyperv VM with 13.1rc1 inst-sys:
bax.arch.suse.de:/olaf_xenimages/nfsroot/hv /mnt nfs4
rw,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.121.48.50,local_lock=none,addr=10.121.8.52
0 0

I did not actively select nfs4 in the yast dialog, perhaps thats the underlying
issue? Maybe something defaults to nfs4 now.

hammer50:~ # ls -la /mnt/
total 20
drwxr-xr-x  10 4294967294 4294967294 4096 Oct 16 11:25 .
drwxr-xr-x  24 root       root        840 Oct 16 11:19 ..
drwxr-xr-x   4 root       root       4096 Oct 16 11:23 boot
drwxr-xr-x  11 root       root       4640 Oct 16 11:23 dev
drwxr-xr-x   3 4294967294 4294967294 4096 Oct 16 11:24 etc
dr-xr-xr-x 228 root       root          0 Oct 16  2013 proc
drwxr-xr-x   7 root       root        180 Oct 16 11:20 run
dr-xr-xr-x  12 root       root          0 Oct 16  2013 sys
drwxr-xr-x   3 4294967294 4294967294 4096 Oct 16 11:23 usr
drwxr-xr-x   6 4294967294 4294967294 4096 Oct 16 11:23 var
-rw-r--r

summary: install onto nfsroot, chown fails


body:
Using virtualbox for this test of 13.1.
Noticed that bug 821375 is not solved in 13_1 just yet.

I'm doing tftp boot installation using NFS for autoyast profile reference. For
12.3 this config is working as expected and the install is success.

When doing the same for 13.1 (Build0041) I get no profile found. The progress
bar shows Retrieving control file (/data/LinuxInstall/autoYast/) from NFS
server: x.x.x.x. Within that location I have rules directory and rules.xml file
which is working fine for 12.3 installs.

Reproducible: Always

Steps to Reproduce:
select the right entry for 13_1 within tftp boot config menu. Process starts
and fails once it requires the profile from NFS location.
Actual Results:
Popup window with information about the System Profile Location.

Expected Results:
No popup window but just continuation of the overall autoYast install process
until a minimal running 13.1 system.

summary: autoyast can't find profile for install


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

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

           Summary: Displaylink device not available for xrandr 1.4
    Classification: openSUSE
           Product: openSUSE Factory
           Version: 13.1 Beta 1
          Platform: x86-64
        OS/Version: SUSE Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: oneukum-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

By default the udlfb driver binds to the device. That's wrong. udl should be
used, because udlfb doesn't implemt the modesetting ioctls. udlfb must be
blacklisted.


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

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

           Summary: apparmor="DENIED" operation="open" profile="/usr/lib/colord"
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: x86-64
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: AppArmor
        AssignedTo: suse-beta-at-cboltz.de
        ReportedBy: koenig-at-linux.de
         QAContact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

after update from 12.3 to 13.1-factory I noticed these kernel msg:

[  165.814132] type=1400 audit(1381957265.766:36): apparmor="DENIED"
operation="open" parent=1 profile="/usr/lib/colord" name="/sys/class/drm/"
pid=2791 comm="colord" requested_mask="r" denied_mask="r" fsuid=120 ouid=0
[  165.921781] type=1400 audit(1381957265.873:37): apparmor="DENIED"
operation="open" parent=1 profile="/usr/lib/colord"
name="/usr/local/share/mime/mime.cache" pid=2791 comm="colord"
requested_mask="r" denied_mask="r" fsuid=120 ouid=0
[  165.921820] type=1400 audit(1381957265.873:38): apparmor="DENIED"
operation="open" parent=1 profile="/usr/lib/colord"
name="/usr/local/share/mime/globs2" pid=2791 comm="colord" requested_mask="r"
denied_mask="r" fsuid=120 ouid=0
[  165.921850] type=1400 audit(1381957265.873:39): apparmor="DENIED"
operation="open" parent=1 profile="/usr/lib/colord"
name="/usr/local/share/mime/magic" pid=2791 comm="colord" requested_mask="r"
denied_mask="r" fsuid=120 ouid=0
[  165.921871] type=1400 audit(1381957265.873:40): apparmor="DENIED"
operation="open" parent=1 profile="/usr/lib/colord"
name="/usr/local/share/mime/aliases" pid=2791 comm="colord" requested_mask="r"
denied_mask="r" fsuid=120 ouid=0
[  165.921892] type=1400 audit(1381957265.873:41): apparmor="DENIED"
operation="open" parent=1 profile="/usr/lib/colord"
name="/usr/local/share/mime/subclasses" pid=2791 comm="colord"
requested_mask="r" denied_mask="r" fsuid=120 ouid=0
[  165.921914] type=1400 audit(1381957265.873:42): apparmor="DENIED"
operation="open" parent=1 profile="/usr/lib/colord"
name="/usr/local/share/mime/icons" pid=2791 comm="colord" requested_mask="r"
denied_mask="r" fsuid=120 ouid=0
[  165.921937] type=1400 audit(1381957265.873:43): apparmor="DENIED"
operation="open" parent=1 profile="/usr/lib/colord"
name="/usr/local/share/mime/generic-icons" pid=2791 comm="colord"
requested_mask="r" denied_mask="r" fsuid=120 ouid=0

$ rpm -qa colord apparmor\*
apparmor-utils-2.8.2-7.1.noarch
apparmor-profiles-2.8.2-7.1.noarch
apparmor-docs-2.8.2-7.1.noarch
apparmor-parser-2.8.2-7.1.x86_64
colord-1.1.2-1.3.x86_64


body:
If updates are available, pk-update-icon shows up in the system tray of the
Xfce desktop and also presents a small window with the number of available
updates and a button to install them. When clicking the button with OS 13.1
RC1, the small window disappears, but nothing else happens.

In 12.3 and before gpk-update-viewer was started after clicking the button. I
noticed that this program was missing and tried to install package
gnome-packagekit, but got a message that this package conflicts with package
apper, which made me unsure ho to proceed.

Reproducible: Always

I first installed openSUSE 13.1 RC1 from live KDE DVD because KDE is my 2.
choice of GUI. I then added Xfce as my 1. choice from the 13.1 repository by
selecting pattern "Xfce desktop environment" in YaST.

pkgs: apper gnome-packagekit pk-update-icon

summary: Update icon broken in Xfce desktop


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

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

           Summary: Tracker Bug Froxlor upstream release
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: x86-64
        OS/Version: SUSE Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
        AssignedTo: bnc-team-screening-at-forge.provo.novell.com
        ReportedBy: asemen-at-suse.com
         QAContact: qa-bugs-at-suse.de
          Found By: Development
           Blocker: ---

Tracker Bug Froxlor upstream release

to version 0.9.29

changelog:

Bug #1139: Froxlor package for armhf doesn't show up in aptitude
Bug #1258: unable to register 'memcache' SSL session cache: Memcache support
not enabled
Bug #1260: Cron Domain-SSL Zertifikat
Bug #1261: Fehler Apache mod_write
Feature #587: Provide php.ini Konfiguration for php-fpm

see announcement
http://forum.froxlor.org/index.php/topic/12264-release-0929/

see also road map
http://redmine.froxlor.org/projects/froxlor/roadmap?utf8=%E2%9C%93&tracker_ids[]=1&tracker_ids[]=2&tracker_ids[]=3&completed=1#0.9.29

summary: Tracker Bug Froxlor upstream release


body:
Hi,
after upgrading to 13.1 pppd does not reconnected after lcp-echo-failure
happened:

2013-10-16T19:31:27.924893+02:00 tenfore pppd[5405]: No response to 2
echo-requests
2013-10-16T19:31:28.121107+02:00 tenfore pppd[5405]: Serial link appears to be
disconnected.
2013-10-16T19:31:28.121745+02:00 tenfore pppd[5405]: Connect time 8532.1
minutes.
2013-10-16T19:31:28.144737+02:00 tenfore pppd[5405]: Sent 576240611 bytes,
received 4264384411 bytes.
2013-10-16T19:31:28.894514+02:00 tenfore pppd[5405]: Script /etc/ppp/ip-down
finished (pid 5193), status = 0x0
2013-10-16T19:31:32.227775+02:00 tenfore pppd[5405]: Connection terminated.
2013-10-16T19:31:32.245382+02:00 tenfore pppd[5405]: Sent PADT
2013-10-16T19:31:32.257248+02:00 tenfore pppd[5405]: Modem hangup
2013-10-16T19:31:32.266251+02:00 tenfore systemd[1]: Stopping ifup managed
network interface dsl0...

.. then it did not reconnect. My setup was working since openSUSE 11.4. On my
former installations it did not sent PADT.

maxfail 0
lcp-echo-interval 60
lcp-echo-failure 2
persist

I don't know how to reproduce. It works when I plug off/on any cables. I guess
I need to trick "No response to 2 echo-requests" somehow else.

Could be that these recently added patches have something todo with this
problem?:

Mon Sep  2 14:41:21 UTC 2013 - max-at-suse.com
- Add ppp-terminate-correct.patch, fix the pppd's hang after exit
  (bnc#693469).
-------------------------------------------------------------------
Wed Jul 24 12:54:01 UTC 2013 - max-at-suse.com
- ppp-send-padt.patch: Send PADT at the end of a PPPoE session.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

summary: pppd does not reconnect (option persist)


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

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

           Summary: systemctl --type=service list-unit-files doesn't show LSB wrapped ones
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: RC 1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: fcrozat-at-suse.com
        ReportedBy: mhrusecky-at-suse.com
         QAContact: qa-bugs-at-suse.de
                CC: locilka-at-suse.com, tchvatal-at-suse.com, vmoravec-at-suse.com
          Found By: ---
           Blocker: Yes

Michal Hrusecky <mhrusecky-at-suse.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|                            |SHIP_STOPPER+

'systemctl --type=service list-unit-files' doesn't show LSB services which are
showed only using 'systemctl --type=service list-units --all' which output on
the other hand doesn't show whether services are enabled or not.

Why major ship stopper: list-unit-files is used and parsed by YaST to provide
service manager. Currently it only shows native systemd services, which we are
still missing for some important services like xdm or MySQL. So fixing it to
show even LSB services is quite crucial for 13.1 release. Other option would be
to parse list-units command in YaST and call status on each of them, which
would be quite slow and ugly work around.