July 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 889065] New: vim or vim-data should install /vim74/ftdetect directory
by bugzilla_noreply＠novell.com 25 Jul '14

25 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=889065 https://bugzilla.novell.com/show_bug.cgi?id=889065#c0 Summary: vim or vim-data should install /vim74/ftdetect directory Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: idonmez(a)suse.com ReportedBy: tampakrap(a)opensuse.org QAContact: qa-bugs(a)suse.de CC: mrueckert(a)suse.com Found By: --- Blocker: --- As per summary, vim or vim-data (probably vim-data) should install the ftdetect directory under /usr/share/vim/vim74 -- 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 0

[Bug 888555] New: yast2-services-manager: error messages not cleared up
by bugzilla_noreply＠novell.com 25 Jul '14

25 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=888555 https://bugzilla.novell.com/show_bug.cgi?id=888555#c0 Summary: yast2-services-manager: error messages not cleared up Classification: openSUSE Product: openSUSE Factory Version: 201407* Platform: All OS/Version: Other Status: ASSIGNED Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: ancor(a)suse.com ReportedBy: ancor(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- If saving the changes fails and the user decides to continue, the messages are not cleared, so a second failure will show the old error messages alongside the new ones. The solution is already known, reporting since I need a bcn in order to submit the fix. -- 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 1

[Bug 786460] New: openSUSE:12.2/libtool: Bug
by bugzilla_noreply＠novell.com 25 Jul '14

25 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=786460 https://bugzilla.novell.com/show_bug.cgi?id=786460#c0 Summary: openSUSE:12.2/libtool: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: pth(a)suse.com ReportedBy: ar16(a)imapmail.org QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Community User Blocker: --- lsb_release -a LSB Version: core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch Distributor ID: SUSE LINUX Description: openSUSE 12.2 (x86_64) Release: 12.2 Codename: Mantis rpm -qa | grep -i libtool libtool-2.4.2-5.1.2.x86_64 grep ^sys_lib_dlsearch_path_spec /usr/bin/libtool sys_lib_dlsearch_path_spec="/lib /usr/lib /usr/local/lib64 /usr/local/lib " on x86_64 that shouldn't be "/lib /usr/lib", but rather "/lib64 /usr/lib64". arguably, /usr/lib/lib64 should lead the order ... -- 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 5

[Bug 885662] New: python-3.4 ensurepip is broken
by bugzilla_noreply＠novell.com 25 Jul '14

25 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=885662 https://bugzilla.novell.com/show_bug.cgi?id=885662#c0 Summary: python-3.4 ensurepip is broken Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: jmatejek(a)suse.com ReportedBy: speilicke(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Seems like the recently added ensurepip patch is broken, pip isn't installed into the venv anymore. saschpe@bort:~/Projects/scrello pyvenv .venv34 > /usr/lib64/python3.4/venv/__init__.py(251)_setup_pip() -> subprocess.check_output(cmd, stderr=subprocess.STDOUT) (Pdb) l 246 # environment vars, the current directory and anything else 247 # intended for the global Python environment 248 cmd = [context.env_exe, '-Im', 'ensurepip', '--upgrade', 249 '--default-pip'] 250 import pdb; pdb.set_trace() 251 -> subprocess.check_output(cmd, stderr=subprocess.STDOUT) 252 253 def setup_scripts(self, context): 254 """ 255 Set up scripts into the created environment from a directory. 256 (Pdb) subprocess.check_output(cmd) /home/saschpe/Projects/scrello/.venv34/bin/python3.4: Error while finding spec for 'ensurepip.__main__' (<class 'ImportError'>: Module 'pip' is missing. Use: sudo zypper install python3-pip to install it. See README.SUSE for more information.); 'ensurepip' is a package and cannot be directly executed *** subprocess.CalledProcessError: Command '['/home/saschpe/Projects/scrello/.venv34/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1 (Pdb) q Error: saschpe@bort:~/Projects/scrello zypper if python3-pip Loading repository data... Reading installed packages... ... Name: python3-pip Version: 1.5.6-0 Installed: Yes ... saschpe@bort:~/Projects/scrello find .venv34 .venv34 .venv34/lib .venv34/lib/python3.4 .venv34/lib/python3.4/site-packages .venv34/include .venv34/pyvenv.cfg .venv34/bin .venv34/bin/python .venv34/bin/python3.4 .venv34/bin/python3 .venv34/lib64 saschpe@bort:~/Projects/scrello .venv34/bin/python3.4 -Im ensurepip --upgrade --default-pip git:master✗ /home/saschpe/Projects/scrello/.venv34/bin/python3.4: Error while finding spec for 'ensurepip.__main__' (<class 'ImportError'>: Module 'pip' is missing. Use: sudo zypper install python3-pip to install it. See README.SUSE for more information.); 'ensurepip' is a package and cannot be directly executed That's pretty obvious since the following works: saschpe@bort:~/Projects/scrello pyvenv --without-pip v saschpe@bort:~/Projects/scrello find v v v/lib v/lib/python3.4 v/lib/python3.4/site-packages v/include v/pyvenv.cfg v/bin v/bin/activate.csh v/bin/activate.fish v/bin/python v/bin/python3.4 v/bin/activate v/bin/python3 v/lib64 -- 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 5

[Bug 886362] New: btrfs "crap" filesystem full signaling
by bugzilla_noreply＠novell.com 25 Jul '14

25 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=886362 https://bugzilla.novell.com/show_bug.cgi?id=886362#c0 Summary: btrfs "crap" filesystem full signaling Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: diego.ercolani(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 I know that is this by design but is very annoying that btrfs (expecially) when used as compressed filesystem doesn't manage the df command well because of metadata, deduplication, compression, balancing and so on. But we need that btrfs manage something useful with df, df is easy to process and with a single simple command to have the snapshot of what is happending. It's very annoying to manage the problem of having the filesystem full just when it happens. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 5

[Bug 876649] New: Can't update tracker
by bugzilla_noreply＠novell.com 25 Jul '14

25 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=876649 https://bugzilla.novell.com/show_bug.cgi?id=876649#c0 Summary: Can't update tracker Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: coolo(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- zypper complained: Detected 1 file conflict: File /usr/share/glib-2.0/schemas/org.freedesktop.Tracker.Extract.gschema.xml from install of libtracker-common-1_0-1.0.0-1.1.x86_64(repo-oss) conflicts with file from package libtracker-extract-0_16-0-0.16.4-1.7.x86_64(@System) Looks like it's missing an obsolete/conflict -- 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 3

[Bug 887013] New: Installing ecryptfs-utils produces an RPM scriptlet failure
by bugzilla_noreply＠novell.com 25 Jul '14

25 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=887013 https://bugzilla.novell.com/show_bug.cgi?id=887013#c0 Summary: Installing ecryptfs-utils produces an RPM scriptlet failure Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: seroton10(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 On a fully updated standard installation of openSUSE 13.1, I try to install the ecryptfs-utils package. This produces an RPM scriptlet error in which it complains about a missing PAM module. Reproducible: Always Steps to Reproduce: First-time install of ecryptfs-utils tested on several systems, always with the same result. Actual Results: themachine:~ # zypper in ecryptfs-utils Loading repository data... Reading installed packages... Resolving package dependencies... The following 20 NEW packages are going to be installed: ecryptfs-utils ecryptfs-utils-32bit gnome-keyring-32bit libffi4-32bit libfreebl3-32bit libgmp10-32bit libgnutls28-32bit libhogweed2-32bit libnettle4-32bit libp11-kit0-32bit libpkcs11-helper1-32bit libsoftokn3-32bit libsqlite3-0-32bit libtasn1-6-32bit libtspi1 libtspi1-32bit mozilla-nspr-32bit mozilla-nss-32bit mozilla-nss-certs-32bit trousers 20 new packages to install. Overall download size: 3.7 MiB. After the operation, additional 9.2 MiB will be used. Continue? [y/n/? shows all options] (y): Retrieving package libffi4-32bit-4.8.1_20130909-3.2.1.x86_64 (1/20), 18.1 KiB ( 25.5 KiB unpacked [cut] ( 1/20) Installing: libffi4-32bit-4.8.1_20130909-3.2.1 ..................................................[done [cut] (11/20) Installing: ecryptfs-utils-103-3.1.3 ............................................................[done Additional rpm output: setting /sbin/mount.ecryptfs_private to root:root 4755. (wrong permissions 0755) ERROR: module /lib/security/pam_ecryptfs.so is not installed. warning: %post(ecryptfs-utils-103-3.1.3.x86_64) scriptlet failed, exit status 1 [cut] Expected Results: No RPM scriptlet errors about missing PAM libraries. -- 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 2

[Bug 888954] New: File-open dialog does not work correctly with KDE4 mozilla integration
by bugzilla_noreply＠novell.com 25 Jul '14

25 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=888954 https://bugzilla.novell.com/show_bug.cgi?id=888954#c0 Summary: File-open dialog does not work correctly with KDE4 mozilla integration Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: sebastian(a)music-starvation.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=599901) --> (http://bugzilla.novell.com/attachment.cgi?id=599901) Test HTML file with file chooser button User-Agent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.16 When clicking on a "file open" button on a webpage displayed in Firefox the native KDE4 file chooser appears. This works on the first and on the second time but on the third time nothing happens any more. This happens only with installed KDE4 mozilla integration. When removing the package mozilla-kde4-integration and using the native Firefox dialog everything works well. Reproducible: Always Steps to Reproduce: 1. Open the following example html-page in Firefox with mozilla-kde4-integration installed: <html><body><input type="file"></body></html> 2. Click on the button, select a file and click "open" in native KDE4 dialog 3. Click again on the button, select a file and click "open" again 4. Click again on the button Actual Results: No file chooser dialog opens Expected Results: KDE4 file chooser should open again like the times before -- 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 0

[Bug 821040] New: openSUSE:12.3/lftp: Unknown command: ssl:ca-file in /etc/lftp.conf
by bugzilla_noreply＠novell.com 25 Jul '14

25 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=821040 https://bugzilla.novell.com/show_bug.cgi?id=821040#c0 Summary: openSUSE:12.3/lftp: Unknown command: ssl:ca-file in /etc/lftp.conf Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Minor Priority: P5 - None Component: 3rd party software AssignedTo: pascal.bleser(a)opensuse.org ReportedBy: cherenz(a)aip.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- lftp works fine, but it always complains in the first line: Unknown command `ssl:ca-file'. This command is stated in the global configuration file which is /etc/lftp.conf which shipped with the official rpm in openSUSE 12.3. Minor annoyance! -- 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 2

[Bug 887066] New: UEFI Boot Entry Disappeared After Updates
by bugzilla_noreply＠novell.com 25 Jul '14

25 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=887066 https://bugzilla.novell.com/show_bug.cgi?id=887066#c0 Summary: UEFI Boot Entry Disappeared After Updates Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: Espionage724(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 Relevant thread: https://forums.opensuse.org/showthread.php/494374-UEFI-Boot-Entry-Disappear… With a fresh instal of openSUSE 13.1 in UEFI, the boot entry for opensuse exists, and all is well. After doing updates (not sure which one in particular is responsible), the UEFI boot entry is removed, and thus, leaves you unable to reboot the system. This has happened as early as January that I've seen, and was reproducible on 3 different computers (two being desktops, one having an ASRock 970 Extreme3 motherboard, one having an ASRock Fatal1ty H97 Killer motherboard, one being an Acer Aspire V3-551G-X419 laptop). Running "update-bootloader --reinit" before rebooting puts the opensuse boot entry back, and rebooting is fine afterward. "efibootmgr -c -d /dev/sda -p 1 -L opensuse-secure -l '\EFI\opensuse\grubx64.efi.efi'" (not 100% sure on the exact command) seems to also re-add the boot entry and allow for successful reboots. Reproducible: Always Steps to Reproduce: 1. Install openSUSE 13.1 in UEFI-mode with SecureBoot disabled 2. Check "efibootmgr -v" and see the opensuse entry 3. Install all available updates from default repositories (about 600MB+ worth of them at the time of writing) without rebooting Actual Results: "efibootmgr -v" right after installing the updates should show no opensuse entry anymore, and rebooting should result in being unable to boot into openSUSE due to the lack-of a boot entry. Expected Results: "efibootmgr -v" should show the opensuse boot entry, and rebooting after updates should boot back into openSUSE without problem due to the existence of the opensuse boot entry. This has happened since January 2014 from what I noted, and still occurs as of July. SecureBoot was disabled throughout the entire process. Unsure if this is reproducible with SecureBoot being enabled. -- 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 7