September 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1176044] Repository mess when upgrading
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1176044 https://bugzilla.suse.com/show_bug.cgi?id=1176044#c2 --- Comment #2 from Stefan Hundhammer <shundhammer(a)suse.com> --- In the YaST "Repositories" module, you see the URL of each repo. You might have to scroll a little to the right, but that URL contains the distro version. That's how an advanced user who adds those repos in the first place is supposed to see where the repo belongs to. When you use the zypper command line, you can add "--url" to see the URL: sudo zypper lr --url -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1174075] Changing %{_libexecdir} breaks some packages which are misusing the macro
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1174075 https://bugzilla.suse.com/show_bug.cgi?id=1174075#c25 --- Comment #25 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1174075) was mentioned in https://build.opensuse.org/request/show/831373 Factory / btrfsmaintenance -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173115] kernel updates lead to showing mok screen on reboot
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1173115 https://bugzilla.suse.com/show_bug.cgi?id=1173115#c22 --- Comment #22 from Gary Ching-Pang Lin <glin(a)suse.com> --- I found that PTF key is also signed by SLE CA, so the "ignore-ca-check" patch would ignore PTF key and make PTF kmp unloadable :( -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175926] [Software Manager] Keep UI in sync with repo autorefresh
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175926 https://bugzilla.suse.com/show_bug.cgi?id=1175926#c4 --- Comment #4 from David Diaz <dgonzalez(a)suse.com> --- (In reply to macias - from comment #3) > Packman is just popular repo, "Packman is down" is the same as saying > "Packman is offline" or "Packman server does not respond", something like > this. I don't know the exact reason. I knew about Packman ;) But I wanted to clarify the "is down" part because the error shown in my screenshot in that situation. > > As for your screenshot -- it is OK, but you taken it too late :-). > :) > I.e. you > taken it when Yast2 already _stopped_ because repository is not available. During my tests, this alert was prompted quite fast. That's the reason why I didn't understand your suggestion. > > And I am talking (sorry I was not clear about that) about _progress_ -- when > Yast still struggles/tries to reach the repo. > > The moment Yast is done with repo X and goes to repo Y it should switch > progress to "Y 0%". Currently it is not the case, it finishes with X with "X > 100%" (ok), then switches to work with Y with progress still "X 100%" (not > ok), it struggles because Y is down, and then you see the outcome as > presented in the screenshot (I mean the progress bar in the background, not > the error popup). So the visual switch with progress happens, but it should > be sooner. IMHO. I see. Let's wait for the Ladislav thoughts until go ahead processing the bug report. Thanks a lot, Macias. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176042] New: System won't boot (error: symbol 'grub_file_filters' not found.)
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1176042 Bug ID: 1176042 Summary: System won't boot (error: symbol 'grub_file_filters' not found.) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Similar as bug 1175045, this happened after upgrading Leap 15.1 to Leap 15.2 using the "zypper dup" method: GRUB enters rescue mode because of "error: symbol 'grub_file_filters' not found.". Once being able to boot (using the "super_gub2_disk_hybrid_2.02s10.iso" rescue CD this time), using "yast2 bootloader" and just applying the settings suggested fixed the problem. (Rebuilding the kernel via dracut did not fix the problem) I'm afraid the typical user will be quite unhappy if the system stops to boot... -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1176041] New: SCA update packages are corrupted
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1176041 Bug ID: 1176041 Summary: SCA update packages are corrupted Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: ralph.roth(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- zypper up fails since last week because of bad SCA packages. # zypper lr -u| grep -i sca 1 | SCA_Tool | SCA_Tool | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/Novell:/NTS:/Unstable/openSUSE_Fa… # zypper up Loading repository data... Reading installed packages... The following 27 package updates will NOT be installed: conky gstreamer-plugins-bad-lang gstreamer-plugins-ugly gstreamer-plugins-ugly-lang libavcodec58 libavdevice58 libavfilter7 libavformat58 libavresample4 libavutil56 libgstadaptivedemux-1_0-0 libgstbadaudio-1_0-0 libgstbadbase-1_0-0 libgstbadvideo-1_0-0 libgstbasecamerabinsrc-1_0-0 libgstcodecparsers-1_0-0 libgstgl-1_0-0 libgstmpegts-1_0-0 libgstphotography-1_0-0 libgsturidownloader-1_0-0 libgstwayland-1_0-0 libpostproc55 libquicktime0 libswresample3 libswscale5 supportutils youtube-dl-bash-completion The following 11 packages are going to be upgraded: sca-patterns-base sca-patterns-edir sca-patterns-filr sca-patterns-hae sca-patterns-oes sca-patterns-sle10 sca-patterns-sle11 sca-patterns-sle12 sca-patterns-sle15 sca-patterns-suma sca-server-report 11 packages to upgrade. Overall download size: 0 B. Already cached: 1.2 MiB. No additional space will be used or freed after the operation. Continue? [y/n/v/...? shows all options] (y): In cache sca-patterns-base-1.3-61.8.noarch.rpm (1/11), 71.1 KiB (324.9 KiB unpacked) In cache sca-server-report-1.0-14.7.noarch.rpm (2/11), 26.7 KiB ( 64.4 KiB unpacked) In cache sca-patterns-suma-1.0-20.8.noarch.rpm (3/11), 20.1 KiB ( 99.2 KiB unpacked) In cache sca-patterns-sle15-1.0-12.5.noarch.rpm (4/11), 18.9 KiB ( 68.0 KiB unpacked) In cache sca-patterns-sle12-1.0-199.5.noarch.rpm (5/11), 398.0 KiB ( 4.1 MiB unpacked) In cache sca-patterns-sle11-1.3-192.6.noarch.rpm (6/11), 365.3 KiB ( 3.7 MiB unpacked) In cache sca-patterns-sle10-1.3-77.8.noarch.rpm (7/11), 190.7 KiB ( 1.9 MiB unpacked) In cache sca-patterns-oes-1.3-37.8.noarch.rpm (8/11), 83.5 KiB (474.0 KiB unpacked) In cache sca-patterns-hae-1.3-21.8.noarch.rpm (9/11), 29.3 KiB (177.3 KiB unpacked) In cache sca-patterns-filr-1.3-15.8.noarch.rpm (10/11), 11.7 KiB ( 18.4 KiB unpacked) In cache sca-patterns-edir-1.3-18.8.noarch.rpm (11/11), 25.3 KiB ( 82.0 KiB unpacked) Checking for file conflicts: .............................................................................................[done] ( 1/11) Installing: sca-patterns-base-1.3-61.8.noarch ...................................................................[error] Installation of sca-patterns-base-1.3-61.8.noarch failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed: cpio: Bad magic error: sca-patterns-base-1.3-61.8.noarch: install failed error: sca-patterns-base-1.3-61.7.noarch: erase skipped Abort, retry, ignore? [a/r/i] (a): a Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint. # zypper in sca-patterns-sle15 The following package is going to be upgraded: sca-patterns-sle15 1 package to upgrade. Overall download size: 0 B. Already cached: 18.9 KiB. No additional space will be used or freed after the operation. Continue? [y/n/v/...? shows all options] (y): In cache sca-patterns-sle15-1.0-12.5.noarch.rpm (1/1), 18.9 KiB ( 68.0 KiB unpacked) Checking for file conflicts: .............................................................................................[done] (1/1) Installing: sca-patterns-sle15-1.0-12.5.noarch ....................................................................[error] Installation of sca-patterns-sle15-1.0-12.5.noarch failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed: cpio: Bad magic error: sca-patterns-sle15-1.0-12.5.noarch: install failed error: sca-patterns-sle15-1.0-12.4.noarch: erase skipped Abort, retry, ignore? [a/r/i] (a): Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint. p5520:~ # zypper in sca-server-report Loading repository data... Reading installed packages... Resolving package dependencies... The following package is going to be upgraded: sca-server-report 1 package to upgrade. Overall download size: 0 B. Already cached: 26.7 KiB. No additional space will be used or freed after the operation. Continue? [y/n/v/...? shows all options] (y): In cache sca-server-report-1.0-14.7.noarch.rpm (1/1), 26.7 KiB ( 64.4 KiB unpacked) Checking for file conflicts: .............................................................................................[done] (1/1) Installing: sca-server-report-1.0-14.7.noarch .....................................................................[error] Installation of sca-server-report-1.0-14.7.noarch failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed: cpio: Bad magic error: sca-server-report-1.0-14.7.noarch: install failed error: sca-server-report-1.0-14.6.noarch: erase skipped Abort, retry, ignore? [a/r/i] (a): -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1174720] unable to load german console keymap - loadkeys dies with syntax error (fix known)
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1174720 Jiří Suchomel <jsuchome(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka(a)suse.com Flags|needinfo?(jsuchome(a)suse.com |needinfo?(locilka(a)suse.com) |) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1174720] unable to load german console keymap - loadkeys dies with syntax error (fix known)
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1174720 https://bugzilla.suse.com/show_bug.cgi?id=1174720#c3 Stanislav Brabec <sbrabec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsuchome(a)suse.com Flags| |needinfo?(jsuchome(a)suse.com | |) --- Comment #3 from Stanislav Brabec <sbrabec(a)suse.com> --- It makes sense to do some migration steps. But the problem is more complex. YaST slowly migrated from the legacy charmaps to xkb-derived keymaps. It is needed to migrate keymaps to a completely different maps. Jiří: Do you know what is the current status of yast migration to xkb-derived console (kbd) keymaps? Does the distro upgrade process cover some way of migration of kbd keymaps from legacy to new ones? (If yes, the reported problem appears only in Tumbleweed.) Regarding the comment 0: Yes, it makes sense to fix it or upgrade. Regarding the comment 2: As long as the symlink is a directory, rpm does not care about it. But if there is a migration from a directory to a symlink, rpm can badly fail. (It can remove seemingly obsolete files that are installed with a different path.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175625] hwclock: settimeofday() failed
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175625 https://bugzilla.suse.com/show_bug.cgi?id=1175625#c1 Stanislav Brabec <sbrabec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kasimir_(a)outlook.de Flags| |needinfo?(kasimir_@outlook. | |de) --- Comment #1 from Stanislav Brabec <sbrabec(a)suse.com> --- It was never reported before. Could you reproduce it? Every time? Could you try LC_ALL=C hwclock --hctosys --verbose And actually, could you provide output of strace? LC_ALL=C strace -f -o hwclock.strace hwclock --hctosys --verbose > I get this error message > > hwclock: settimeofday () failed: Invalid argument Is the string exact? The message I suspect should be: hwclock: settimeofday() failed i. e. no spaces before "()" -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175006] VUL-1: libmaxminddb: use of uninitialized memory leading to heap-buffer-overflow in mmdblookup
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175006 https://bugzilla.suse.com/show_bug.cgi?id=1175006#c3 --- Comment #3 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2020:2440-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1175006 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Server for SAP 15 (src): libmaxminddb-1.4.3-1.6.1 SUSE Linux Enterprise Server 15-LTSS (src): libmaxminddb-1.4.3-1.6.1 SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): libmaxminddb-1.4.3-1.6.1 SUSE Linux Enterprise Module for Basesystem 15-SP1 (src): libmaxminddb-1.4.3-1.6.1 SUSE Linux Enterprise High Performance Computing 15-LTSS (src): libmaxminddb-1.4.3-1.6.1 SUSE Linux Enterprise High Performance Computing 15-ESPOS (src): libmaxminddb-1.4.3-1.6.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0