March 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1177544] New: `bless` hex editor not launching - libglade-2_0-0 missing
by bugzilla_noreply＠suse.com 02 Mar '21

02 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1177544 Bug ID: 1177544 Summary: `bless` hex editor not launching - libglade-2_0-0 missing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: eimantas(a)remote.solutions QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ``` $ bless Unhandled Exception: System.TypeInitializationException: The type initializer for 'Glade.XML' threw an exception. ---> System.DllNotFoundException: libglade-2.0.so.0 assembly:<unknown assembly> type:<unknown type> member:(null) at (wrapper managed-to-native) Glade.XML.glade_xml_get_type() at Glade.XML..cctor () [0x00000] in <4ad1c956e6b8461daac4e25c580fa347>:0 --- End of inner exception stack trace --- at BlessMain..ctor (System.String[] args) [0x0002d] in <0060470b4ad341d89a1ca9087e81e5a4>:0 at BlessMain.Main (System.String[] args) [0x00000] in <0060470b4ad341d89a1ca9087e81e5a4>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'Glade.XML' threw an exception. ---> System.DllNotFoundException: libglade-2.0.so.0 assembly:<unknown assembly> type:<unknown type> member:(null) at (wrapper managed-to-native) Glade.XML.glade_xml_get_type() at Glade.XML..cctor () [0x00000] in <4ad1c956e6b8461daac4e25c580fa347>:0 --- End of inner exception stack trace --- at BlessMain..ctor (System.String[] args) [0x0002d] in <0060470b4ad341d89a1ca9087e81e5a4>:0 at BlessMain.Main (System.String[] args) [0x00000] in <0060470b4ad341d89a1ca9087e81e5a4>:0 ``` somehow the necessary dependency `libglade-2_0-0` doesn't get installed automatically -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1182850] Create homedirectories with stricter permissions
by bugzilla_noreply＠suse.com 02 Mar '21

02 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182850 https://bugzilla.suse.com/show_bug.cgi?id=1182850#c6 --- Comment #6 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Johannes Segitz from comment #5) > The expectation is that without any changes by the user the home directories > should be created with mode 700. So if YaST already takes this from the > configuration file then we probably only need to change it (which then > wouldn't be your task). Upstream did NOT change the default! Please look at the from you quoted jiras. Upstream did add an option which allows to change the mode of the home directory, nothing more, nothing less. It's by default disabled. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1090572] New: VUL-0: CVE-2018-1110: CVE-2018-1110: Knot Resolver <= 2.2.0 Improper Input Validation
by bugzilla_noreply＠novell.com 02 Mar '21

02 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1090572 Bug ID: 1090572 Summary: VUL-0: CVE-2018-1110: CVE-2018-1110: Knot Resolver <= 2.2.0 Improper Input Validation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/204731/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: i(a)marguerite.su Reporter: kbabioch(a)suse.com QA Contact: security-team(a)suse.de CC: detlef(a)die-mafia.de, mrueckert(a)suse.com, pascal.bleser(a)opensuse.org Found By: Security Response Team Blocker: --- CVE-2018-1110 Hello, Knot Resolver software version <= 2.2.0 suffers from Improper Input Validation bugs which allow remote attacker to crash the resolver by sending specially crafted packets. Fixes ===== Knot Resolver 2.3.0 fixes all known security bugs and is available from https://www.knot-resolver.cz/download/ Backports ========= To fix the bugs we had to do major changes to some data structures so backport it most likely not feasible. We are discontinuing support for *all* versions older than 2.3.0 and discourage attempts to backport fixes because these will most likely introduce additional bugs. CVE request data ================ Fixed version: Knot Resolver 2.3.0 Vulnerability type: CWE-20: Improper Input Validation Affected component: resolver Impact of exploitation: Program crashes. Description of vulnerability: Improper input validation bugs in DNS resolver component of Knot Resolver (up to and including version 2.2.0) allow remote attacker who can create malformed packets to cause denial of service. Attack Vector (AV): Network Attack Complexity (AC): Low Privileges Required (PR): None User Interaction (UI): None Scope (S): Unchanged Confidentiality (C): None Integrity (I): Low Availability (A): High Technical Details: CWE-20 CWE-476 CWE-626 Acknowledgment: CZ.NIC would like to thank Toshifumi Sakaguchi and Vicky Shrestha for their responsible reporting of security vulnerabilities. -- Petr Špaček @ CZ.NIC References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1110 http://seclists.org/oss-sec/2018/q2/63 -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1158393] VUL-0: CVE-2019-19331: knot: Denial of service through high CPU utilization
by bugzilla_noreply＠suse.com 02 Mar '21

02 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1158393 http://bugzilla.opensuse.org/show_bug.cgi?id=1158393#c6 Michal Hrusecky <michal.hrusecky(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #6 from Michal Hrusecky <michal.hrusecky(a)opensuse.org> --- Affects Knot Resolver, while we have Knot Authoritative Server in distribution. Although they are named confusingly similar, it is different software. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[opensuse-bugs] [Bug 1179003] New: [Build 20201119] seahorse: unlock keyring seems not to have a reaction
by bugzilla_noreply＠suse.com 02 Mar '21

02 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1179003 Bug ID: 1179003 Summary: [Build 20201119] seahorse: unlock keyring seems not to have a reaction Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1478922/modules/seah orse/steps/11 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_gnome@64bit fails in [seahorse](https://openqa.opensuse.org/tests/1478922/modules/seahorse/steps/… ## Test suite description Maintainer: asmorodskyi, okurz. Extra tests which were designed to run on gnome ## Reproducible Fails since (at least) Build [20201109](https://openqa.opensuse.org/tests/1466090) ## Expected result Last good: [20201108](https://openqa.opensuse.org/tests/1465483) (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 3

[Bug 1182850] Create homedirectories with stricter permissions
by bugzilla_noreply＠suse.com 02 Mar '21

02 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182850 https://bugzilla.suse.com/show_bug.cgi?id=1182850#c5 Johannes Segitz <jsegitz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers(a)suse.de |mvetter(a)suse.com Flags|needinfo?(jsegitz(a)suse.com) | --- Comment #5 from Johannes Segitz <jsegitz(a)suse.com> --- (In reply to Lukas Ocilka from comment #4) The expectation is that without any changes by the user the home directories should be created with mode 700. So if YaST already takes this from the configuration file then we probably only need to change it (which then wouldn't be your task). Assigning to the maintainer of shadow -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182888] New: perf: Fix jump parsing for C++ code
by bugzilla_noreply＠suse.com 02 Mar '21

02 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182888 Bug ID: 1182888 Summary: perf: Fix jump parsing for C++ code Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: jslaby(a)suse.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mliska(a)suse.cz Found By: --- Blocker: --- Considering the following testcase: int foo(int a, int b) { for (unsigned i = 0; i < 1000000000; i++) a += b; return a; } int main() { foo (3, 4); return 0; } perf annotate displays: 86.52 ��40055e: �� ja 40056c <foo(int, int)+0x26> 13.37 ��400560: mov -0x18(%rbp),%eax ��400563: add %eax,-0x14(%rbp) ��400566: addl $0x1,-0x4(%rbp) 0.11 ��40056a: �� jmp 400557 <foo(int, int)+0x11> ��40056c: mov -0x14(%rbp),%eax ��40056f: pop %rbp and the 'ja 40056c' does not link to the location in the function. It's caused by fact that comma is wrongly parsed, it's part of function signature. With my patch I see: 86.52 �� ja 26 13.37 �� mov -0x18(%rbp),%eax �� add %eax,-0x14(%rbp) �� addl $0x1,-0x4(%rbp) 0.11 �� jmp 11 ��26:��mov -0x14(%rbp),%eax and 'o' output prints: 86.52 ��4005�� ja 40056c <foo(int, int)+0x26> 13.37 ��4005��0: mov -0x18(%rbp),%eax ��4005��3: add %eax,-0x14(%rbp) ��4005��6: addl $0x1,-0x4(%rbp) 0.11 ��4005��a: �� jmp 400557 <foo(int, int)+0x11> ��4005�� mov -0x14(%rbp),%eax On the contrary, compiling the very same file with gcc -x c, the parsing is fine because function arguments are not displyed: jmp 400543 <foo+0x1d> -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1180610] New: perf does not load symbols from libantlr4
by bugzilla_noreply＠suse.com 02 Mar '21

02 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1180610 Bug ID: 1180610 Summary: perf does not load symbols from libantlr4 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mliska(a)suse.cz Found By: --- Blocker: --- 1) install libantlr4-runtime-devel and perf. 2) 3) cat > main.cpp <<EOF #include <cstdio> #include <antlr4-runtime.h> int main() { for (int a = 0; a < 10000000; a++) antlr4::ANTLRInputStream input("/dev/null"); } EOF 4) cat > Makefile <<EOF CXXFLAGS=-g -Wall -I/usr/include/antlr4-runtime -Wno-attributes -mfentry LDLIBS=-lantlr4-runtime all: main EOF 5) make && perf record -g ./main 6) perf report -g 7) symbols of antlr library are shown in hexa (not resolved), despite debuginfo is installed Perf fails here: https://github.com/torvalds/linux/blob/9f1abbe97c08ba7ed609791627533a805a1b… It walks through all symbols in .symtab of: /usr/lib/debug/usr/lib64/libantlr4-runtime.so.4.8-4.8-1.4.x86_64.debug and resolves the symbol addresses into names there. First, it obtains the section a symbol is in -- sym.st_shndx (like 13th for .text, 25th for .data, ...) from: /usr/lib64/libantlr4-runtime.so.4.8 (i.e. not the .debug). And then it uses the section header to eliminate ASLR. But there are also symbols like these: 10305: 0000000000955fa4 0 NOTYPE LOCAL DEFAULT 29 Predicate.cpp.2bc410e7 There is no section 29 in libantlr4-runtime.so.4.8, it's only in libantlr4-runtime.so.4.8-4.8-1.4.x86_64.debug (it's .debuginfo there). Now, I don't know whose bug is this. Is it perf or the dwarf separator in rpm? BTW are the section numbers supposed to be the same in both elfs? -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1182847] samba has too many hard dependencies
by bugzilla_noreply＠suse.com 02 Mar '21

02 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182847 Felix Miata (offline until ???) <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda(a)earthlink.net -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1096241] [opensuse][tumbleweed][20180603][liveCD/rescue] Shutdown takes too much time when lvmetad doesn't respond to SIGKILL
by bugzilla_noreply＠suse.com 02 Mar '21

02 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1096241 https://bugzilla.suse.com/show_bug.cgi?id=1096241#c50 --- Comment #50 from Oliver Kurz <okurz(a)suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: kde-live@uefi-2G https://openqa.opensuse.org/tests/1650119 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0