November 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1171368] New: [Build 20200506] openQA ppc64 test fails with new ruby 2.7
by bugzilla_noreply＠novell.com 02 Nov '22

02 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1171368 Bug ID: 1171368 Summary: [Build 20200506] openQA ppc64 test fails with new ruby 2.7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1258904/modules/welc ome/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Ruby Assignee: ruby-devel(a)suse.de Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- [Build 20200506] openQA ppc64 test fails with new ruby 2.7 ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-ppc64-gpt@ppc64 fails in [welcome](https://openqa.opensuse.org/tests/1258904/modules/welcome/steps/7) This is the first openQA tests for TW PowerPC since new ruby 2.7 reported message: === YaST2 ... internal error Caller: /mounts/mp_0001/usr/lib64/ruby/2.7.0/rubygems/core_ext/kernel_requires.rb:92:in `require' Details: cannot load such file -- storage ... === no data reported by openQA env, I will do a manual trial. ## Test suite description ## Reproducible Fails since (at least) Build [20200506](https://openqa.opensuse.org/tests/1258904) (current job) ## Expected result Last good: [20200501](https://openqa.opensuse.org/tests/1251875) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64&distri=opensuse… -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1177956] New: [Build 20201020] openQA test fails in await_install: grub2-install fails for i386-pc
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1177956 Bug ID: 1177956 Summary: [Build 20201020] openQA test fails in await_install: grub2-install fails for i386-pc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1443345/modules/awai t_install/steps/9 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: mchang(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: --- With this fairly standard and simple ext4 setup (see https://openqa.opensuse.org/tests/1443345#step/partitioning_filesystem/9 for the YaST view), the installation fails with grub2-install complaining: "failed to get canonical path of `/boot/grub2/i386-pc'." This failure also happens in lvm-encrypt-separate-boot and autoyast_multi_btrfs tests, but doesn't appear to affect standard cryptlvm or btrfs setups. My guess ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-ext4_textmode@64bit fails in [await_install](https://openqa.opensuse.org/tests/1443345/modules/await_inst… ## Test suite description Mantainer: jeriveramoya Test selection of file system ext4 for / partition in textmode for openSUSE distributions ## Reproducible Fails since (at least) Build [20201020](https://openqa.opensuse.org/tests/1443345) (current job) ## Expected result Last good: [20201019](https://openqa.opensuse.org/tests/1441513) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1177957] New: [Build 20201020] openQA test fails in await_install: grub2-install fails for i386-pc
by bugzilla_noreply＠suse.com 02 Nov '22

02 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1177957 Bug ID: 1177957 Summary: [Build 20201020] openQA test fails in await_install: grub2-install fails for i386-pc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1443345/modules/awai t_install/steps/9 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: mchang(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: --- With this fairly standard and simple ext4 setup (see https://openqa.opensuse.org/tests/1443345#step/partitioning_filesystem/9 for the YaST view), the installation fails with grub2-install complaining: "failed to get canonical path of `/boot/grub2/i386-pc'." This failure also happens in lvm-encrypt-separate-boot and autoyast_multi_btrfs tests, but doesn't appear to affect standard cryptlvm or btrfs setups. My guess ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-ext4_textmode@64bit fails in [await_install](https://openqa.opensuse.org/tests/1443345/modules/await_inst… ## Test suite description Mantainer: jeriveramoya Test selection of file system ext4 for / partition in textmode for openSUSE distributions ## Reproducible Fails since (at least) Build [20201020](https://openqa.opensuse.org/tests/1443345) (current job) ## Expected result Last good: [20201019](https://openqa.opensuse.org/tests/1441513) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1171115] New: PERMISSION_SECURITY="secure local" - KDE hangs on logout when choosing "shut down"
by bugzilla_noreply＠novell.com 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1171115 Bug ID: 1171115 Summary: PERMISSION_SECURITY="secure local" - KDE hangs on logout when choosing "shut down" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- PERMISSION_SECURITY="secure local" in /etc/sysconfig/security works for most things even in desktop usage, but KDE hangs on logout when choosing "shut down" (german "Herunterfahren"). The fix for this are the following two entries in /etc/polkit-default-privs.local: org.freedesktop.login1.power-off auth_admin_keep:auth_admin_keep:yes org.freedesktop.login1.reboot auth_admin_keep:auth_admin_keep:yes After running /sbin/set_polkit_default_privs I can shut down my computer from the KDE logout dialog again. Please consider to add these two for polkit-default-privs.restrictive. (Without these two lines, the workaround is to logout, and then shutdown from sddm ;-) Sidenotes: - The default in restrictive is "auth_admin_keep", and I guess it's too late in the logout process to show a password dialog, so the logout simply hangs. - The only other local rules I need to live with "permissions.secure" are org.freedesktop.packagekit.system-sources-refresh auth_admin_keep_always:no:yes org.freedesktop.NetworkManager.network-control no:no:yes # mount / umount USB stick org.freedesktop.udisks2.filesystem-mount auth_admin:auth_admin:yes org.freedesktop.udisks2.eject-media auth_admin:auth_admin:yes -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1118099] New: aws-cli-1.16.48-1.1.noarch requires python3-colorama <= 0.3.9, but this requirement cannot be provided
by bugzilla_noreply＠novell.com 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1118099 Bug ID: 1118099 Summary: aws-cli-1.16.48-1.1.noarch requires python3-colorama <= 0.3.9, but this requirement cannot be provided Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cloud:Tools Assignee: public-cloud-maintainers(a)suse.de Reporter: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It seems that the aws-cli / python3-colorama dance is up again :-) Problem: aws-cli-1.16.48-1.1.noarch requires python3-colorama <= 0.3.9, but this requirement cannot be provided deleted providers: python3-colorama-0.3.9-1.3.noarch Solution 1: deinstallation of aws-cli-1.16.48-1.1.noarch Solution 2: keep obsolete python3-colorama-0.3.9-1.3.noarch Solution 3: break aws-cli-1.16.48-1.1.noarch by ignoring some of its dependencies -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1174680] New: [Build 20200728] yast sudo - syntax error in /etc/sudoers.YaST2.new
by bugzilla_noreply＠suse.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1174680 Bug ID: 1174680 Summary: [Build 20200728] yast sudo - syntax error in /etc/sudoers.YaST2.new Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1346585/modules/yast 2_control_center/steps/44 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_gui@64bit fails in [yast2_control_center](https://openqa.opensuse.org/tests/1346585/modules/yas… The log file contains this (hopefully relevant) excerpt >2020-07-29 08:55:45 <0> susetest(10814) [libscr] SCR.cc(SCRWrite2):67 Running SCR::Write (2 args) on SCR agent 0x55c9153b35e0 2020-07-29 08:55:45 <0> susetest(10814) [scr] ScriptingAgent.cc(executeSubagentCommand):589 ScriptingAgent::executeSubagentCommand: Write 2020-07-29 08:55:45 <0> susetest(10814) [scr] ScriptingAgent.cc(executeSubagentCommand):590 path: .sudo 2020-07-29 08:55:45 <0> susetest(10814) [scr] ScriptingAgent.cc(executeSubagentCommand):591 arg: nil 2020-07-29 08:55:45 <0> susetest(10814) [scr] ScriptingAgent.cc(executeSubagentCommand):592 opt: null 2020-07-29 08:55:46 <3> susetest(10822) [ag_etc_sudoers] Syntax error in /etc/sudoers.YaST2.new 2020-07-29 08:55:46 <0> susetest(10814) [libycp] parser.yy(yyparse):404 ## Test suite description Maintainer: qsf-y Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests. Temporarily added YAST2_GUI_TERMINATE_PREVIOUS_INSTANCES to see if helps. This variable triggers code which terminates all yast2 processes before starting new one. (see poo#26104). ## Reproducible Fails since (at least) Build [20200728](https://openqa.opensuse.org/tests/1346327) ## Expected result Last good: [20200727](https://openqa.opensuse.org/tests/1345093) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[opensuse-bugs] [Bug 1179342] New: [deprecated-init-script] openstack-suse-macros
by bugzilla_noreply＠suse.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1179342 Bug ID: 1179342 Summary: [deprecated-init-script] openstack-suse-macros Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: OpenStack Assignee: cloud-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package suse-deprecated-init-script is one of the very few remaining that trigger the rpmlint warning openstack-suse-macros.noarch: W: suse-deprecated-init-script /etc/init.d/openstack-skeleton SysV init scripts are deprecated. Please migrate to systemd service files. This warning is going to be changed to an error rather soon. This skeleton is used by the macro %openstack_init_script_install which in turn seems not to be used by any package anymore. There are currently 2 package BuildRequiring openstack-suse-macros: python-openstack.nose_plugin python-sphinxcontrib-pecanwsme where none of the two actually make uses of any macro defined in openstack-suse-macros. This smells a lot like it could just be eliminated (instead of trying to invest the time to migrate it properly to systems services) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1159263] New: [Build 20191214] Yast modules: Window title seems to contain trailing whitespaces
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1159263 Bug ID: 1159263 Summary: [Build 20191214] Yast modules: Window title seems to contain trailing whitespaces Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1114514/modules/yast 2_lang/steps/13 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_gui@64bit fails in [yast2_lang](https://openqa.opensuse.org/tests/1114514/modules/yast2_lang/st… The window title is not centered, and also in the GNOME TopBar, the window name is indicating that it continues with a lot of spaces behind the actual name ## Test suite description Maintainer: zluo, riafarov Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests. Temporarily added YAST2_GUI_TERMINATE_PREVIOUS_INSTANCES to see if helps. This variable triggers code which terminates all yast2 processes before starting new one. (see poo#26104). ## Reproducible Fails since (at least) Build [20191211](https://openqa.opensuse.org/tests/1111241) ## Expected result Last good: [20191210](https://openqa.opensuse.org/tests/1109911) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1157790] New: [Build 20191125][firewalld?] Upgrade from 13.1 to TW: curl fails to download files
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1157790 Bug ID: 1157790 Summary: [Build 20191125][firewalld?] Upgrade from 13.1 to TW: curl fails to download files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1096186/modules/prep are_test_data/steps/9 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-13.1-gnome@64bit_cirrus fails in [prepare_test_data](https://openqa.opensuse.org/tests/1096186/modules/prepar… This issue seems only to happen when upgrading openSUSE 13.1 to Tumbleweed - after firewalld has been upgraded. ## Test suite description Set hdd size to 10 to not going do snapshot test riafarov has added HDDSERIAL_1=1 poo#38963 ## Reproducible Fails since (at least) Build [20191125](https://openqa.opensuse.org/tests/1095468) ## Expected result Last good: [20191124](https://openqa.opensuse.org/tests/1095003) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1157785] New: [Build 20191125] openQA test fails in yast2_ftp
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1157785 Bug ID: 1157785 Summary: [Build 20191125] openQA test fails in yast2_ftp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1096178/modules/yast 2_ftp/steps/127 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ncurses@64bit fails in [yast2_ftp](https://openqa.opensuse.org/tests/1096178/modules/yast2_ftp/step… Since the upgrade to firewalld 07., the yat2 ftp module fails the test; seems the port is no longer being opened ## Test suite description Maintainer: zluo, riafarov Test for yast2 UI, ncurses only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests. riafarov set TIMEOUT_SCALE to improve stability of the test. ## Reproducible Fails since (at least) Build [20190202](https://openqa.opensuse.org/tests/846144) ## Expected result Last good: [20190110](https://openqa.opensuse.org/tests/829581) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

2 4