http://bugzilla.opensuse.org/show_bug.cgi?id=909307
Bug ID: 909307
Summary: wicked.service can't configure user-class id
Classification: openSUSE
Product: openSUSE Distribution
Version: 13.2
Hardware: x86-64
OS: openSUSE 13.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Network
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: asaf.magen(a)sap.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
wicked does not handle DHCLIENT_USER_CLASS ifcfg setting properly.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=915714
Bug ID: 915714
Summary: Request security review for smb4k (Project: KDE:Extra)
Classification: openSUSE
Product: openSUSE Factory
Version: 201501*
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Security
Assignee: security-team(a)suse.de
Reporter: tittiatcoke(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
The latest versions of smb4k are installing a helper which causes the error:
E: suse-dbus-unauthorized-service (Badness: 10000)
/usr/share/dbus-1/system-services/net.sourceforge.smb4k.mounthelper.service
E: suse-dbus-unauthorized-service (Badness: 10000)
/etc/dbus-1/system.d/net.sourceforge.smb4k.mounthelper.conf
and
E: polkit-unauthorized-privilege (Badness: 10000)
net.sourceforge.smb4k.mounthelper.mount (??:no:yes)
E: polkit-unauthorized-privilege (Badness: 10000)
net.sourceforge.smb4k.mounthelper.unmount (??:no:yes)
These helpers are installed in order for users to mount and unmount SMB shares
in their own home-directory.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=915160
--- Comment #6 from Markus Zimmermann <markus.zimmermann(a)nethead.at> ---
I noticed that the services wickedd-dhcp4.service and wickedd-dhcp6.service are
not running. Should I enable them?
And I remembered that I could not connect some years ago with older KDE
versions. But this was the fault of the KDE's NM UI. Maybe the old problem is
back? https://bugs.kde.org/show_bug.cgi?id=209673
Also I rememberd a problem with the WIFI N mode
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/575492 I will try that
too. But I tought that these problems were all resolved with newer KDE/NM/Linux
versions. What do you think?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=915160
Peter Varkoly <varkoly(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|varkoly(a)suse.com |bnc-team-screening(a)forge.pr
| |ovo.novell.com
--- Comment #5 from Peter Varkoly <varkoly(a)suse.com> ---
Thi is a issue of dhcpclient not dhcpcd!
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=915711
Bug ID: 915711
Summary: package plasmoid-akonadi-contacts conlicts with
official skype rpm package
Classification: openSUSE
Product: openSUSE Distribution
Version: 13.2
Hardware: Other
OS: openSUSE 13.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE4 Applications
Assignee: kde-maintainers(a)suse.de
Reporter: devel.suse(a)gmail.com
QA Contact: qa-bugs(a)suse.de
CC: devel.suse(a)gmail.com
Found By: ---
Blocker: ---
There is the conflict between plasmoid-akonadi-contacts package from KDE:Extra
repository and the skype-4.3.0.37-suse121.i586 from the official website.
The conflicted file is:
- /usr/share/icons/hicolor/32x32/apps/skype.png
Due to this automated installs with zypper from scripts are failed.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=899112
Serg Opensuse user <devel.suse(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |devel.suse(a)gmail.com
--- Comment #4 from Serg Opensuse user <devel.suse(a)gmail.com> ---
It was reported to the upstream already. See the next entries:
https://bugs.kde.org/show_bug.cgi?id=343468https://bugs.freedesktop.org/show_bug.cgi?id=88004
There is also workaround mentioned.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=848775
--- Comment #12 from John Bowling <johnlb2002(a)cox.net> ---
I installed 13.2 from the rolling portion of factory this morning.
It did not exhibit any delays as before, and the boot loader now shows me 13.1
and the current one.
Prior to install. I made sure 13.1 that 13.1 and it's boot location were on a
500G as /dev/sda, and that this 13.2+today is on the 3T drive as /dev/sdb..
When it rebooted, lt exhibited a problem where it went to 13.1 and it could not
find some files. I discovered that the BIOS had changed the drive order
It booted properly into 13.2 after that was corrected, but 13.1 does not boot,
still missing something I have not yet had time to look for.
The shifting drive location may have given me problems before, or the /boot(s)
being not being on the same drive may be causing the BIOS situation.
I'm using an ASUS M2A-VM motherboard.
As far as the speed of os-prober, any test I make now is enough different with
drive count that my result is not equivelent as to what it was before. The
probing at the beginning was over in a few seconds.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=905863
Bug ID: 905863
Summary: lsinitrd - cat: write error: Broken pipe
Classification: openSUSE
Product: openSUSE Distribution
Version: 13.2
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: per(a)computer.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
I noticed this error message when I did an "lsinitrd" on the initrd generated
by a fresh 13.2 installation. The initrd can be found here:
http://files.jessen.ch/office13-initrd-3.16.6-2-desktop (too big to attach
directly)
--
You are receiving this mail because:
You are on the CC list for the bug.