September 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 877241] New: Temporary directories are not being cleared
by bugzilla_noreply＠novell.com 11 Sep '14

11 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=877241 https://bugzilla.novell.com/show_bug.cgi?id=877241#c0 Summary: Temporary directories are not being cleared 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: yanestra(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 While CLEAR_TMP_DIRS_AT_BOOTUP is yes TMP_DIRS_TO_CLEAR is /tmp MAX_DAYS_IN_TMP is 2 the files in /tmp are rotting for weeks. Same problem with ..._LONG_... 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 3

[Bug 895997] New: gnome-control-center requires PackageKit
by bugzilla_noreply＠novell.com 11 Sep '14

11 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=895997 https://bugzilla.novell.com/show_bug.cgi?id=895997#c0 Summary: gnome-control-center requires PackageKit Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: itsbo(a)fz-juelich.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 The gnome-control-center now requires gnome-color-manager. gnome-color-manager in turn requires PackageKit. This is unwanted in a managed environment and was not the case with OpenSuSE 12.3 Please remove either gnome-color-manager requirement from gnome-control-center -or- remove PackageKit as a requirement by gnome-color-manager Reproducible: Always Steps to Reproduce: 1. Install pattern gnome 2. 3. Actual Results: PackageKit is installed Expected Results: Packagekit is not installed -- 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 804748] New: Allow to enter password after pam_fprint.so timeout
by bugzilla_noreply＠novell.com 11 Sep '14

11 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=804748 https://bugzilla.novell.com/show_bug.cgi?id=804748#c0 Summary: Allow to enter password after pam_fprint.so timeout Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: chodorenko(a)mail.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 please add in pam_fprint.so value of timeout wait fingerprint. In console all good work, in KDE all application required root access wait fingerprint without any messages. # cat /etc/pam.d/common-auth auth required pam_env.so auth sufficient pam_fprint.so auth optional pam_gnome_keyring.so auth required pam_unix2.so Reproducible: Always -- 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 8

[Bug 812421] New: Sysconfig editor in yast contains unused variables
by bugzilla_noreply＠novell.com 11 Sep '14

11 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=812421 https://bugzilla.novell.com/show_bug.cgi?id=812421#c0 Summary: Sysconfig editor in yast contains unused variables Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: erwin.vandevelde(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 The varibales for cleaning out TMP directories are unused in openSUSE 12.3, but you can still configure them in the sysconfig editor in yast, which is confusing. These variables should be removed (and possibly other unused variables as well) from the editor. Reproducible: Always -- 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 10

[Bug 893441] New: Base:System/filesystem: Add %_datadir/appdata
by bugzilla_noreply＠novell.com 11 Sep '14

11 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=893441 https://bugzilla.novell.com/show_bug.cgi?id=893441#c0 Summary: Base:System/filesystem: Add %_datadir/appdata Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: ro(a)suse.com ReportedBy: johannesobermayr(a)gmx.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- More and more packages (esp. KDE applications) install files in %_datadir/appdata. So it should be added to filesystem. -- 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 783100] New: zypper: doesn't account for btrfs snapshots when calculating disk space
by bugzilla_noreply＠novell.com 11 Sep '14

11 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=783100 https://bugzilla.novell.com/show_bug.cgi?id=783100#c0 Summary: zypper: doesn't account for btrfs snapshots when calculating disk space Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: jeffm(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- When installing updates, zypper will assume that the space occupied by packages being updated will be removed. If the file system is a btrfs file system with snapshots turned on, then the space will not be freed during update and we can run out of space unexpectedly. -- 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 6

[Bug 895884] New: The 20140904 factory snapshot adds an extraneous "," to end of EFI subdirectory name
by bugzilla_noreply＠novell.com 11 Sep '14

11 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=895884 https://bugzilla.novell.com/show_bug.cgi?id=895884#c0 Summary: The 20140904 factory snapshot adds an extraneous "," to end of EFI subdirectory name Classification: openSUSE Product: openSUSE Factory Version: 201409* Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: nrickert(a)ameritech.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Background. In "/etc/default/grub", I have the line: GRUB_DISTRIBUTOR=betasuse That so that my factory install will use a different directory name in the EFI partition. Now, looking at the EFI partition, I see: # ls -l /boot/efi/EFI total 20 drwxrwxr-x 2 croot root 4096 Jul 10 11:37 arch drwxrwxr-x 2 croot root 4096 Mar 22 14:45 betasuse drwxrwxr-x 2 croot root 4096 Sep 1 09:21 betasuse, drwxrwxr-x 2 croot root 4096 Mar 23 13:56 Boot drwxrwxr-x 2 croot root 4096 Jul 20 10:03 opensuse That directory name "betasuse," looks like a bug to me. I had expected it to reuse the "betasuse" directory. On checking the output from "efibootmgr -v", I see (as one of the output lines): Boot0004* betasuse, HD(2,800,fa000,bf8f0c7b-6395-4d74-9c29-8731cbca231d)File(\EFI\betasuse,\grubx64.efi) That was the entry that I last booted from (I have since changed the order to what I want). In summary: I don't think that "," is supposed to be there. 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 6

[Bug 896122] New: kiwi: warnings when creating symlinks in /usr/src/packages/SOURCES/repos
by bugzilla_noreply＠novell.com 11 Sep '14

11 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=896122 https://bugzilla.novell.com/show_bug.cgi?id=896122#c0 Summary: kiwi: warnings when creating symlinks in /usr/src/packages/SOURCES/repos Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: System Imaging AssignedTo: ms(a)suse.com ReportedBy: aspiers(a)suse.com QAContact: adrian(a)suse.com Found By: Development Blocker: --- When locally building https://build.suse.de/package/show/Devel:Cloud:4/suse-cloud-vagrant-admin I see failures from ln(1) like this: [ 139s] Saving Primary metadata [ 139s] Saving file lists metadata [ 139s] Saving other metadata [ 139s] ln: failed to create symbolic link 'Devel:/Cloud:/4/SLE_11_SP3/SLE_11_SP3': File exists [ 139s] creating repodata for /usr/src/packages/SOURCES/repos/Devel:/Cloud:/4/SLE_11_SP3/ [ 142s] Spawning worker 0 with 176 pkgs [ 142s] Workers Finished [ 142s] Gathering worker results [ 142s] [ 142s] Saving Primary metadata [ 142s] Saving file lists metadata [ 142s] Saving other metadata [ 142s] ln: failed to create symbolic link 'Devel:/Cloud:/Shared:/11-SP3/standard/standard': File exists [ 142s] creating repodata for /usr/src/packages/SOURCES/repos/Devel:/Cloud:/Shared:/11-SP3/standard/ [ 143s] Spawning worker 0 with 115 pkgs [ 143s] Workers Finished [ 143s] Gathering worker results Is this simply an artefact of bug #895204 preventing kiwi from cleaning up these links properly at the end of the previous build, or are they supposed to persist across (local) builds? If the latter, the ln(1) should only be attempted if the symlink doesn't already exist. -- 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 896126] New: kiwi: suseImportBuildKey should be more robust
by bugzilla_noreply＠novell.com 11 Sep '14

11 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=896126 https://bugzilla.novell.com/show_bug.cgi?id=896126#c0 Summary: kiwi: suseImportBuildKey should be more robust Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: System Imaging AssignedTo: ms(a)suse.com ReportedBy: aspiers(a)suse.com QAContact: adrian(a)suse.com Found By: Development Blocker: --- https://build.suse.de/build/Devel:Cloud:4/vagrantbox_images/x86_64/suse-clo… shows the following errors: [ 233s] /.kconfig: line 209: /usr/lib/rpm/gnupg/dumpsigs: No such file or directory [ 233s] ls: cannot access gpg-pubkey-*.asc: No such file or directory [ 233s] / when config.sh invokes the following code: #====================================== # Add missing gpg keys to rpm #-------------------------------------- suseImportBuildKey I'm guessing this is because neither the suse-build-key nor openSUSE-build-key rpms were installed, so /usr/lib/rpm/gnupg/dumpsigs doesn't exist. But suseImportBuildKey could check for its existence before running and offer a more helpful error which suggests adding either of these packages to the kiwi config file. -- 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 896128] New: kiwi: doesn't clean up /usr/src/packages/KIWIROOT-vmx after build
by bugzilla_noreply＠novell.com 11 Sep '14

11 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=896128 https://bugzilla.novell.com/show_bug.cgi?id=896128#c0 Summary: kiwi: doesn't clean up /usr/src/packages/KIWIROOT-vmx after build Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: System Imaging AssignedTo: ms(a)suse.com ReportedBy: aspiers(a)suse.com QAContact: adrian(a)suse.com Found By: Development Blocker: --- If I do two local osc builds of a Vagrant box, the second one always fails with something like this: [ 226s] Sep-10 23:01:58 <1> : Setting up source channel: [ 226s] Sep-10 23:01:58Sep-10 23:01:58 <3> : Couldn't mkdir '/usr/src/packages/KIWIROOT-vmx': File exists [ 226s] Sep-10 23:01:58 <3> : Couldn't create root directory: File exists [ 226s] Sep-10 23:01:58 <3> : Couldn't create root object [ 226s] Sep-10 23:01:58 <3> : KIWI exited with error(s) If I then do sudo rm -rf /usr/src/packages/KIWIROOT-vmx and retry the osc build, it works. But this cleanup should be done automatically. -- 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