April 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1177262] New: Zypper does not honor locked kernel packages
by bugzilla_noreply＠suse.com 22 Sep '22

22 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177262 Bug ID: 1177262 Summary: Zypper does not honor locked kernel packages Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: arcasinky(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Machine in question uses Kernel:stable repository for kernels. I am attempting to configure zypper to not also install kernels from the normal Leap 15.2 update repository. Presently, the 15.2 update repo provides 5.3.x kernels. The Kernel:stable repo provides 5.8.x kernels. Currently-installed kernel packages: # rpm -qa | grep kernel-default-5 kernel-default-5.8.11-1.1.gf4bb27a.x86_64 kernel-default-5.8.12-1.1.g79e03c2.x86_64 kernel-default-5.8.13-1.1.gea492d4.x86_64 Test #1: create a package lock for 5.3.* kernels: # zypper al kernel-default-5.3* kernel-default-devel-5.3* kernel-devel-5.3* kernel-source-5.3* kernel-syms-5.3* Specified locks have been successfully added. # zypper ll # | Name | Type | Repository --+---------------------------+---------+----------- 1 | kernel-default-5.3* | package | (any) 2 | kernel-default-devel-5.3* | package | (any) 3 | kernel-devel-5.3* | package | (any) 4 | kernel-source-5.3* | package | (any) 5 | kernel-syms-5.3* | package | (any) # zypper update <stuff> The following 11 NEW packages are going to be installed: kernel-default-5.3.18-lp152.44.1 kernel-default-5.8.13-2.1.g08db7a3 kernel-default-devel-5.3.18-lp152.44.1 kernel-default-devel-5.8.13-2.1.g08db7a3 kernel-devel-5.3.18-lp152.44.1 kernel-devel-5.8.13-2.1.g08db7a3 kernel-preempt-devel kernel-source-5.3.18-lp152.44.1 kernel-source-5.8.13-2.1.g08db7a3 kernel-syms-5.3.18-lp152.44.1 kernel-syms-5.8.13-2.1.g08db7a3 <stuff> RESULTS: zypper ignores the package lock and wants to install 5.3.18 kernel. Test #2: Remove all package locks and create repository locks to prevent kernels from being installed from the 15.2 updates repository: # zypper al -r "openSUSE-Leap-15.2-Update" kernel-default* kernel-default-devel* kernel-syms* kernel-source* kernel-macros* kernel-devel* Specified locks have been successfully added. # zypper ll # | Name | Type | Repository --+-----------------------+---------+------------ 1 | kernel-default* | package | repo-update 2 | kernel-default-devel* | package | repo-update 3 | kernel-devel* | package | repo-update 4 | kernel-macros* | package | repo-update 5 | kernel-source* | package | repo-update 6 | kernel-syms* | package | repo-update # zypper update <stuff> The following 11 NEW packages are going to be installed: kernel-default-5.3.18-lp152.19.2 kernel-default-5.8.13-2.1.g08db7a3 kernel-default-devel-5.3.18-lp152.19.2 kernel-default-devel-5.8.13-2.1.g08db7a3 kernel-devel-5.3.18-lp152.19.2 kernel-devel-5.8.13-2.1.g08db7a3 kernel-preempt-devel kernel-source-5.3.18-lp152.19.2 kernel-source-5.8.13-2.1.g08db7a3 kernel-syms-5.3.18-lp152.19.2 kernel-syms-5.8.13-2.1.g08db7a3 <stuff> RESULTS: No change. The repository locks are ignored. zypper continues to want to install 5.3.18. Test #3: Remove those locks, create repository locks for Kernel:stable. # zypper al -r "Kernel:stable" kernel-default* kernel-default-devel* kernel-syms* kernel-source* kernel-macros* kernel-devel* Specified locks have been successfully added. # zypper ll # | Name | Type | Repository --+-----------------------+---------+-------------- 1 | kernel-default* | package | Kernel:stable 2 | kernel-default-devel* | package | Kernel:stable 3 | kernel-devel* | package | Kernel:stable 4 | kernel-macros* | package | Kernel:stable 5 | kernel-source* | package | Kernel:stable 6 | kernel-syms* | package | Kernel:stable # zypper update <stuff> The following 6 NEW packages are going to be installed: kernel-default-5.3.18-lp152.44.1 kernel-default-devel-5.3.18-lp152.44.1 kernel-devel-5.3.18-lp152.44.1 kernel-preempt-devel kernel-source-5.3.18-lp152.44.1 kernel-syms-5.3.18-lp152.44.1 <stuff> RESULTS: The locks for Kernel:stable are honored. The 5.8.13 kernels are no longer marked for installation. Final test: Remove the Kernel:stable locks and create repository locks for "@System": # zypper al -r "@System" kernel-default* kernel-default-devel* kernel-syms* kernel-source* kernel-macros* kernel-devel* Specified locks have been successfully added. # zypper ll # | Name | Type | Repository --+-----------------------+---------+----------- 1 | kernel-default* | package | (any) 2 | kernel-default-devel* | package | (any) 3 | kernel-devel* | package | (any) 4 | kernel-macros* | package | (any) 5 | kernel-source* | package | (any) 6 | kernel-syms* | package | (any) # zypper update <stuff> The following 31 items are locked and will not be changed by any action: Available: kernel-default-base kernel-default-base-rebuild kernel-default-debuginfo kernel-default-debugsource kernel-default-devel-debuginfo kernel-default-livepatch-devel kernel-devel-rt kernel-source-rt kernel-source-vanilla kernel-syms-rt <stuff> The following 9 package updates will NOT be installed: kernel-default-5.8.13-2.1.g08db7a3 kernel-default-devel-5.8.13-2.1.g08db7a3 kernel-devel-5.8.13-2.1.g08db7a3 kernel-macros kernel-source-5.8.13-2.1.g08db7a3 kernel-syms-5.8.13-2.1.g08db7a3 libseccomp-devel ... <stuff> RESULTS: That also seems to work. No kernels are marked for installation now. ---------- So, I can create a repository lock to prevent kernels from being installed from Kernel:stable. I can create a global @System lock to prevent all kernels from being installed. But I seem to be unable to create a lock to specifically prevent 5.3.18 kernels from being installed from the 15.2 updates repo while still allowing kernels to be installed from Kernel:stable. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1125814] New: [Build 20190125] YaST2 keyboard module applies settings even when Cancel button is pressed
by bugzilla_noreply＠novell.com 21 Sep '22

21 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=1125814 Bug ID: 1125814 Summary: [Build 20190125] YaST2 keyboard module applies settings even when Cancel button is pressed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: riafarov(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 797088 --> http://bugzilla.suse.com/attachment.cgi?id=797088&action=edit YaST logs ## Steps to reproduce: 1. Change X11 keyboard setting (e.g. run setxkbmap -layout us,ru) 2. Run yast2 keyboard module 3. English US is preselected 4. Press Cancel button 5. English US is set as a keyboard layout, so settings from step 1) are overwritten. Please, find logs in the attachment. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1046309] New: Popup title is not hidden in installation
by bugzilla_noreply＠novell.com 21 Sep '22

21 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=1046309 Bug ID: 1046309 Summary: Popup title is not hidden in installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://trello.com/c/jO8YkgSc OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jreidinger(a)suse.com QA Contact: jsrain(a)suse.com CC: dimstar(a)opensuse.org, fabian(a)ritter-vogt.de, fvogt(a)suse.com, jreidinger(a)suse.com, kossebau(a)kde.org, lnussel(a)suse.com, lslezak(a)suse.com, mkravec(a)suse.com, okurz(a)suse.com Depends on: 1037891 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1037891 +++ IMHO the regression is (see comment #36): * openSUSE Leap 42.1 had no title whatsoever for popups during installation (unless remote ssh install) * openSUSE Leap 42.3 has a title that is overly long and prone to touch the border of the window -> ugly and not adding information -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1012825] New: YaST2 hung "retrieving cracklib-dict-full.rpm extension" if rpm passed in DUD
by bugzilla_noreply＠novell.com 21 Sep '22

21 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=1012825 Bug ID: 1012825 Summary: YaST2 hung "retrieving cracklib-dict-full.rpm extension" if rpm passed in DUD Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: normand(a)linux.vnet.ibm.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 704263 --> http://bugzilla.suse.com/attachment.cgi?id=704263&action=edit installation_overview-y2logs.tar.bz2 YaST2 hung "retrieving cracklib-dict-full.rpm extension" while investigating bug https://bugzilla.suse.com/show_bug.cgi?id=1009472 I tried to pass a DUD=*dud containing the rpm*.rpm The consequence is that YaST2 hungs at "retrieving cracklib-dict-full.rpm extension" The y2log ends is stuck at Calling: extend, note that there is no /var/log/extend in reported tarball and no trace of extend in /var/log/linuxrc.log steps: === $mkdud -c /tmp/boo1009472.dud --install instsys --force -d 20161122 /tmp/powerpc-utils-1.3.2-9.ppc64le.rpm /tmp/rpm-4.12.0.1-0.ppc64le.rpm === /var/lib/openqa/script/client jobs post ISO=openSUSE-Tumbleweed-DVD-ppc64le-Snapshot20161122-Media.iso ARCH=ppc64le BUILD=20161122 DESKTOP=minimalx DISTRI=opensuse DVD=1 FLAVOR=DVD HDDSIZEGB=40 MACHINE=ppc64le-multipath MULTIPATH=1 OFW=1 QEMU=ppc64 QEMUCPU=host QEMUCPUS=8 QEMURAM=4096 QEMUTHREADS=8 TEST=install_minimalx VERSION=Tumbleweed Test=install_minimalx VGA=std WORKER_CLASS=qemu_ppc64le DUD=http://stade.lab.toulouse-stg.fr.ibm.com/~normand/boo1009472.dud === extract y2log install(8235) [Ruby] modules/InstExtensionImage.rb:386 Calling: extend 'cracklib-dict-full.rpm' === -- You are receiving this mail because: You are on the CC list for the bug.

2 17

[Bug 973590] New: weird layout of bootloader screen
by bugzilla_noreply＠novell.com 21 Sep '22

21 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=973590 Bug ID: 973590 Summary: weird layout of bootloader screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dmueller(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- While updating the openQA needle for openSUSE on AArch64 people noted that the "indentation" of the items in the ncurses ui looks slightly awkward. Is it intended that there is this huge empty space at the top left corner? -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 958483] New: 3rd party application UI is not behaving as required
by bugzilla_noreply＠novell.com 21 Sep '22

21 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=958483 Bug ID: 958483 Summary: 3rd party application UI is not behaving as required Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: tchvatal(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When using 3rd party module (like Virtualization) that tries to install additional packages it at this moment works like this when you are in X environment: For each package there is pop-up showing progress and then this pop-up is closed. This causes severe issue if user runs compoziting enabled environment. Imagine it like disco-bulb turning on and off as only on-top window is supposed to be rendered right and all the underlying windows are greyed out. More apps you install the more "funky" blinking you get. Prefferable solution would be to somehow include the yast2 sw_single interface that has the bottom progressbar and prints the installed packages. Added value would be mostly for openSUSE, where the default DE's have enabled compositing, but also for SLE case it would get at minimal prettier and at best more understandable about what is happening for the installed packages. For openSUSE it is quite commonly reported issue as I closed 3-4 during the bugzilla cleanup mentioning this problem. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1175779] New: Symlink /etc/systemd/system/tmp.mount cripples system
by bugzilla_noreply＠suse.com 21 Sep '22

21 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1175779 Bug ID: 1175779 Summary: Symlink /etc/systemd/system/tmp.mount cripples system Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: suseacc(a)johnzone.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After the dist-upgrade to 20200823, my system did not log in to the graphical environment (plasma). After reboot, it was worse. The root fs was mounted read only and some services did not start because of this. After some poking, I decided to roll back. The system came up and I dist-upgraded again. As Robert Munteanu hinted, there was a symlink from /etc/systemd/system/tmp.mount to /usr/share/systemd/tmp.mount which I deleted. The system rebooted normally this time. I checked the snapshots and did not find this symlink in the rw snapshot after the rollback, but in all previous until the one after the first upgrade to 20200823. I did comment out the /tmp entry in /etc/fstab as described in the wiki to migrate /tmp to tmpfs (https://en.opensuse.org/openSUSE:Tmp_on_tmpfs) and i wrote a service to create a symlink from /tmp/dumps to /dev/null to prevent steam from dumping gigabytes of logfiles there, effectively filling /tmp. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1154582] New: [Build 20191018] openQA test fails in shutdown: at-spi2 hangs
by bugzilla_noreply＠novell.com 19 Sep '22

19 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1154582 Bug ID: 1154582 Summary: [Build 20191018] openQA test fails in shutdown: at-spi2 hangs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1061840/modules/shut down/steps/10 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-NET-x86_64-otherDE_mate@64bit fails in [shutdown](https://openqa.opensuse.org/tests/1061840/modules/shutdown/steps/… ## Test suite description ## Reproducible Fails since (at least) Build [20191017](https://openqa.opensuse.org/tests/1059937) ## Expected result Last good: [20191016](https://openqa.opensuse.org/tests/1058657) (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 10

[Bug 1180987] New: RPMLINT: error out when a GPL package does not contain a valid %license
by bugzilla_noreply＠suse.com 18 Sep '22

18 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180987 Bug ID: 1180987 Summary: RPMLINT: error out when a GPL package does not contain a valid %license Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: giecrilj(a)stegny.2a.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- By the rules of GPL, every package built and distributed under that licence has to contain the text of the licence. Some packagers refuse to implement this rule on a case-by-case basis, indicating that an automatic check is required to do it correctly. Which is pretty much the case. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1154753] New: screen stays dark on boot unless I specify nouveau.modeset=0
by bugzilla_noreply＠novell.com 17 Sep '22

17 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1154753 Bug ID: 1154753 Summary: screen stays dark on boot unless I specify nouveau.modeset=0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: 64bit OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: estellnb(a)elstel.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kernel modesetting does not seem to work with 4.12.14-lp151.28.20-default. My screens (integrated+external) stay dark without nouveau.modeset=0. I have a dual boot option with Debian 9, kernel 4.20.0-rc4 and there it works well with nouveau.hdmimhz=225. Strange. I remember that always having worked without any additional parameter (4K only with hdmimhz). Would you believe it to be possible that this is caused by openSUSE kernel extensions? -- You are receiving this mail because: You are on the CC list for the bug.

2 3