December 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 990956] New: Missing categories in brp-check-suse (brp-30-desktop)
by bugzilla_noreply＠novell.com 26 Jul '19

26 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=990956 Bug ID: 990956 Summary: Missing categories in brp-check-suse (brp-30-desktop) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: luizluca(a)tre-sc.jus.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I was writing a RPM file which packs a .desktop file. I used the categogy "Utility;TelephonyTools;" and OBS gave me: 'ERROR: No sufficient Category definition:' I checked the file /usr/lib/rpm/brp-desktop.data/applications.menu and it seems to be outdated when I compare with https://specifications.freedesktop.org/menu-spec/menu-spec-1.0.html or https://cgit.freedesktop.org/xdg/xdg-specs/tree/menu/menu-spec.xml. Even OpenSUSE suggests TelephonyTools category at https://en.opensuse.org/openSUSE:Packaging_desktop_menu_categories So, something is not updated. Either all the checked sources or brp-check-suse. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1008493] New: YaST2 tftp-server configuration shows error for reading the log
by bugzilla_noreply＠novell.com 17 Jul '19

17 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1008493 Bug ID: 1008493 Summary: YaST2 tftp-server configuration shows error for reading the log Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: zluo(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 700651 --> http://bugzilla.suse.com/attachment.cgi?id=700651&action=edit yast logs (tftp server) run test case yas2_tftp. I got error for error occurred while reading the log. compare with sles 12 sp2 gmc (SLE-12-SP2-Server-DVD-ppc64le-Build2192) there is no error message pops up even at stage of initial configuration before any logs created. Please check logs and screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1009432] New: openSUSE:Tools/osc-plugin-install: Bug
by bugzilla_noreply＠novell.com 16 Jul '19

16 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1009432 Bug ID: 1009432 Summary: openSUSE:Tools/osc-plugin-install: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: ro(a)suse.com Reporter: a.malik.michael(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Hi, every time i try to use "osc in" i get the following error Traceback (most recent call last): File "/usr/bin/osc", line 41, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 61, in run return prg.main(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 343, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 366, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 500, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1230, in _dispatch_cmd return handler(argv[0], opts, *args) File "/var/lib/osc-plugins/osc-install.py", line 305, in do_install arch_words = self._read_system_name(etc_S_r, opts) File "/var/lib/osc-plugins/osc-install.py", line 559, in _read_system_name text = open(file).read() IOError: [Errno 2] No such file or directory: '/etc/SuSE-release' when i checked /etc/, i could not find SUSE-release. I am not sure if this would help but, i could fine os-release which contained the following NAME="openSUSE Tumbleweed" # VERSION="20161108" ID=opensuse ID_LIKE="suse" VERSION_ID="20161108" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20161108" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 954556] New: After upgrading from 13.2 to Leap 42.1, Mercurial chokes on files locally deleted and ignored, but changed on the remote
by bugzilla_noreply＠novell.com 12 Jul '19

12 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=954556 Bug ID: 954556 Summary: After upgrading from 13.2 to Leap 42.1, Mercurial chokes on files locally deleted and ignored, but changed on the remote Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 URL: http://users.skynet.be/antoine.mechelynck/vim/vim-tony mec.bundle.bz2 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: antoine.mechelynck(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm not sure if this bug is in the correct Component. It concerns a difference between the Mercurial versions for openSUSE 13.2 and openSUSE Leap 42.1. I'll describe below the problems I had (in a Mercurial repository with local changes) after upgrading to Leap 42.1, and how I solved them (probably not ideally), in the hope that something can be found to make life easier to anyone else running into the same (or a sufficiently similar) problem. FWIW I've uploaded at http://users.skynet.be/antoine.mechelynck/vim/vim-tonymec.bundle.bz2 a full bundle of my local Vim repository, including a clone of the Mercurial mirror at https://bitbucket.org/vim-mirror/vim with local changes. The bundle is 8.8 MiB for a repository occupying about 151 MiB so I didn't attach it to this bug. The tip before I upgraded to Leap 42.1 was the merge commit about 30 changesets from the present tip. The earlier changesets (0 to 7225) are probably not as interesting but I didn't know how else to let you look at it from my point of view. It might be possible to inspect the bundle without unpacking it, by declaring it as a "repository" by means of the -R argument to Mercurial. This past weekend I upgraded to Leap 42.1 and a few hours ago "hg in" displayed 27 new changesets. I tried to "fetch" them but instead of saying "remote changed runtime/doc/tags which local deleted" and asking me if I wanted to download the changes or keep deleted, Mercurial errored out with the new changesets applied, the "old" merge still current, no new merge done, and a message saying that it could not proceed because of a locally ignored file changed on the remote (the deleted file in question). I goofed around some, updated (not easily) to 0 and back to tip, including a couple of manual merges for which Mercurial invoked vimdiff as my preferred merge tool, and finally added one monstrous changeset by hg addremove followed by hg commit. Those "added" files are IIUC files ignored by my locally modified .hgignore on the other unnamed branch. After that I could finally merge my local changes with the monstrous changeset I had just added on top of Bram's official tip. After that I notice that "hg diff" on the locally deleted file does not give the same output as it used to before the upgrade to Leap. Previously it showed a diff between the remote version of the file and /dev/null, which was longish and looked messy, but, well, I used to think that was the way of things, at least with that version of Mercurial. Now it just says: diff --git a/runtime/doc/tags b/runtime/doc/tags deleted file mode 100644 which I find much neater even if it is not visually reversible. I am practically certain that what I did was not the "ideal" thing to do, but it is the best I could find to work around this change of behaviour and still get a working directory tree with which I could compile Bram's version with my local changes (which consist of one feature added and one disabled in src/feature.h, plus .hgignore lines for runtime/doc/tags which is regenerated by "make install" anyway, and for some directories and files not present on the remote, e.g. "shadow" directories allowing me to compile a Huge and a Tiny build in parallel from the same source with different config settings passed as environment variables). I hope Mercurial won't choke again the next time new changesets are added at the remote and I try to apply them. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[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 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