September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1190810] New: zypper dup failure on package openmpi4-config with snapshot 20210920
by bugzilla_noreply＠suse.com 23 Sep '21

23 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190810 Bug ID: 1190810 Summary: zypper dup failure on package openmpi4-config with snapshot 20210920 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm getting this, trying to zypper dup to snapshot 20210920: Problem: the to be installed python38-mpi4py-3.0.3-3.1.x86_64 requires 'openmpi4-config', but this requirement cannot be provided not installable providers: openmpi4-config-4.1.1-1.3.i586[http-download.opensuse.org-ade0eb17] openmpi4-config-4.1.1-1.3.x86_64[http-download.opensuse.org-ade0eb17] openmpi4-config-4.1.1-1.3.i586[repo-oss] openmpi4-config-4.1.1-1.3.x86_64[repo-oss] Solution 1: deinstallation of openmpi2-config-2.1.6-11.2.x86_64 Solution 2: deinstallation of python38-mpi4py-3.0.3-2.6.x86_64 Solution 3: keep obsolete python38-mpi4py-3.0.3-2.6.x86_64 Solution 4: break python38-mpi4py-3.0.3-3.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c): d Problem: the to be installed python38-mpi4py-3.0.3-3.1.x86_64 requires 'openmpi4-config', but this requirement cannot be provided not installable providers: openmpi4-config-4.1.1-1.3.i586[http-download.opensuse.org-ade0eb17] openmpi4-config-4.1.1-1.3.x86_64[http-download.opensuse.org-ade0eb17] openmpi4-config-4.1.1-1.3.i586[repo-oss] openmpi4-config-4.1.1-1.3.x86_64[repo-oss] Detailed information: the to be installed python38-mpi4py-3.0.3-3.1.x86_64 requires 'openmpi4-config', but this requirement cannot be provided the to be installed openmpi2-config-2.1.6-11.3.x86_64 conflicts with 'namespace:otherproviders(openmpi-runtime-config)' provided by the to be installed openmpi4-config-4.1.1-1.3.x86_64 the to be installed openmpi4-config-4.1.1-1.3.x86_64 conflicts with 'namespace:otherproviders(openmpi-runtime-config)' provided by the to be installed openmpi2-config-2.1.6-11.3.x86_64 the installed python38-mpi4py-3.0.3-2.6.x86_64 does not belong to a distupgrade repository and must be replaced the to be installed python38-mpi4py-3.0.3-3.1.i586 has inferior architecture the to be installed openmpi4-config-4.1.1-1.3.i586 has inferior architecture the installed openmpi2-config-2.1.6-11.2.x86_64 does not belong to a distupgrade repository and must be replaced the to be installed openmpi2-config-2.1.6-11.3.i586 has inferior architecture Solution 1: deinstallation of openmpi2-config-2.1.6-11.2.x86_64 Solution 2: deinstallation of python38-mpi4py-3.0.3-2.6.x86_64 Solution 3: keep obsolete python38-mpi4py-3.0.3-2.6.x86_64 Solution 4: break python38-mpi4py-3.0.3-3.1.x86_64 by ignoring some of its dependencies -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1190762] [Build 20210920] gd: support for gd2 images disabled
by bugzilla_noreply＠suse.com 23 Sep '21

23 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190762 https://bugzilla.suse.com/show_bug.cgi?id=1190762#c4 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(felix.niederwange | |r(a)suse.com) --- Comment #4 from Petr Gajdos <pgajdos(a)suse.com> --- I would follow upstream and remove the gd/gd2 support for now, if this is not much work for openQA guys, as this is more future proof attitude. For PHP code: <?php // Load the gd image $im = @imagecreatefromgd('./test.gd'); // Test if the image was loaded if(!$im) { die('Unable to load gd image!'); } // Do image operations here // Save the image imagegd($im, './test_updated.gd'); imagedestroy($im); ?> I get: :/ # php test.php Unable to load gd image!:/ # when php is built against current 2.3.3 as in Factory. Might be that the GD/GD2 support will be requested to be added back temporarily, though. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186458] VUL-0: chromium: multiple security issues fixed in 91.0.4472.77
by bugzilla_noreply＠suse.com 23 Sep '21

23 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1186458 https://bugzilla.suse.com/show_bug.cgi?id=1186458#c9 --- Comment #9 from Alexander Bergmann <abergmann(a)suse.com> --- The following CVE was added to this Chrome release: [$NA][916326] Medium CVE-2021-30558: Insufficient policy enforcement in content security policy. Reported by Jun Kokatsu, Microsoft Browser Vulnerability Research on 2018-12-19 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190740] Race condition when linking to LLVM on s390x
by bugzilla_noreply＠suse.com 23 Sep '21

23 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190740 http://bugzilla.opensuse.org/show_bug.cgi?id=1190740#c9 --- Comment #9 from Reinhard Max <max(a)suse.com> --- (In reply to Sarah Kriesch from comment #6) > PostgreSQL11 has got no constraints file in OBS at the moment. We can adapt > it if we know the correct requirements (same as SLE). None of the PostgreSQL packages on openSUSE or SLE has a constraints file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190330] gpk-update-viewer doesn't list all available updates
by bugzilla_noreply＠suse.com 23 Sep '21

23 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190330 https://bugzilla.suse.com/show_bug.cgi?id=1190330#c15 Jonathan Kang <songchuan.kang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED Assignee|gnome-bugs(a)suse.de |songchuan.kang(a)suse.com --- Comment #15 from Jonathan Kang <songchuan.kang(a)suse.com> --- FIXED. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190272] Most volumes gets unmounted after boot
by bugzilla_noreply＠suse.com 23 Sep '21

23 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190272 https://bugzilla.suse.com/show_bug.cgi?id=1190272#c11 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|systemd-maintainers(a)suse.de |mchang(a)suse.com --- Comment #11 from Franck Bui <fbui(a)suse.com> --- Michael, I'm reassigning this bug to you in order to make sure that grub2-once.service is changed to use a condition check on all relevant distros. Once done could you re-assign it back to systemd-maintainers so I'll mark this bug as a duplicate of bsc#1137373 ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190272] Most volumes gets unmounted after boot
by bugzilla_noreply＠suse.com 23 Sep '21

23 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190272 https://bugzilla.suse.com/show_bug.cgi?id=1190272#c9 --- Comment #9 from Franck Bui <fbui(a)suse.com> --- (In reply to Michael Chang from comment #7) > (In reply to Franck Bui from comment #6) > > Michael, do you think we could add the '--no-reload' option ? > > We could. But as long as this has been fixed in openSUSE Tumbleweed > differently in a way that disabling systemd service during boot up is not > required, we may have to follow the fix in bsc#1169460. Indeed using a condition in grub2-once.service seems better. > Agree. We could fix this is in grub via maintenance update of bsc#1169460. Yes please, also please note that all supported distros (such as SLE12-SP5, Leap) relying on grub2-once.service would need the change. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190802] pam-deprecated removed but pam_cracklib not removed from config
by bugzilla_noreply＠suse.com 23 Sep '21

23 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190802 https://bugzilla.suse.com/show_bug.cgi?id=1190802#c2 --- Comment #2 from Thorsten Kukuk <kukuk(a)suse.com> --- Hm, you seem to have blocked the migration to pam_pwquality for nearly half a year and wondering, that this results in a failure when the deprecated package get's removed? If you use options like "no-recommends" or not the official base patterns, you are responsible of your own for a flawless migration. If you use "recommends" and the official base patterns, your system should have been migrated about half an year ago. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190272] Most volumes gets unmounted after boot
by bugzilla_noreply＠suse.com 23 Sep '21

23 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190272 https://bugzilla.suse.com/show_bug.cgi?id=1190272#c7 --- Comment #7 from Michael Chang <mchang(a)suse.com> --- (In reply to Franck Bui from comment #6) > Michael, do you think we could add the '--no-reload' option ? We could. But as long as this has been fixed in openSUSE Tumbleweed differently in a way that disabling systemd service during boot up is not required, we may have to follow the fix in bsc#1169460. > > I think the disablement of grub2-once.service is only relevant for the next > reboot, right ? Yes, the idea is that this service only gets started to cleanup the boot once flag on next reboot, then disabling itself ... > > I know it would be a workaround for bsc#1137373 but in that case adding > '--no-reload' shouldn't hurt and would avoid the reloading of PID1 > configuration which is a relatively costly operation, which is a good thing. Agree. We could fix this is in grub via maintenance update of bsc#1169460. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1063638] New: btrfs balance renders system unresponsive and eventually even kills WiFi when quota is enabled - review I/O scheduling parameters of btrfsmaintenance
by bugzilla_noreply＠novell.com 23 Sep '21

23 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1063638 Bug ID: 1063638 Summary: btrfs balance renders system unresponsive and eventually even kills WiFi when quota is enabled - review I/O scheduling parameters of btrfsmaintenance Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de CC: Antoine.Saroufim(a)gmail.com, aschnell(a)suse.com, auxsvr(a)gmail.com, dmitry(a)roshchin.org, dsterba(a)suse.com, ecsos(a)schirra.net, enadolski(a)suse.com, fcrozat(a)suse.com, fliu(a)suse.com, friedhelm.stappert(a)web.de, guenther(a)mpanrw.de, gweberbh(a)gmail.com, hannsj_uhl(a)de.ibm.com, harald.achitz(a)gmail.com, ingo.goeppert+suse(a)mailbox.org, jeffm(a)suse.com, kdejaeger(a)gmail.com, lnussel(a)suse.com, lpechacek(a)suse.com, ndcunliffe(a)gmail.com, okurz(a)suse.com, ortsacs(a)yahoo.es, rgoldwyn(a)suse.com, richard(a)nod.at, ronisbr(a)gmail.com, slindomansilla(a)suse.com, suse(a)bugs.jan.ritzerfeld.org, sven.heithecker(a)web.de, t.rother(a)netzwissen.de, tneo(a)gmx.com, ulrich.hobelmann+suse(a)gmail.com Depends on: 1017461 Found By: --- Blocker: --- ## Observation +++ This bug was initially created as a clone of Bug #1017461 +++ The first part of fixes have been done in bug 1017461 but it seems the btrfs maintenance tasks can still have a significant impact on system responsiveness. Running the btrfs maintenance jobs, e.g. * /etc/cron.monthly/btrfs-scrub * /etc/cron.weekly/btrfs-balance * /etc/cron.weekly/btrfs-trim can make the clock with seconds displayed stop for some seconds or the mouse cursor to get stuck for seconds ## Reproducible * Somehow cause lot of "dirty" data that needs balancing/scrubbing * Run the cron jobs * Observe the system responsiveness is hindered ## Expected result Interactive use of a machine should not be impacted ## Suggestion It looks like /usr/share/btrfsmaintenance/btrfs-scrub.sh checks for the variable "$BTRFS_SCRUB_PRIORITY" equalling "normal" from /etc/sysconfig/btrfsmaintenance but this is set to "idle" for me in the config file which causes that no I/O scheduling parameters are forwarded to the call of scrub at all which does not seem to make sense to me. Should it set `-c 3` for idle or `-c 2 -n 7` for best-effort prio 7 instead? -- You are receiving this mail because: You are on the CC list for the bug.

2 109