February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1021271] New: KDE session are not visible in who / last output
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1021271 Bug ID: 1021271 Summary: KDE session are not visible in who / last output Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Holm.Schubert(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Users running a KDE (Plasma 5) session are not visible in the output of "who" or "last". Same problem for IceWM session on a KDE installed system. Only open consoles (within the KDE session or in a text terminal) are listed by who/last. In a GNOME installation of 42.2 the error doesn't occur. The error was observed for the first time in Leap 42.1, persists in 42.2 and Tumbleweed but does not exist in openSUSE 13.2. Steps to reproduce: Login user A to a KDE session but do not open any console in this session. Switch to text terminal and login as user B. Check for running session of user A (who / last A). -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 997052] New: when console is rotated splash screen is not
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=997052 Bug ID: 997052 Summary: when console is rotated splash screen is not Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I boot with GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/system/swap splash=silent quiet showopts console fbcon=rotate:3" This can be detected by parsing the commandline or examining /sys/class/graphics/fbcon/rotate (3) and /sys/class/graphics/fb0/rotate (0) which should be more reliable should the console get rotated automagically by some other script. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1026093] New: tuned: activating throughput-performance profile exposes python syntax error
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1026093 Bug ID: 1026093 Summary: tuned: activating throughput-performance profile exposes python syntax error Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: hguo(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following python syntax error was captured when attempting to activate throughput-performance profile: 2017-02-20 10:50:47,277 INFO tuned.profiles.loader: loading profile: throughput-performance 2017-02-20 10:50:47,280 INFO tuned.daemon.daemon: starting tuning 2017-02-20 10:50:47,283 INFO tuned.plugins.base: instance disk: assigning devices sda, sdb 2017-02-20 10:50:47,285 ERROR tuned.units.manager: failed to initialize plugin cpu 2017-02-20 10:50:47,285 ERROR tuned.units.manager: invalid syntax (plugin_cpu.py, line 235) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/tuned/units/manager.py", line 45, in create plugin = self._plugins_repository.create(plugin_name) File "/usr/lib/python2.7/site-packages/tuned/plugins/repository.py", line 32, in create plugin_cls = self.load_plugin(plugin_name) File "/usr/lib/python2.7/site-packages/tuned/utils/plugin_loader.py", line 28, in load_plugin return self._get_class(module_name) File "/usr/lib/python2.7/site-packages/tuned/utils/plugin_loader.py", line 32, in _get_class module = __import__(module_name) File "/usr/lib/python2.7/site-packages/tuned/plugins/plugin_cpu.py", line 235 else: ^ SyntaxError: invalid syntax Please investigate. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1024931] New: lib for unpacking tar archives makes errors
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1024931 Bug ID: 1024931 Summary: lib for unpacking tar archives makes errors Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dieter.jurzitza(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 713789 --> http://bugzilla.suse.com/attachment.cgi?id=713789&action=edit Erratic results looking into an archive with mc I stumbled across an error that is hard for me to assign. I installed a tar based backup system at my sisters site. Now I told her to use midnight commander if she wanted to extract certain files from this archive. She tried this and got strange results. Please take a look on attachement (1) Fehler - MidnightCommander.jpg. The directory contents "original" is shown on the left pane, the erratic content (i.E. what midnight commander reads from the archive is shown on the right pane). Please note that the archive (a file) is ok, I can flawlessly extract whatever I want using "tar", and I tested this several times. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1009742] New: YaST crashes when choosing not to install bootcode onto /
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1009742 Bug ID: 1009742 Summary: YaST crashes when choosing not to install bootcode onto / Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: fabian(a)ritter-vogt.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- During inst_proposal, when clicking onto 'Install bootcode onto "/" partition (do not install)', yast shows an error dialog about an "Invalid option boot". I tested this with the RC2 DVD, so it might have been fixed meanwhile. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1006832] New: miscellaneous -> "system log" tries to open non-existent /var/log/messages
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1006832 Bug ID: 1006832 Summary: miscellaneous -> "system log" tries to open non-existent /var/log/messages Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Yast module "System log" points to non-existent /var/log/messages supposedly fixed for 13.2 in bug 900830 However, the fix is to install one of two extra packages neither of which gets pre-installed. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1001133] New: VUL-1: CVE-2016-7511: libdwarf: Integer Overflow
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1001133 Bug ID: 1001133 Summary: VUL-1: CVE-2016-7511: libdwarf: Integer Overflow Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: dmueller(a)suse.com Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Security Response Team Blocker: --- https://www.prevanders.net/libdwarf-20160923.tar.gz bugxml/data.txt id: DW201609-002 cve: CVE-2016-7511 datereported: 20160918 reportedby: Shi Ji (@Puzzor) vulnerability: libdwarf 20160613 Integer Overflow product: libdwarf description: In dwarf_get_size_of_val() with fuzzed DWARF data we get a SEGV. <pre> See https://sourceforge.net/p/libdwarf/bugs/3/ </pre> <pre> ==6825== ERROR: AddressSanitizer: SEGV on unknown address 0x0583903c (pc 0xb61f1a98 sp 0xbfa388b4 bp 0xbfa38d08 T0) AddressSanitizer can not provide additional info. #1 0xb61e3c0b (/usr/lib/i386-linux-gnu/libasan.so.0+0xdc0b) #2 0x80a21b1 in _dwarf_get_size_of_val /home/fuzzing/fuzzing/dwarf-20160613/libdwarf/dwarf_util.c:210 #3 0x8054214 in _dwarf_next_die_info_ptr /home/fuzzing/fuzzing/dwarf-20160613/libdwarf/dwarf_die_deliv.c:1340 #4 0x80557a5 in dwarf_child /home/fuzzing/fuzzing/dwarf-20160613/libdwarf/dwarf_die_deliv.c:1640 #5 0x804b23f in get_die_and_siblings /home/fuzzing/fuzzing/dwarf-20160613/dwarfexample/./simplereader.c:573 </pre> _dwarf_make_CU_Context() is insufficiently cautious about the length of a CU being absurd. Unclear as yet if this is the problem but it is a problem and is fixed for next release. datefixed: references: regressiontests/DW201609-002/DW201609-002-poc gitfixid: 3767305debcba8bd7e1c483ae48c509d25399252 tarrelease: endrec: References: https://www.prevanders.net/dwarf.html#releases -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1001132] New: VUL-1: CVE-2016-7510: libdwarf: Out-of-bounds read in read_line_table_program
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1001132 Bug ID: 1001132 Summary: VUL-1: CVE-2016-7510: libdwarf: Out-of-bounds read in read_line_table_program Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: dmueller(a)suse.com Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Security Response Team Blocker: --- https://www.prevanders.net/libdwarf-20160923.tar.gz bugxml/data.txt id: DW201609-003 cve: CVE-2016-7410 datereported: 20160913 reportedby: https://marc.info/?l=oss-security&m=147391785920048&w=2 vulnerability: libdwarf 20160613 heap-buffer-overflow product: libdwarf description: With AddressSanitizer, we found a Heap-Buffer-overflow in the latest release version of dwarfdump. The crash output is as follows: <pre> See also: https://marc.info/?l=oss-security&m=147378394815872&w=2 The testcase poc is from this web page. </pre> <pre> ==17411==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xf3808904 at pc 0x80a6f76 bp 0xffb95e78 sp 0xffb95a5c READ of size 4 at 0xf3808904 thread T0 ==17411==WARNING: Trying to symbolize code, but external symbolizer is not initialized! #0 0x80a6f75 in __interceptor_memcpy ??:? #1 0x8426c3b in _dwarf_read_loc_section /home/starlab/fuzzing/dwarf-20160613/libdwarf/./dwarf_loc.c:919 #2 0x84250e2 in _dwarf_get_loclist_count /home/starlab/fuzzing/dwarf-20160613/libdwarf/./dwarf_loc.c:970 #3 0x8438826 in dwarf_get_loclist_c /home/starlab/fuzzing/dwarf-20160613/libdwarf/./dwarf_loc2.c:551 #4 0x81a1be8 in get_location_list /home/starlab/fuzzing/dwarf-20160613/dwarfdump/print_die.c:3523 #5 0x816e1a2 in print_attribute </pre> _dwarf_get_loclist_header_start() is not cautious about values in the header being absurdly large. Unclear as yet if this is the problem but it is a potential problem (fixed for next release). <pre> Address Sanitizer in gcc reproduces the report. In _dwarf_read_loc_section() the simple calculation of loc_section_end was wrong, so end-of section was incorrect for the local reads. With that fixed we get DW_DLE_READ_LITTLEENDIAN_ERROR when libdwarf attempts to read off end of section. id: DW201609-003 cve: CVE-2016-7410 datereported: 20160913 reportedby: https://marc.info/?l=oss-security&m=147391785920048&w=2 vulnerability: libdwarf 20160613 heap-buffer-overflow product: libdwarf description: With AddressSanitizer, we found a Heap-Buffer-overflow in the latest release version of dwarfdump. The crash output is as follows: <pre> See also: https://marc.info/?l=oss-security&m=147378394815872&w=2 The testcase poc is from this web page. </pre> <pre> ==17411==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xf3808904 at pc 0x80a6f76 bp 0xffb95e78 sp 0xffb95a5c READ of size 4 at 0xf3808904 thread T0 ==17411==WARNING: Trying to symbolize code, but external symbolizer is not initialized! #0 0x80a6f75 in __interceptor_memcpy ??:? #1 0x8426c3b in _dwarf_read_loc_section /home/starlab/fuzzing/dwarf-20160613/libdwarf/./dwarf_loc.c:919 #2 0x84250e2 in _dwarf_get_loclist_count /home/starlab/fuzzing/dwarf-20160613/libdwarf/./dwarf_loc.c:970 #3 0x8438826 in dwarf_get_loclist_c /home/starlab/fuzzing/dwarf-20160613/libdwarf/./dwarf_loc2.c:551 #4 0x81a1be8 in get_location_list /home/starlab/fuzzing/dwarf-20160613/dwarfdump/print_die.c:3523 #5 0x816e1a2 in print_attribute </pre> _dwarf_get_loclist_header_start() is not cautious about values in the header being absurdly large. Unclear as yet if this is the problem but it is a potential problem (fixed for next release). <pre> Address Sanitizer in gcc reproduces the report. In _dwarf_read_loc_section() the simple calculation of loc_section_end was wrong, so end-of section was incorrect for the local reads. With that fixed we get DW_DLE_READ_LITTLEENDIAN_ERROR when libdwarf attempts to read off end of section. </pre> datefixed: references: regressiontests/DW201609-003/poc gitfixid: 3767305debcba8bd7e1c483ae48c509d25399252 tarrelease: endrec: References: https://www.prevanders.net/dwarf.html#releases https://bugzilla.redhat.com/show_bug.cgi?id=1378718 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-7510 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 995367] New: Leap 42.2 ppc64le net install failure linuxrc or bad repo
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=995367 Bug ID: 995367 Summary: Leap 42.2 ppc64le net install failure linuxrc or bad repo Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: PowerPC-64 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 689327 --> http://bugzilla.suse.com/attachment.cgi?id=689327&action=edit abanc_net_install_leap42_2_failure.log Leap 42.2 ppc64le net install failure linuxrc or bad repo I tried install of Leap 42.2 ppc64le using the net iso Build0112 from (1) Using the default setup, linuxrc is failing with "Please make sure your installation medium is available" as per (2) the failing repo is (3) Looking at the linuxrc.log the failure is a missing repo/content file. If I choose ...repo/oss in place of .../repo then the failure reported in linuxrc.log is a missing repo/oss/config I do not know from those data if the problem is a bad repo or an error in linuxrc (1) http://download.opensuse.org/ports/ppc/distribution/leap/42.2-Current/iso/ (2) linuxrc reporting bad installation medium === ... ending DHCP request to eth3... ok, ip = 9.101.18.90/24 Please make sure your installation medium is available. Choose the URL to retry. 0) <-- Back <-- 1) ftp://9.101.18.1/pub/linux/opensuse/42.2/ppc64le/os/ 2) http://download.opensuse.org/ports/ppc/distribution/leap/42.2/r 3) Enter another URL > === (3) http://download.opensuse.org/ports/ppc/distribution/leap/42.2/repo === -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 991850] New: YaST2 > Software Manager tries to access skipped remository
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=991850 Bug ID: 991850 Summary: YaST2 > Software Manager tries to access skipped remository Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Sometimes some custom repositories are not available. Then YaST2 Software manager is reading */repodata/repomd.xml for long time and fails, and ask user what to do; if user selects to Skip this repository, YaST2 still will try to access this repository (at stage of creating/updating catch for accesible repositories)! And YaST2 will again ask in same dialog what to do! I suppose, that YaST2 must remember, that used skipped repository, and not to try access it again. Tested and reproducible in openSUSE 13.2 and Leap 42.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 8