January 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1180493] MultiOS Flatpak Installation
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180493 https://bugzilla.suse.com/show_bug.cgi?id=1180493#c9 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ancor(a)suse.com) | --- Comment #9 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- In my opinion, the openSUSE installer should recommend or even automate setups that are considered a good practice or that are common for many users. That doesn't seem to be the case here, although I can see the benefit of the particular setup used by the author of this feature request, it doesn't seem to be an widespread practice. It's relatively easy to add an extra mount point (either for a new partition/LV or for reusing an existing one) using the Expert Partitioner. And, in my opinion, that's good enough for custom setups like this one. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1125470] [TRACK] solved by FETCHER / MEDIABACKEND enhancement
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1125470 http://bugzilla.opensuse.org/show_bug.cgi?id=1125470#c6 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |claudius.ellsel(a)live.de --- Comment #6 from Michael Andres <ma(a)suse.com> --- *** Bug 1180617 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180408] Installation fails on aarch64 in openQA since snapshot 20201224
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180408 https://bugzilla.suse.com/show_bug.cgi?id=1180408#c7 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Steffen Winterfeldt <snwint(a)suse.com> --- I've merged the pr from comment 4. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1045901] strongswan 5.3.5: No connection possible!
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1045901 https://bugzilla.suse.com/show_bug.cgi?id=1045901#c9 --- Comment #9 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Manuel Buil from comment #8) > Hey, I have inherited strongswan as Madhu left the company. I see that this > bug did not have any activity for years and it refers to an old version of > strongswan, can we close it? Thanks Thx for asking, but for me the problem has been solved. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1169874] [Build 20200417] Failure to boot due to resume=/dev/disk/by-path
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1169874 https://bugzilla.suse.com/show_bug.cgi?id=1169874#c29 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fvogt(a)suse.com) | --- Comment #29 from Fabian Vogt <fvogt(a)suse.com> --- Created attachment 844914 --> https://bugzilla.suse.com/attachment.cgi?id=844914&action=edit YaST logs (patched Kernel.rb, still no resume=) I patched Kernel.propose_hibernation? to log "prop hiber" on entry and "returning true" on exit, and only the entry is logged: 2021-01-07 05:50:26 <2> g149(9912) [Ruby] modules/Kernel.rb(propose_hibernation?):559 prop hiber 2021-01-07 05:50:26 <1> g149(9912) [Ruby] proposal/space_maker.rb(block in provide_space):84 No need to find a fit for this partition, it will reuse /dev/vda3: #<Y2Storage::Planned::Partition mount_point=swap, reuse_name=/dev/vda3, reuse_sid=46, min_size=0 B, max_size=2 GiB, disk=nil, max_start_offset=nil, subvolumes=[]> I did another try with also patching out the product features condition and then resume= appeared in the cmdline. Using /dev/disk/by-uuid/, so this bug is confirmed fixed! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180662] VUL-1: CVE-2020-35904: rust: An issue was discovered in the crossbeam-channel crate before 0.4.4 for Rust. It has incorrect expectations about the relationship between the memory allocation and how many iterator elements there are.
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180662 Maintenance Robot <maint-coord+maintenance_robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180662] New: VUL-1: CVE-2020-35904: rust: An issue was discovered in the crossbeam-channel crate before 0.4.4 for Rust. It has incorrect expectations about the relationship between the memory allocation and how many iterator elements there are.
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180662 Bug ID: 1180662 Summary: VUL-1: CVE-2020-35904: rust: An issue was discovered in the crossbeam-channel crate before 0.4.4 for Rust. It has incorrect expectations about the relationship between the memory allocation and how many iterator elements there are. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other URL: https://smash.suse.de/issue/274390/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: federico(a)suse.com Reporter: atoptsoglou(a)suse.com QA Contact: security-team(a)suse.de CC: ngompa13(a)gmail.com Found By: Security Response Team Blocker: --- CVE-2020-35904 An issue was discovered in the crossbeam-channel crate before 0.4.4 for Rust. It has incorrect expectations about the relationship between the memory allocation and how many iterator elements there are. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35904 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-35904 https://rustsec.org/advisories/RUSTSEC-2020-0052.html -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1178489] Enchant 2 Voikko backend does not work in eg gspell
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1178489 Timo Jyrinki <tjyrinki(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1178489] Enchant 2 Voikko backend does not work in eg gspell
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1178489 https://bugzilla.suse.com/show_bug.cgi?id=1178489#c7 --- Comment #7 from Timo Jyrinki <tjyrinki(a)suse.com> --- Bug fixed in SLE 15SP2&SP3, openSUSE Tumbleweed and openSUSE Leap 15.3. Leap 15.2 fix now new and waiting at https://build.opensuse.org/request/show/860353 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180317] New: [Build 20201222] vnxmanager uninstallable after boost update
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180317 Bug ID: 1180317 Summary: [Build 20201222] vnxmanager uninstallable after boost update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1523287/modules/yast 2_vnc/steps/16 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: gfx-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ncurses@64bit fails in [yast2_vnc](https://openqa.opensuse.org/tests/1523287/modules/yast2_vnc/step… openSUSE:Factory/vncmanager failed to build against the new boost version ## Test suite descriptionn Maintainer: qsf-y 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 [20201222](https://openqa.opensuse.org/tests/1522983) ## Expected result Last good: [20201221](https://openqa.opensuse.org/tests/1521430) (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 5