April 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1183727] Shutdown hangs frequently in various places.
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183727 https://bugzilla.suse.com/show_bug.cgi?id=1183727#c5 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui(a)suse.com Flags| |needinfo?(jcarricksmith@gma | |il.com) --- Comment #5 from Franck Bui <fbui(a)suse.com> --- (In reply to John Carrick Smith from comment #0) > User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 > Firefox/78.0 > Build Identifier: > > When I shutdown my laptop (Novatech N1819 which is a re-badged Clevo > PB71DF1-G) the process will hang > 50% of the time. > > > > Reproducible: Sometimes > Which issue is the most reproducible on your side ? I think it's better if we focus on that one first. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184284] New: installation-images: /proc/sys/vm/local-oom-kill doesn't exist
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184284 Bug ID: 1184284 Summary: installation-images: /proc/sys/vm/local-oom-kill doesn't exist Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: snwint(a)suse.com Reporter: lnussel(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- data/root/etc/inst_setup has 20 # see bug 61535 21 [ -e /proc/sys/vm/local-oom-kill ] && echo 1 > /proc/sys/vm/local-oom-kill That doesn't exist anymore. Looks like it was a temporary downstream hack. Maybe /proc/sys/vm/panic_on_oom should be used instead so the system doesn't continue in half broken state -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1174166] New: Leap15.2 installed not detected by petitboot on PowerPC baremetal
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1174166 Bug ID: 1174166 Summary: Leap15.2 installed not detected by petitboot on PowerPC baremetal Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: normand(a)linux.vnet.ibm.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 839724 --> http://bugzilla.opensuse.org/attachment.cgi?id=839724&action=edit pb-discover.log Leap15.2 installed not detected by petitboot on PowerPC baremetal I did a Leap15.2 install on a Habanero PowerPC machine after successful install and reboot, petitboot failed as per pb-discover.log === extract diag/petitboot/pb-discover.log [11:49:32] Snapshot successfully created for sda2 [11:49:32] mounting device /dev/sda2 read-only [11:49:32] trying parsers for sda2 [11:49:32] parse error: 241('{'): syntax error, unexpected '{', expecting elif or else or fi === I am adding in attachment the pb-discover.log and will do also the grub.cfg may be a grub2 error generating the grub.cfg -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1181891] New: hardware:razer repo filelist.xml.gz cannot download
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181891 Bug ID: 1181891 Summary: hardware:razer repo filelist.xml.gz cannot download Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Fedora Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: josh(a)10leej.com QA Contact: adrian.schroeter(a)suse.com Found By: --- Blocker: --- sudo dnf up output hardware:razer (Fedora_33) 716 B/s | 1.9 kB 00:02 Errors during downloading metadata for repository 'hardware_razer': - Status code: 403 for http://espejito.fder.edu.uy/opensuse/repositories/hardware:/razer/Fedora_33… (IP: 190.64.49.124) - Status code: 403 for http://espejito.fder.edu.uy/opensuse/repositories/hardware:/razer/Fedora_33… (IP: 190.64.49.124) Error: Failed to download metadata for repo 'hardware_razer': Yum repo downloading error: Downloading error(s): repodata/7346ca1adc1c810a1910b1d6e241961ad0d4a5a5bda6ff09961f938a3d5444b5-primary.xml.gz - Cannot download, all mirrors were already tried without success; repodata/1363787f61ae70f58f9d9ada69af2f6fc87f5f6942cee8c91f6807e8f66a501f-filelists.xml.gz - Cannot download, all mirrors were already tried without success Ignoring repositories: hardware_razer Last metadata expiration check: 0:59:02 ago on Sat 06 Feb 2021 05:18:37 PM EST. Dependencies resolved. Nothing to do. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1184263] New: File permission detection fails for Tumbleweed running in Docker on Windows
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184263 Bug ID: 1184263 Summary: File permission detection fails for Tumbleweed running in Docker on Windows Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Windows 10 Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: kevin.napper(a)siemens.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Summary Shell tests for execute & read permissions don't return the correct results in containers constructed from the Tumbleweed image pulled from Docker Hub (https://hub.docker.com/r/opensuse/tumbleweed) when running in Docker Desktop on Windows 10. Expected Behaviour When run in sh or bash the following should report "yes": cd /bin; if [ -x pgrep ]; then echo "yes"; else echo "no"; fi Actual Behaviour "no" is reported Further information * -r also results in "no" but -f results in "yes". * This has operated correctly in the past. We first noticed the problem on 23rd March 2021 and the problem has persisted although the Tumbleweed image on Docker Hub has been updated since. * This has been reproduced by different individuals on different Windows 10 machines. * The problem doesn't appear to be present when the Docker image is run on Linux (Opensuse Tumbleweed). * The problem doesn't appear to be present in Leap. * The problem isn't present in a Docker image based on on older Tumbleweed (about a month or so old) probably indicating that the problem isn't caused by change to Windows or Docker Desktop. * I also posted on the forum (https://forums.opensuse.org/showthread.php/551912-File-permission-detection…) but have had no response. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1184243] [Build 117.13] yast online updates fails at no update repositories being present
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184243 https://bugzilla.suse.com/show_bug.cgi?id=1184243#c3 Ladislav Slez�k <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #3 from Ladislav Slez�k <lslezak(a)suse.com> --- `Product.short_name` reads that from /etc/os-release: NAME="openSUSE Leap" So that is different than the expected "openSUSE". Anyway, the problem should go away once there is an update available: https://github.com/yast/yast-online-update/blob/1b3d032d40505120b9d0a97159c… Currently there is no update in http://download.opensuse.org/update/leap/15.3/oss/ I'll fix that for 15.4 and I think it does not make much sense to fix it for 15.3, once a patch is available the error will be gone... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184266] [Staging] toolbox fails with cgroupsv2 enabled
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184266 https://bugzilla.suse.com/show_bug.cgi?id=1184266#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kukuk(a)suse.com Assignee|kukuk(a)suse.com |jalausuch(a)suse.com --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- Sounds like toolbox is started by a user for which no systemd login session exists. Maybe runuser does not create such one? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183726] VUL-0: CVE-2021-28089,CVE-2021-28090: tor: New releases (with security fixes): 0.3.5.14, 0.4.4.8, and 0.4.5.7
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183726 https://bugzilla.suse.com/show_bug.cgi?id=1183726#c7 --- Comment #7 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1183726) was mentioned in https://build.opensuse.org/request/show/882519 Backports:SLE-15-SP3 / tor -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184261] New: VUL-0: CVE-2021-28090: tor: allow an attacker to remotely crash the authority with an assertion failure
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184261 Bug ID: 1184261 Summary: VUL-0: CVE-2021-28090: tor: allow an attacker to remotely crash the authority with an assertion failure Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/279896/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: bwiedemann(a)suse.com Reporter: rfrohl(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- rh#1940639 A flaw was found in Tor in appending detached signatures to a pending consensus document that could be used to crash a directory authority because of an assertion failure. This bug is also tracked as TROVE-2021-002. References: https://gitlab.torproject.org/tpo/core/tor/-/issues/40316 https://blog.torproject.org/node/2009 References: https://bugzilla.redhat.com/show_bug.cgi?id=1940639 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-28090 http://www.debian.org/security/-1/dsa-4871 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-28090 https://blog.torproject.org/node/2009 https://bugs.torproject.org/tpo/core/tor/40316 https://gitlab.torproject.org/tpo/core/tor/-/issues/40316 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1183726] New: VUL-0: CVE-2021-28089,CVE-2021-28090: tor: New releases (with security fixes): 0.3.5.14, 0.4.4.8, and 0.4.5.7
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183726 Bug ID: 1183726 Summary: VUL-0: CVE-2021-28089,CVE-2021-28090: tor: New releases (with security fixes): 0.3.5.14, 0.4.4.8, and 0.4.5.7 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: bwiedemann(a)suse.com Reporter: rfrohl(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We have a new stable release today. If you build Tor from source, you can download the source code for 0.4.5.7 on the download page. Packages should be available within the next several weeks, with a new Tor Browser coming next week. Also today, Tor 0.3.5.14 (changelog) and Tor 0.4.4.8 (changelog) have also been released; you can find them (and source for older Tor releases) at https://dist.torproject.org. -- Major bugfixes (security, denial of service): Disable the dump_desc() function that we used to dump unparseable information to disk. It was called incorrectly in several places, in a way that could lead to excessive CPU usage. Fixes bug 40286; bugfix on 0.2.2.1-alpha. This bug is also tracked as TROVE-2021- 001 and CVE-2021-28089. Fix a bug in appending detached signatures to a pending consensus document that could be used to crash a directory authority. Fixes bug 40316; bugfix on 0.2.2.6-alpha. Tracked as TROVE-2021-002 and CVE-2021-28090. -- https://blog.torproject.org/node/2009 -- You are receiving this mail because: You are on the CC list for the bug.

1 2