June 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 755603] New: The gnome keyring socket is not owned with the same credentials as the user login
by bugzilla_noreply＠novell.com 11 Mar '17

11 Mar '17

https://bugzilla.novell.com/show_bug.cgi?id=755603 https://bugzilla.novell.com/show_bug.cgi?id=755603#c0 Summary: The gnome keyring socket is not owned with the same credentials as the user login Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: mvyskocil(a)suse.com QAContact: qa-bugs(a)suse.de CC: vuntz(a)suse.com, vcizek(a)suse.com Found By: Development Blocker: --- Created an attachment (id=484752) --> (http://bugzilla.novell.com/attachment.cgi?id=484752) copy the credential checking code from git.gnome.org Running command via sudo fills my log errors as appears in $SUBJECT $ sudo ls Password: xxxx and then log contains following Apr 4 10:20:01 zelva sudo: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/mvyskocil/keyring-5MIqXs/control Apr 4 10:20:01 zelva sudo: gkr-pam: couldn't unlock the login keyring. Apr 4 10:20:01 zelva sudo: mvyskocil : TTY=pts/5 ; PWD=/home/mvyskocil ; USER=root ; COMMAND=/usr/bin/ls Apr 4 10:20:01 zelva systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus However that's not true $ echo $GNOME_KEYRING_CONTROL /run/user/mvyskocil/keyring-5MIqXs $ ls -n $GNOME_KEYRING_CONTROL/* srwxr-xr-x 1 10112 100 0 4. dub 09.33 /run/user/mvyskocil/keyring-5MIqXs/control srwxr-xr-x 1 10112 100 0 4. dub 09.33 /run/user/mvyskocil/keyring-5MIqXs/gpg srwxr-xr-x 1 10112 100 0 4. dub 09.33 /run/user/mvyskocil/keyring-5MIqXs/pkcs11 srwxr-xr-x 1 10112 100 0 4. dub 09.33 /run/user/mvyskocil/keyring-5MIqXs/ssh $ id uid=10112(mvyskocil) gid=100(users) groups=100(users),10(wheel),33(video),41(xok),113(vboxusers),404(lighttpd),1194(vpn) $ id -u 10112 $ id -ru 10112 so the 10112 is my *real* id and keyring sockets are really owned by this id. $ cat /proc/$GNOME_KEYRING_PID/loginuid 10112 and even the process runs with the same uid, so there is really **no** surprise in my configuration. I did a bit more and copy the part of gnome-keyring-daemon, however even getsockopt returns the id 10112, like getuid does. $ ./creds uid=10112, geteuid()=10112 I would say the best way to debug would be patch gnome-keyring-daemon and print the values of uid and getuid on error, but I haven't a time to do that yet. BTW: as google returns most of suse related things for $SUBJ, I suspect some misconfiguration in our pam stack. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 923764] New: server:monitoring/smokeping: invalid user: 'smokeping:root
by bugzilla_noreply＠novell.com 06 Mar '17

06 Mar '17

http://bugzilla.opensuse.org/show_bug.cgi?id=923764 Bug ID: 923764 Summary: server:monitoring/smokeping: invalid user: 'smokeping:root Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: nix(a)opensuse.org Reporter: martin(a)oneiros.de QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- After an install of smokeping > rpm -qi smokeping Name : smokeping Version : 2.6.9 Release : 5.1 Architecture: noarch Install Date: Mo 23 Mär 2015 14:57:44 CET Group : System/Monitoring Size : 1295402 License : GPL v2 Signature : DSA/SHA1, Di 29 Jul 2014 11:37:14 CEST, Key ID a5c23697ee454f98 Source RPM : smokeping-2.6.9-5.1.src.rpm Build Date : Di 29 Jul 2014 11:36:58 CEST Build Host : build93 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/server:monitoring URL : http://oss.oetiker.ch/smokeping/ Summary : Advanced network latency monitor Description : SmokePing is a network latency monitor which works in a way that is similar to MRTG. It measures network latency to a configurable set of destinations on the network, and displays its findings in easy-to-read Web pages. SmokePing has special support for monitoring hosts with dynamic IP addresses. SmokePing uses RRDtool as its logging and graphing back-end, making the system very efficient. The presentation of the data on the Web is done through a CGI which creates graphs on demand. Distribution: server:monitoring / openSUSE_13.1 The service can not be started as installed: > sudo systemctl start smokeping Job for smokeping.service failed. See 'systemctl status smokeping.service' and 'journalctl -xn' for details. > sudo systemctl status smokeping smokeping.service - LSB: Smokeping Latency Monitor Loaded: loaded (/etc/init.d/smokeping) Active: failed (Result: exit-code) since Mo 2015-03-23 15:03:28 CET; 5s ago Process: 5638 ExecStart=/etc/init.d/smokeping start (code=exited, status=2) Mär 23 15:03:28 lucien systemd[1]: Starting LSB: Smokeping Latency Monitor... Mär 23 15:03:28 lucien smokeping[5638]: chown: invalid user: 'smokeping:root' Mär 23 15:03:28 lucien systemd[1]: smokeping.service: control process exited, code=exited status=2 Mär 23 15:03:28 lucien systemd[1]: Failed to start LSB: Smokeping Latency Monitor. Mär 23 15:03:28 lucien systemd[1]: Unit smokeping.service entered failed state. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 903974] New: Libraries missing symbol information
by bugzilla_noreply＠novell.com 02 Mar '17

02 Mar '17

http://bugzilla.opensuse.org/show_bug.cgi?id=903974 Bug ID: 903974 Summary: Libraries missing symbol information Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- A bug for tracking symbol versioning progress in NetworkManager. Halfway during upgrade, encountered: NetworkManager[29114]: <info> NetworkManager (version 0.9.10.0) is starting... NetworkManager[29114]: <info> Read config: /etc/NetworkManager/NetworkManager.conf NetworkManager[29114]: <info> WEXT support is enabled NetworkManager[29114]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn NetworkManager[29114]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager[29114]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager[29114]: /usr/sbin/NetworkManager: symbol lookup error: /usr/sbin/NetworkManager: undefined symbol: nm_utils_hwaddr_aton_len systemd[1]: Failed to start Network Manager. systemd[1]: Unit NetworkManager.service entered failed state. 11:10 localhorse:/home/jengelh # rpm -qa --qf="%{DISTRIBUTION}\t%{NAME}-%{VERSION}-%{RELEASE}\n" | grep -Pi 'libnm|networkm' openSUSE 13.2 NetworkManager-gnome-0.9.10.0-2.2.1 openSUSE 13.1 libnm-gtk0-0.9.8.4-20.3 openSUSE 13.2 NetworkManager-0.9.10.0-3.1.4 openSUSE 13.1 libnm-glib-vpn1-0.9.8.8-10.1 openSUSE 13.1 libnm-util2-0.9.8.8-10.1 openSUSE 13.2 NetworkManager-openvpn-0.9.10.0-2.1.4 openSUSE 13.1 libnm-glib4-0.9.8.8-10.1 openSUSE 13.2 NetworkManager-openvpn-gnome-0.9.10.0-2.1.4 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 901944] New: Xfce 4.10 Weather Applet says "NO DATA"
by bugzilla_noreply＠novell.com 01 Mar '17

01 Mar '17

http://bugzilla.opensuse.org/show_bug.cgi?id=901944 Bug ID: 901944 Summary: Xfce 4.10 Weather Applet says "NO DATA" Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: 64bit OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: linux(a)interworld.net.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I use the Xfce Desktop on OpenSuse 13.1. The Xfce Weather Applet says since a few days "No Data" and has stopped to show weather information. I understand this Applet has to be updated. No update is available for OpenSuse. Please publish and update. There are updates available from http://pkgs.org/download/xfce4-weather-plugin for: Arch Linux CentOS 7 CentOS 5 Debian Sid Debian Jessie Debian Wheezy Fedora Rawhide Fedora 21 Fedora 20 Fedora 19 Mageia Cauldron Mageia 4.1 Mageia 3 OpenMandriva Cooker OpenMandriva Lx 2014.0 OpenMandriva Lx 2013.0 ROSA Desktop Fresh R3 ROSA Enterprise Desktop X1 Slackware 14.1 Slackware 14.0 Slackware 13.37 Ubuntu 14.10 Ubuntu 14.04 LTS Ubuntu 12.04 LTS There is no update for OpenSuse! -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 921494] New: [ocfs2] run run_mmaptruncate() case on opensuse13.2 with ocfs2-tools-1.8.2 will hang in 10G volume
by bugzilla_noreply＠novell.com 01 Mar '17

01 Mar '17

http://bugzilla.suse.com/show_bug.cgi?id=921494 Bug ID: 921494 Summary: [ocfs2] run run_mmaptruncate() case on opensuse13.2 with ocfs2-tools-1.8.2 will hang in 10G volume Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: lmb(a)suse.com Reporter: ghe(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a very weird problem, running run_mmaptruncate() case on opensuse13.2 with ocfs2-tools-1.8.2 will hang in 10G volume, but running this case in a more bigger volume (e.g. 60G) will be OK. So, I want to see if this behavior art is considered as a bug. the accurate step which is hanged is in case of block-size=4096/cluster-size=1048576 (last step). -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 913360] New: Yast2-bootloader hangs on the kernel parameters tab
by bugzilla_noreply＠novell.com 24 Feb '17

24 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=913360 Bug ID: 913360 Summary: Yast2-bootloader hangs on the kernel parameters tab Classification: openSUSE Product: openSUSE Factory Version: 201501* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: tchvatal(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When I try click on it for couple of minutes it was just thinking, when Ctrl+C stopped it, I got notification it was stuck on this line: YaST got signal 2 at file /usr/share/YaST2/modules/Initrd.rb:424 Which translates to: SCR.Read(path(".probe.framebuffer")), No idea to what is wrong, but maybe it should try to probe for a moment and then give up... -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 936535] New: LighDM doesn't change mouse pointer
by bugzilla_noreply＠novell.com 23 Feb '17

23 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=936535 Bug ID: 936535 Summary: LighDM doesn't change mouse pointer Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sysek(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi. After the instalation LightDM, and add as a display-manager.service, the LightDM doesn't seems to change, the mouse pointer. Even if I choose from mate-apperance-properties for example DMZ, the mouse pointer is still the same. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 914814] New: zypper does not remove old kernels
by bugzilla_noreply＠novell.com 23 Feb '17

23 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=914814 Bug ID: 914814 Summary: zypper does not remove old kernels Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: illumilore(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 Build Identifier: On opensuse 13.2, I have followed the instructions at https://en.opensuse.org/SDB:Keep_multiple_kernel_versions to make sure multiversion = provides:multiversion(kernel) and multiversion.kernels = latest,latest-1,latest-2,running are present and uncommented in zypp.conf, however, there are still about a dozen kernel versions that show up on the boot screen and have not been autoremoved. Reproducible: Always Steps to Reproduce: 1. run zypper dup to update system, it then installs new updated kernel 2. 3. Actual Results: old kernels are never removed by zypper Expected Results: only 3 or so of the most recent kernels should be kept. I have http://download.opensuse.org/repositories/Kernel:/HEAD/standard/ in zypper repos enabled. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 926844] New: zypp leaves directories in /var/tmp/zypp.XXXXXX
by bugzilla_noreply＠novell.com 22 Feb '17

22 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=926844 Bug ID: 926844 Summary: zypp leaves directories in /var/tmp/zypp.XXXXXX Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: lmuelle(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: No gab:/var/tmp # ls -ld zypp.?????? | wc -l 6 Such a directory has for example the following content: zypp.bzvN4s zypp.bzvN4s/zypp-general-krpkAJfS zypp.bzvN4s/zypp-trusted-kry1ngFF zypp.bzvN4s/zypp-trusted-kry1ngFF/pubring.gpg zypp.bzvN4s/zypp-trusted-kry1ngFF/trustdb.gpg zypp.bzvN4s/zypp-trusted-kry1ngFF/pubring.gpg~ zypp.bzvN4s/zypp-trusted-kry1ngFF/secring.gpg -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 904015] New: font aliasing broken under KDE
by bugzilla_noreply＠novell.com 21 Feb '17

21 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=904015 Bug ID: 904015 Summary: font aliasing broken under KDE Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace Assignee: kde-maintainers(a)suse.de Reporter: vkrevs(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 612480 --> http://bugzilla.opensuse.org/attachment.cgi?id=612480&action=edit opensuse_13.1_kde_font_settings1.png For a very long time (since openSUSE 11.x), my KDE font settings had been set up to use Tahoma 8 as the main font, with enabled anti-aliasing and excluding range 0.0-8.0. This resulted in beautiful fonts in all KDE and GTK apps (see attached opensuse_13.1_kde_font_settings1.png file). Today I had upgraded to openSUSE 13.2 from 13.1. As a result, rendering of Tahoma 8 has changed in all applications but Google Chrome (see attached opensuse_13.2_kde_font_settings1.png file) and is very ugly compared to how it was in 13.1. Looks like BCI is not used for font sizes in the excluded range. I have tried rebuilding the freetype2 package with enable_subpixel_rendering set to 1 to no avail, also tried changing BYTECODE_BW_MAX_PIXEL from 0 to 8 in /etc/sysconfig/fonts-config to no avail as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 23