November 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1065563] AUDIT-0: Review of package kcm-sddm (polkit-untracked-privilege , suse-dbus-unauthorized-service)
by bugzilla_noreply＠novell.com 02 Nov '17

02 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1065563 http://bugzilla.suse.com/show_bug.cgi?id=1065563#c4 --- Comment #4 from Luca Beltrame <lbeltrame(a)kde.org> --- rpmlint errors (badness is changed in the devel project to allow building and testing): kcm_sddm.x86_64: I: polkit-cant-acquire-privilege org.kde.kcontrol.kcmsddm.installtheme (??:no:auth_admin_keep) kcm_sddm.x86_64: I: polkit-cant-acquire-privilege org.kde.kcontrol.kcmsddm.uninstalltheme (??:no:auth_admin_keep) Usability can be improved by allowing users to acquire privileges via authentication. Use e.g. 'auth_admin' instead of 'no' and make sure to define 'allow_any'. This is an issue only if the privilege is not listed in /etc/polkit-default-privs.* kcm_sddm.x86_64: I: polkit-untracked-privilege org.kde.kcontrol.kcmsddm.installtheme (??:no:auth_admin_keep) kcm_sddm.x86_64: I: polkit-untracked-privilege org.kde.kcontrol.kcmsddm.uninstalltheme (??:no:auth_admin_keep) The privilege is not listed in /etc/polkit-default-privs.* which makes it harder for admins to find. If the package is intended for inclusion in any SUSE product please open a bug report to request review of the package by the security team kcm_sddm.x86_64: W: suse-dbus-unauthorized-service /etc/dbus-1/system.d/org.kde.kcontrol.kcmsddm.conf kcm_sddm.x86_64: W: suse-dbus-unauthorized-service /usr/share/dbus-1/system-services/org.kde.kcontrol.kcmsddm.service The package installs a DBUS system service file. If the package is intended for inclusion in any SUSE product please open a bug report to request review of the service by the security team. The relevant files (polkit, dbus) will be attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1065563] AUDIT-0: Review of package kcm-sddm (polkit-untracked-privilege , suse-dbus-unauthorized-service)
by bugzilla_noreply＠novell.com 02 Nov '17

02 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1065563 http://bugzilla.suse.com/show_bug.cgi?id=1065563#c3 --- Comment #3 from Luca Beltrame <lbeltrame(a)kde.org> --- Created attachment 746745 --> http://bugzilla.suse.com/attachment.cgi?id=746745&action=edit Polkit policy -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1060627] New: The desktop session entries in gdm are duplicate
by bugzilla_noreply＠novell.com 02 Nov '17

02 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1060627 Bug ID: 1060627 Summary: The desktop session entries in gdm are duplicate Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: qkzhu(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ast(a)suse.com, behlert(a)suse.com, dimstar(a)opensuse.org, fcrozat(a)suse.com, gwang(a)suse.com, mawerner(a)suse.com, sreeves(a)suse.com, yfjiang(a)suse.com, zaitor(a)opensuse.org Found By: --- Blocker: --- Created attachment 742201 --> http://bugzilla.suse.com/attachment.cgi?id=742201&action=edit (TW) There are two Icewm entries in gdm Click the gear icon in gdm login screen, you can find the session entries are duplicate. - If icewm is installed there will be two icewm items and one of the 'icewm' will lead you into 'GNOME' session (see the screenshot) - If icewm is not installed there will be two 'GNOME' entries This bug might be related with bsc#1039756, gdm now is patched to recognize default.desktop (usually in /usr/share/xsessions) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1065587] [FAILED] Failed unmounting /xhome
by bugzilla_noreply＠novell.com 02 Nov '17

02 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1065587 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |systemd-maintainers(a)suse.de |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1025863] New: clang++ assumes gccN-c++ is available
by bugzilla_noreply＠novell.com 02 Nov '17

02 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1025863 Bug ID: 1025863 Summary: clang++ assumes gccN-c++ is available Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: rguenther(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I get > g++ -S t.C > clang++ -S t.C t.C:1:10: fatal error: 'iostream' file not found #include <iostream> ^ 1 error generated. which is because clang seems to search for installed compilers: stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/4.8", {st_mode=S_IFDIR|0755, st_si ze=1234, ...}) = 0 stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/4.8/64/crtbegin.o", 0x7ffe7d06f550 ) = -1 ENOENT (No such file or directory) stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/4.8/crtbegin.o", {st_mode=S_IFREG| 0644, st_size=2712, ...}) = 0 ... stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/6", {st_mode=S_IFDIR|0755, st_size =1356, ...}) = 0 stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/6/64/crtbegin.o", 0x7ffe7d06f550) = -1 ENOENT (No such file or directory) stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/6/crtbegin.o", {st_mode=S_IFREG|0644, st_size=2736, ...}) = 0 ... stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/5", {st_mode=S_IFDIR|0755, st_size=1364, ...}) = 0 stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/7", {st_mode=S_IFDIR|0755, st_size=1296, ...}) = 0 stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/7/64/crtbegin.o", 0x7ffe7d06f550) = -1 ENOENT (No such file or directory) stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/7/crtbegin.o", {st_mode=S_IFREG|0644, st_size=2488, ...}) = 0 and then, without further checking, assumes the "newest" also provides libstdc++ headers: stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/7/../../../../include/c++/7", 0x7f fe7d06ea10) = -1 ENOENT (No such file or directory) stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/7/include/g++-v7.", 0x7ffe7d06ea10 ) = -1 ENOENT (No such file or directory) stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/7/include/g++-v7", 0x7ffe7d06ea10) = -1 ENOENT (No such file or directory) stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/in clude/c++/7", 0x7ffe7d06ea10) = -1 ENOENT (No such file or directory) stat("/usr/bin/../lib64/gcc/x86_64-suse-linux/7/../../../../include/c++", {st_mode=S_IFDIR|0755, st_size=14, ...}) = 0 to bad, while I have gcc7 installed I did not install gcc7-c++. I find the behavior confusing (the error reporting even more so) and would have expected the SUSE clang++ uses the system compilers standard library. Note that llvm-clang doesn't even require any installed libstdc++ headers so w/o installing gcc-c++ the error message would be similarly cryptic. Just checked Leap 42.2 where I ran into it, might be fixed in Tumbleweed (but I guess not as the above looks like upstream behavior) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1065965] New: Missing RPM requirement: Desktop applications don't depend on fonts
by bugzilla_noreply＠novell.com 02 Nov '17

02 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1065965 Bug ID: 1065965 Summary: Missing RPM requirement: Desktop applications don't depend on fonts Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: swagner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- when installing Qt 4 software inside of a docker image, like so: > FROM opensuse:42.3 > RUN zypper up -y > RUN zypper in -y <some software using Qt4> > ENV DISPLAY :0 > ENV QT_GRAPHICSSYSTEM native > CMD fate And you run it like so: > docker build -t missing-font . > XSOCK=/tmp/.X11-unix > XAUTH=/tmp/.docker.xauth > xauth nlist $DISPLAY | sed -e 's/^..../ffff/' | xauth -f $XAUTH nmerge - > docker run -ti -v $XSOCK:$XSOCK -v $XAUTH:$XAUTH -e XAUTHORITY=$XAUTH missing-font Then, only the □ characters are rendered. Installing a font package like > lato-fonts Fixes this problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1065539] Login screen shows 4 options named "Plasma", first one logs into Gnome desktop
by bugzilla_noreply＠novell.com 02 Nov '17

02 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1065539 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |opensuse-kde-bugs@opensuse. |ovo.novell.com |org -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1064999] [Build 20171023] Installation fails with segmentation fault in ZYppFactory.cc
by bugzilla_noreply＠novell.com 02 Nov '17

02 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1064999 http://bugzilla.suse.com/show_bug.cgi?id=1064999#c5 Ladislav Slezák <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |libzypp Assignee|yast2-maintainers(a)suse.de |zypp-maintainers(a)forge.prov | |o.novell.com QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de Flags|needinfo?(lslezak(a)suse.com) | --- Comment #5 from Ladislav Slezák <lslezak(a)suse.com> --- The backtrace from the log is: ZYppFactory.cc(sigsegvHandler):55 [bt]: (0) /lib/libc.so.6 : memcpy+0x6c [0xb7b9f13c] ZYppFactory.cc(sigsegvHandler):55 [bt]: (1) /usr/lib/libzypp.so.1600 : +0x41c523 [0xb5176523] ZYppFactory.cc(sigsegvHandler):55 [bt]: (2) /usr/lib/libzypp.so.1600 : +0x41b29f [0xb517529f] ZYppFactory.cc(sigsegvHandler):55 [bt]: (3) /usr/lib/libzypp.so.1600 : zypp::IdString::IdString(char const*, unsigned int)+0x25 [0xb502cd45] ZYppFactory.cc(sigsegvHandler):55 [bt]: (4) /usr/lib/libzypp.so.1600 : zypp::IdString::IdString(boost::basic_string_ref<char, std::char_traits<cha ZYppFactory.cc(sigsegvHandler):55 [bt]: (5) /usr/lib/libzypp.so.1600 : zypp::Locale::name[abi:cxx11]() const+0x5e7 [0xb5147607] ZYppFactory.cc(sigsegvHandler):55 [bt]: (6) /usr/lib/YaST2/plugin/libpy2Pkg.so.2 : PkgFunctions::ResolvablePropertiesEx(YCPString const&, YCPSymbo 3ee00b] ZYppFactory.cc(sigsegvHandler):55 [bt]: (7) /usr/lib/YaST2/plugin/libpy2Pkg.so.2 : PkgFunctions::ResolvableProperties(YCPString const&, YCPSymbol const&, YCPString const&)+0x38 [0xb53eee78] To me to problem seems to be somewhere inside the Locale::name() libzypp function. JFYI: YaST just calls this: https://github.com/yast/yast-pkg-bindings/blob/f67bce3767e7dea54ef4122634c3… Changing to the libzypp component. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1025863] clang++ assumes gccN-c++ is available
by bugzilla_noreply＠novell.com 02 Nov '17

02 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1025863 http://bugzilla.suse.com/show_bug.cgi?id=1025863#c4 --- Comment #4 from Richard Biener <rguenther(a)suse.com> --- It would be nice to have clang not add many random search paths but only a single pre-configured one so we can have that match a proper Requires: for libstdc++-devel. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1065841] stddef.h: The symbol `__float128' does not fit here.
by bugzilla_noreply＠novell.com 02 Nov '17

02 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1065841 http://bugzilla.suse.com/show_bug.cgi?id=1065841#c1 Richard Biener <rguenther(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter.trommler@ohm-hochschu | |le.de, rguenther(a)suse.com Assignee|rguenther(a)suse.com |mimi.vx(a)gmail.com --- Comment #1 from Richard Biener <rguenther(a)suse.com> --- This is a bug in ghc which appearantly tries to "parse" C headers and doesn't understand the new basic type __float128. I've seen this elsewhere. -- You are receiving this mail because: You are on the CC list for the bug.

1 0