June 2015 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 900038] New: Application:Geo/postgis2: Bug
by bugzilla_noreply＠novell.com 18 Feb '17

18 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=900038 Bug ID: 900038 Summary: Application:Geo/postgis2: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: tzotsos(a)gmail.com Reporter: nikolai(a)prokoschenko.de QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: opensuse(a)dstoecker.de Found By: --- Blocker: --- It seems postgis 2.1 requires libgeos0 >= 3.4 at runtime. I would normally expect BuildRequires to suffice for that, but apparently it uses whatever libgeos0 is currently installed, i.e. it wouldn't upgrade 3.3 to 3.4. I'm not sure how to fix this correctly (Requires: libgeos0 >= 3.4 ?) therefore this bug report. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 924000] New: Please release K3B 2.0.3 as update for 13.2
by bugzilla_noreply＠novell.com 18 Feb '17

18 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=924000 Bug ID: 924000 Summary: Please release K3B 2.0.3 as update for 13.2 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: wbauer(a)tmo.at QA Contact: qa-bugs(a)suse.de CC: friedhelm.stappert(a)web.de, wbauer(a)tmo.at Depends on: 904524 Found By: --- Blocker: --- I would propose to release K3B 2.0.3 as bugfix update for 13.2. This has many bugs fixed, and would also fix the missing translations for K3B's solid actions and service menus. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 786679] New: usability issues with man
by bugzilla_noreply＠novell.com 16 Feb '17

16 Feb '17

https://bugzilla.novell.com/show_bug.cgi?id=786679 https://bugzilla.novell.com/show_bug.cgi?id=786679#c0 Summary: usability issues with man Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Documentation AssignedTo: ke(a)suse.com ReportedBy: aspiers(a)suse.com QAContact: ke(a)suse.com Found By: Development Blocker: --- This bug has two parts - a minor behavioural issue, and a minor documentation issue. As per FATE #303433, the default behaviour of man when there are multiple sections offering the requested man page was changed in June 2008. The old behaviour can be reverted by setting the MAN_POSIXLY_CORRECT environment variable. Whilst this was an improvement on the prior situation, there seems to be a minor behavioural issue when two versions of the same man page are on the manpath, e.g. $ manpath | tr : '\n' manpath: warning: $MANPATH set, ignoring /etc/manpath.config /home/adam/share/man /home/adam/.rvm/rubies/ruby-1.9.3-p194/share/man /home/adam/.rvm/man /opt/kde3/share/man /usr/local/man /usr/share/man /home/adam/.GIT/3rd-party/rvm/man $ ls -l ~/share/man/man1/git-commit.1 lrwxrwxrwx 1 adam users 46 Sep 26 13:19 /home/adam/share/man/man1/git-commit.1 -> ../../../.STOW/git/share/man/man1/git-commit.1 $ man -aw git-commit /usr/share/man/man1/git-commit.1.gz /home/adam/.STOW/git/share/man/man1/git-commit.1 $ man git-commit Man: find all matching manual pages (set MAN_POSIXLY_CORRECT to avoid this) * git-commit (1) git-commit (1+) Man: What manual page do you want? Man: However, if I enter '1+' and hit Enter, I still get the version from /usr/share. Likewise, $ man 1+ git-commit No manual entry for git-commit in section 1+ Perhaps I am wrong to expect this to work, which brings me onto the documentation issue: it is not clear how this is supposed to work, because while man-db-2.5.1-listall.dif patches src/man.c to introduce MAN_POSIXLY_CORRECT, it does not patch man/man1/man.man1 to correspondingly amend the documentation. So it would also be good if the changed behaviour and MAN_POSIXLY_CORRECT were documented. This would presumably help the patch get accepted upstream too. (Incidentally I notice that 2.5.1 is 4 years behind the current version 2.6.3, so it might be worth refreshing at some point soon.) -- 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 9

[Bug 936308] New: Black external monitor after resume from suspend
by bugzilla_noreply＠novell.com 16 Feb '17

16 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=936308 Bug ID: 936308 Summary: Black external monitor after resume from suspend Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: noga.dany(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- How to reproduce: 1) Dell Latitude E7450 with i7-5600U (HD Graphics 5500) 2) Notebook in dock station with external monitor connected 3) Everything ok 4) Suspend to ram 5) Resume from suspend 6) External screen connected via DVI is black Environment: 1) openSUSE 13.2 with 3.16.7 is ok 2) openSUSE 13.2 with 4.0.5 (from previous Kernel:stable repository) bugged 3) openSUSE 13.2 with 4.1.0 (from lattest Kernel:stable repository) bugged -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 905558] New: "zypper -ve" throws strange dependency errors for some applications (firefox, thunderbird...)
by bugzilla_noreply＠novell.com 15 Feb '17

15 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=905558 Bug ID: 905558 Summary: "zypper -ve" throws strange dependency errors for some applications (firefox, thunderbird...) Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: madworm_de.novell(a)spitzenpfeil.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build Identifier: The only way to get rid of this error is to completely remove the offending applications. Nothing else works. --- linux-m086:/home # zypper ve Loading repository data... Reading installed packages... Problem: nothing provides appdata(firefox.appdata.xml) needed by application:Firefox-.noarch Solution 1: deinstallation of application:Firefox-.noarch Solution 2: break application:Firefox-.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): --- Pressing (1) doesn't do anything. In this case it only goes away after removing all the MozillaFirefox rpms. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 929711] New: vsftpd virtual users not working
by bugzilla_noreply＠novell.com 14 Feb '17

14 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=929711 Bug ID: 929711 Summary: vsftpd virtual users not working Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bugzilla(a)singvogel.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0 Build Identifier: To enable virtual users in vsftpd the pam file is used: /etc/pam.d/vsftpd This file requires /lib64/security/pam_userdb.so to access the vsftpd_login.db Pam doesn't have an pam_userdb.so included anymore (removed Jan 2014). vsftpd isn't capable of virtual users anymore. Reproducible: Always Steps to Reproduce: Enable virtual user in vsftpd as described in /usr/share/doc/packages/vsftpd/EXAMPLE/VIRTUAL_USERS/README ...and access the ftp daemon Actual Results: See error message in /var/log/messages: May 5 14:08:08 ftpserver vsftpd: PAM unable to dlopen(/lib64/security/pam_userdb.so): /lib64/security/pam_userdb.so: cannot open shared object file: No such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 913517] New: Wrong $TERM after paravirtualized installation
by bugzilla_noreply＠novell.com 08 Feb '17

08 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=913517 Bug ID: 913517 Summary: Wrong $TERM after paravirtualized installation Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fabian(a)ritter-vogt.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Installed openSUSE 13.2 from DVD using the SLES 12 template XenServer provides. Installs and boots fine, but $TERM is set to vt102 after logon so the console is black and white only. Putting "export TERM=linux" into /etc/profile.local fixes this. This issue is not present on 13.1. I guess this doesn't only affect XenServer but rather all PV installs. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 927712] New: Slow shutdown with encrypted LVM
by bugzilla_noreply＠novell.com 08 Feb '17

08 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=927712 Bug ID: 927712 Summary: Slow shutdown with encrypted LVM Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Windows 7 Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: opensuse.forum(a)mailinator.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Steps to reproduce: 1) Perform plain vanilla installation of OpenSUSE 13.2 in a VirtualBox VM - only change during installation: enable LVM and encryption. 2) Shutdown VM. Actual Results: Shutdown takes significantly longer in comparision to a setup without full disk encryption And this does not seem to be related to the encryption overhead. When shutting down the following messages appear before the virtual machine is closed: 1.systemd-shutdown[1]: Cannot finalize remaining file systems and devices, giving up. 2.systemd-shutdown[1]: Failed to mkdir /run/initramfs/oldroot: Read-only file system Expected Results: As this seems not to be a real problem, shutdown should not wait, but give up immediately if encryption is used. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 911334] New: dracut prints errors when run after uninstalling fglrx binary blob
by bugzilla_noreply＠novell.com 07 Feb '17

07 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=911334 Bug ID: 911334 Summary: dracut prints errors when run after uninstalling fglrx binary blob 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: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After uninstalling fglrx everytime i run mkinitrd I get errors about fglrx.ko not being found. I sadly have no idea where the decision to configure this in came from. In etc the only fglrx is here: root@arcarius: /etc # grep -r fglrx . ./apparmor.d/abstractions/X: /usr/lib/fglrx/dri/** mr, ./zypp/repos.d/AMD_blob.repo:baseurl=http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_13.2/ The output of mkinitrd: Creating initrd: /boot/initrd-3.16.6-2-desktop Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-3.16.6-2-desktop 3.16.6-2-desktop dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found! dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found! dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found! dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found! dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found! dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found! *** Including module: bash *** *** Including module: warpclock *** *** Including module: i18n *** *** Including module: ifcfg *** *** Including module: drm *** /usr/lib/dracut/modules.d/50drm/module-setup.sh: line 29: /lib/modules/3.16.6-2-desktop//extra/fglrx.ko: No such file or directory *** Including module: plymouth *** *** Including module: btrfs *** *** Including module: kernel-modules *** Omitting driver i2o_scsi /usr/lib/dracut/modules.d/90kernel-modules/module-setup.sh: line 15: /lib/modules/3.16.6-2-desktop//extra/fglrx.ko: No such file or directory *** Including module: resume *** *** Including module: rootfs-block *** *** Including module: terminfo *** *** Including module: udev-rules *** Skipping udev rule: 91-permissions.rules Skipping udev rule: 80-drivers-modprobe.rules *** Including module: systemd *** *** Including module: usrmount *** *** Including module: base *** *** Including module: fs-lib *** *** Including module: shutdown *** *** Including module: suse *** *** Including modules done *** *** Installing kernel module dependencies and firmware *** *** Installing kernel module dependencies and firmware done *** *** Resolving executable dependencies *** *** Resolving executable dependencies done*** *** Hardlinking files *** *** Hardlinking files done *** *** Stripping files *** *** Stripping files done *** *** Generating early-microcode cpio image *** *** Store current command line parameters *** Stored kernel commandline: resume=UUID=b2b04505-5b4b-48da-be23-77198a258995 root=UUID=df95b0f0-ab22-4c08-b445-c40128121109 rootflags=rw,relatime,ssd,space_cache rootfstype=btrfs *** Creating image file *** *** Creating image file done *** -- You are receiving this mail because: You are on the CC list for the bug.

1 4