August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 941883] New: LIRC version is missing irman module and is really old
by bugzilla_noreply＠novell.com 06 Mar '17

06 Mar '17

http://bugzilla.opensuse.org/show_bug.cgi?id=941883 Bug ID: 941883 Summary: LIRC version is missing irman module and is really old Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: DaAwesomeP(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There are two major problems with the LIRC module. The first is that it is missing the irman module. In order to get the irman module LIRC must be compiled with libirman (available from here: https://sourceforge.net/projects/lirc/files/libirman/0.4.5/) However, libirman is not currently a package in OpenSUSE. I'm currently using the packages from http://download.opensuse.org/repositories/home:/wolfi323:/irman/openSUSE_13… and they work fine, but they have the other problem below. Forum discussion about that here: https://forums.opensuse.org/showthread.php/508988-LIRC-missing-irman-driver The other problem, the same as the one that I just submitted a bug for in OpenSUSE 13.2, is that LIRC is really old. It's at version 0.9.0, which is not supported anymore. The latest version is 0.9.3. I discovered this when I needed to receieve support via SourceForge about LIRC: https://sourceforge.net/p/lirc/tickets/120/ If this were fixed for Factory (both compiling with libirman and the version), would I be able to do a vendor switch and subscribe to it in 13.2 (what I currently use)? I can't see anything that would make it incompatible. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[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

[Bug 911575] New: poor IPv6-geolocation in mirrorbrain / download.o.o
by bugzilla_noreply＠novell.com 19 Feb '17

19 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=911575 Bug ID: 911575 Summary: poor IPv6-geolocation in mirrorbrain / download.o.o Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Download Infrastructure Assignee: lrupp(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: lrupp(a)suse.com CC: adrian(a)suse.com, hvogel(a)suse.com Found By: --- Blocker: --- When I run osc build on my workstation, the slowest part is the downloads of rpms with speeds varying between 5kB/s (very bad) and 500kB/s (slow but OKish). This might be due to mirrorbrain poorly handling our new IPv6 addrs curl http://download.opensuse.org/distribution/13.1/repo/non-oss/suse/noarch/joh… > List of best mirrors for IP address 2620:113:80c0:5::2222, located in an unknown country: > Found 99 mirrors in other parts of the world so it will probably randomly pick mirrors anywhere on the world and most of the download time is spent on slow mirrors -- You are receiving this mail because: You are on the CC list for the bug.

1 8