June 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1076039] New: science/slepc: Bug slepc-openmpi-devel not installable
by bugzilla_noreply＠novell.com 30 Apr '20

30 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1076039 Bug ID: 1076039 Summary: science/slepc: Bug slepc-openmpi-devel not installable Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: dmitry(a)roshchin.org Reporter: gass(a)search.ch QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- slepc-openmpi-devel is not installable on openSUSE Tumbleweed or openSUSE Leap 42.2. Commands to reproduce the problem: zypper addrepo 'http://download.opensuse.org/repositories/science/openSUSE_Leap_42.2/' science zypper install slepc-openmpi-devel Relevant output: Problem: nothing provides petsc-openmpi-devel needed by slepc-openmpi-devel-3.7.3-1.19.x86_64 Greetings Nathan Gass -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1063167] New: crash of synergyc
by bugzilla_noreply＠novell.com 28 Apr '20

28 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1063167 Bug ID: 1063167 Summary: crash of synergyc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- noether:~ # coredumpctl list synergyc TIME PID UID GID SIG COREFILE EXE Tue 2017-09-05 14:35:11 CEST 3778 223 50 11 missing /usr/bin/synergyc Tue 2017-09-12 12:49:47 CEST 2474 223 50 11 missing /usr/bin/synergyc Thu 2017-10-05 08:23:57 CEST 2956 223 50 11 none /usr/bin/synergyc Thu 2017-10-05 08:56:20 CEST 32056 223 50 11 none /usr/bin/synergyc Thu 2017-10-05 10:17:47 CEST 2495 223 50 11 none /usr/bin/synergyc Thu 2017-10-05 10:51:14 CEST 4517 223 50 11 none /usr/bin/synergyc Mon 2017-10-09 13:54:01 CEST 2147 223 50 11 none /usr/bin/synergyc Mon 2017-10-09 14:28:03 CEST 12156 223 50 11 none /usr/bin/synergyc Tue 2017-10-10 12:45:05 CEST 13178 223 50 11 none /usr/bin/synergyc Wed 2017-10-11 15:02:24 CEST 20573 223 50 11 present /usr/bin/synergyc -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 894783] New: CA management: Sign Request: Don't use sequential serial numbers
by bugzilla_noreply＠novell.com 26 Apr '20

26 Apr '20

https://bugzilla.novell.com/show_bug.cgi?id=894783 https://bugzilla.novell.com/show_bug.cgi?id=894783#c0 Summary: CA management: Sign Request: Don't use sequential serial numbers Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Firefox/31.0 (In openssl tradition certificates use sequential serial numbers) YaST's certificate signing function uses sequential serial numbers to issue (sign) certificates (like 01, 02, 03, ... 09, 0A, 0B, ...) Due to some weaknesses in SHA-1, there's a recommendation to use serial numbers with a higher entropy. See https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/ElekSignatur/BSI_SHA1_Z… (German): ---BEGIN quote--- Kollisionsangriffe gegen die Zertifikaterstellung mit SHA-1 können von vornherein verhindert werden, wenn folgendes gilt: 1) Es wird das X.509v3 Format gemäß ISIS-MTT verwendet. 2) Die Seriennummer ("serialNumber") des Zertifikats hat eine genügend hohe Entropie h für den Angreifer. D.h. die Unsicherheit des Angreifers über die Seriennummer eines zu erstellenden Zertifikats ist mindestens h Bits. (...) ---END quote--- Reproducible: Always Steps to Reproduce: 1. Sign a certificate request (CSR) in YaST's CA management Actual Results: The certificate gets a serial number that can easily be guessed Expected Results: The serial number should not be easy to guess See also http://www.heise.de/security/meldung/Fragwuerdige-Hash-Funktion-SHA-1-immer… (German) -- 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 1095131] New: kubelet service (1.10.2) fails to start: failed to get device for dir "/var/lib/kubelet"
by bugzilla_noreply＠novell.com 26 Apr '20

26 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1095131 Bug ID: 1095131 Summary: kubelet service (1.10.2) fails to start: failed to get device for dir "/var/lib/kubelet" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: mmeister(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.170 Safari/537.36 Build Identifier: May 30 04:56:24 admin hyperkube[2766]: F0530 04:56:24.779150 2766 kubelet.go:1354] Failed to start ContainerManager failed to get rootfs info: failed to get device for dir "/var/lib/kubelet": could not find device with major: 0, minor: 46 in cached partitions map kubelet wont start with kubernetes 1.10.2 it might be a regression of https://github.com/google/cadvisor/pull/1668 ? k8s is not yet updated officially, i have used: https://build.opensuse.org/package/show/home:m_meister:branches:devel:CaaSP… tested on the Stack-hardware image, which comes with the additional 9p kernel modules and k8s preinstalled: https://download.opensuse.org/repositories/devel:/CaaSP:/images/images/open… some previous discussion can be found also in https://bugzilla.suse.com/show_bug.cgi?id=1084766 Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1021335] New: desktop files randomly miss translations
by bugzilla_noreply＠novell.com 23 Apr '20

23 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1021335 Bug ID: 1021335 Summary: desktop files randomly miss translations Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE 42.2 Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ke(a)suse.com Found By: Development Blocker: --- While working on making builds reproducible for openSUSE, I found multiple packages randomly missing translations in .desktop files. Affected packages are at least exo gedit gedit-plugins gnome-menus gnome-video-effects lxmenu-data for an example diff see https://www.zq1.de/~bernhard/linux/reproducibleopensuse/compare.factory/exo… when looking at the build.log it had sequences like [ 49s] Generating and caching the translation database [ 49s] Merging translations into debian-sensible-browser.desktop. [ 49s] LC_ALL=C /usr/bin/intltool-merge -d -u -c ../../po/.intltool-merge-cache ../../po epiphany.desktop.in epiphany.desktop [ 49s] Found cached translation database [ 49s] Merging translations into epiphany.desktop. [ 49s] LC_ALL=C /usr/bin/intltool-merge -d -u -c ../../po/.intltool-merge-cache ../../po eterm.desktop.in eterm.desktop [ 49s] Generating and caching the translation database [ 49s] Merging translations into encompass.desktop. [ 49s] LC_ALL=C /usr/bin/intltool-merge -d -u -c ../../po/.intltool-merge-cache ../../po evolution.desktop.in evolution.desktop [ 49s] Generating and caching the translation database [ 49s] Merging translations into debian-x-terminal-emulator.desktop. [ 49s] LC_ALL=C /usr/bin/intltool-merge -d -u -c ../../po/.intltool-merge-cache ../../po firefox.desktop.in firefox.desktop [ 49s] Found cached translation database so my guess is that this is running in parallel with make -j8 and thus there might be races with processes using the cache file before it is fully generated. Assiging to GNOME team as maintainers of intltool-merge tool -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1082655] New: vim: please, provide a /etc/vim.d
by bugzilla_noreply＠novell.com 23 Apr '20

23 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1082655 Bug ID: 1082655 Summary: vim: please, provide a /etc/vim.d Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: luizluca(a)tre-sc.jus.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As many other sw do, vim could use a config directory. It is just a matter of including those lines in /etc/vimrc for rcfile in split(globpath("/etc/vim.d/", "*.vim"), '\n') execute('source '.rcfile) endfor -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1041112] New: KDE packagekit update dialog shows still updates available for a short time after applying updates
by bugzilla_noreply＠novell.com 23 Apr '20

23 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1041112 Bug ID: 1041112 Summary: KDE packagekit update dialog shows still updates available for a short time after applying updates Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other URL: http://lord.arch/tests/6386/modules/updates_packagekit _kde/steps/15 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-42.2-UpdateTest-x86_64-fix_kde_update_tray@64bit-2G fails in [updates_packagekit_kde](http://lord.arch/tests/6386/modules/updates_packagekit_kde/steps/15) showing that there is an update available which has been installed just in before by a click on "Install Updates" button. This is detected by the openQA tests in about 30-50 percent of all cases. Going through the video from http://lord.arch/tests/6386/file/video.ogv is giving the best impression. There it can clearly be seen that after a click on "install updates" these are installed, the dialog shows the 1 update to install again, then it suddenly shows that there are no updates to install. Further logs are available: http://lord.arch/tests/6386#downloads ## Reproducible Fails since (at least) Build [20170526-3](http://lord.arch/tests/6361) ## Expected result Last good: (unknown), probably in there like "forever". Expected behaviour is that after refreshing there are no available updates shown anymore. Is this related to how package kit related events are handled and libzypp and such? ## Further details Always latest result in this scenario: [latest](http://lord.arch/tests/latest?flavor=UpdateTest&version=42.2&distri=opensuse&machine=64bit-2G&arch=x86_64&test=fix_kde_update_tray). Bug 992773 is probably related. If necessary we can try to provide more information in logs. Or should I report upstream? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1044250] New: FileSystems.rb - undefined method `split' for nil:NilClass
by bugzilla_noreply＠novell.com 20 Apr '20

20 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1044250 Bug ID: 1044250 Summary: FileSystems.rb - undefined method `split' for nil:NilClass Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: joyce.na(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 728882 --> http://bugzilla.suse.com/attachment.cgi?id=728882&action=edit y2logs issue: There is an error message when try to open "yast disk" Error Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Details: undefined method `split' for nil:NilClass Caller: /usr/share/YaST2/modules/FileSystems.rb:2114:in `btrfs_subvol_name_for' reproduce steps: 1.create 2 new partitions /dev/sda7 and /dev/sda8 2.mkfs.btrfs /dev/sda7 /dev/sda8 3.mount /dev/sda7 /mnt/backup 4.mount /dev/sda8 /mnt 5.yast disk Note:Ext4 and XFS do not have this issue,only btrfs failed. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1013047] New: Autoyast profile does not validate
by bugzilla_noreply＠novell.com 20 Apr '20

20 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1013047 Bug ID: 1013047 Summary: Autoyast profile does not validate Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: autoyast-maintainers(a)suse.de Reporter: mkravec(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 704429 --> http://bugzilla.suse.com/attachment.cgi?id=704429&action=edit autoinst.xml Generated profile fails to validate with: xmllint: - Element profile has extra content: add-on jing: - element "copy_on_write" not allowed here; expected the element end-tag or text - element "path" not allowed here; expected the element end-tag or text OpenQA link: http://dhcp91.suse.cz/tests/3181#step/yast2_clone_system/7 -- You are receiving this mail because: You are on the CC list for the bug.

1 40

[Bug 1079400] New: 389-ds upgrade to 1.3.4 breaks existing LDAP setups
by bugzilla_noreply＠novell.com 17 Apr '20

17 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1079400 Bug ID: 1079400 Summary: 389-ds upgrade to 1.3.4 breaks existing LDAP setups Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lbeltrame(a)kde.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I used to have a working LDAP setup with 389-ds and Tumbleweed, but once 1.3.4 hit the distribution the server refuses to start: - /etc/dirsrv/slapd-palver/dse.ldif[04/Feb/2018:20:41:46.884975571 +0100] - ERR - slapd_bootstrap_config - The default password storage scheme could not be read or was not found in the file /etc/dirsrv/slapd-palver/dse.ldif. It is mandatory. There were no changes in dse.ldif across version upgrades. Did anything change with regards to configuration (note: I wasn't able to find anything relevant in the 389-ds documentation)? -- You are receiving this mail because: You are on the CC list for the bug.

1 3