March 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1127602] VUL-0: CVE-2019-5786: chromium: Use-after-free in FileReader
by bugzilla_noreply＠novell.com 02 Mar '19

02 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1127602 http://bugzilla.suse.com/show_bug.cgi?id=1127602#c1 --- Comment #1 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1127602) was mentioned in https://build.opensuse.org/request/show/680828 15.0 / chromium https://build.opensuse.org/request/show/680831 42.3 / chromium https://build.opensuse.org/request/show/680833 Factory / chromium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1123784] New: xkeyboard-config: evdev keys KEY_RFKILL and KEY_WWAN are not currently mapped
by bugzilla_noreply＠novell.com 02 Mar '19

02 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1123784 Bug ID: 1123784 Summary: xkeyboard-config: evdev keys KEY_RFKILL and KEY_WWAN are not currently mapped Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: sndirsch(a)suse.com Reporter: sebastian.parschauer(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- I have a brand new Dell Inspiron 13 7380 laptop. The rfkill key is handled by the dell_laptop driver and that one emits keycode 247 (KEY_RFKILL). But KEY_RFKILL is not mapped in xkeyboard-config. I've found and tested the upstream bug and patch: > https://bugs.freedesktop.org/show_bug.cgi?id=100970 > https://patchwork.freedesktop.org/patch/155965/ This is working with that patch. I applied the changes from the patch manually and followed some instructions to make the change effective: > rm -rf /var/lib/xkb/* > shutdown -r now HW test report: > https://en.opensuse.org/HCL:Dell_laptops#Inspiron_7xxx HW details: > https://www.dell.com/en-us/work/shop/dell-laptops-and-notebooks/new-inspiro… Please apply that patch to openSUSE Leap 15.0 as well. TIA -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1033770] liblapacke3: undefined references
by bugzilla_noreply＠novell.com 02 Mar '19

02 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1033770 http://bugzilla.suse.com/show_bug.cgi?id=1033770#c5 --- Comment #5 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2019:0288-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1033770 CVE References: Sources used: openSUSE Leap 42.3 (src): lapack-3.5.0-12.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127602] New: VUL-0: CVE-2019-5786: chromium: Use-after-free in FileReader
by bugzilla_noreply＠novell.com 02 Mar '19

02 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1127602 Bug ID: 1127602 Summary: VUL-0: CVE-2019-5786: chromium: Use-after-free in FileReader Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: tchvatal(a)suse.com Reporter: Andreas.Stieger(a)gmx.de QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- https://chromereleases.googleblog.com/2019/03/stable-channel-update-for-des… Fixed in Chromium 72.0.3626.121: CVE-2019-5786: Use-after-free in FileReader https://crbug.com/936448 https://chromium.googlesource.com/chromium/src/+/150407e8d3610ff25a45c7c468… https://chromium.googlesource.com/chromium/src/+/ba9748e78ec7e9c0d594e7edf7… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127564] gcc bug in double calculation in i586
by bugzilla_noreply＠novell.com 02 Mar '19

02 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1127564 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |rguenther(a)suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127447] Warning: Repository 'openSUSE-42.3-Up-Non-Oss' appears to be outdated. Consider using a different mirror or server
by bugzilla_noreply＠novell.com 02 Mar '19

02 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1127447 http://bugzilla.suse.com/show_bug.cgi?id=1127447#c3 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Marcus Meissner <meissner(a)suse.com> --- i released an opera update to the channels yesterday, the warning should be gone again now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127596] New: [doc] 6.5.5 Configuring the KDC
by bugzilla_noreply＠novell.com 02 Mar '19

02 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1127596 Bug ID: 1127596 Summary: [doc] 6.5.5 Configuring the KDC Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation Assignee: fs(a)suse.com Reporter: elliott.scott(a)scottsolutions.us QA Contact: fs(a)suse.com Found By: --- Blocker: --- 6.5.5 Configuring the KDC https://doc.opensuse.org/documentation/leap/security/html/book.security/cha… Under the section, "2. Adjust the configuration files..." it would be extremely beneficial to be more specific in discussing what adjustments should be made, e.g. establishing the default_realm = <YOUR.REALM> under the [libdefaults] section. I had to figure this out by referring to a post: https://github.com/crazyadmins/useful-scripts/issues/1 where the author points out the default_realm setting doesn't exist, preventing the installation from proceeding. This happens in openSUSE Leap 15 as well without this value established. I was banging my head against a wall for a while before I stumbled upon it. I still don't know what modifications I should make to the kdc.conf file before starting the YaST2 installation/configuration. Please advise. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127465] VUL-0: CVE-2019-2031: matio: NULL pointer dereference in function Mat_VarFree() in mat.c
by bugzilla_noreply＠novell.com 01 Mar '19

01 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1127465 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1125841] New: AppArmor security driver not enabled for QEMU in libvirt
by bugzilla_noreply＠novell.com 01 Mar '19

01 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1125841 Bug ID: 1125841 Summary: AppArmor security driver not enabled for QEMU in libvirt Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: supercoolemail(a)seznam.cz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.109 Safari/537.36 Build Identifier: Setting security_driver = "apparmor" in /etc/libvirt/qemu.conf or enabling apparmor individually per domain leads to error with libvirt 5: Security driver apparmor not enabled Reproducible: Always Steps to Reproduce: 1. Set apparmor as security driver in /etc/libvirt/qemu.conf . 2. Use libvirt to start QEMU domain. Actual Results: Error: Security driver apparmor not enabled Failed to initialize security drivers Initialization of QEMU state driver failed: internal error: Failed to initialize security drivers Expected Results: Domain would start and be confined by AppArmor as it used to be before libvirt 5. -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1127586] New: Please split libijs into its own package (for cups-filters)
by bugzilla_noreply＠novell.com 01 Mar '19

01 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1127586 Bug ID: 1127586 Summary: Please split libijs into its own package (for cups-filters) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Enhancement Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: cfeck(a)kde.org QA Contact: jsmeix(a)suse.com Found By: --- Blocker: --- Please split "libijs" into its own package. Rationale: Long I had the impression I needed ghostscript to be able to print (to my non-PostScript) printer. But checking dependencies, I see that cups-filters only needs libijs-0.35.so from the ghostscript package. If my analysis is correct, libijs does not have any dependencies besides glibc. I found no reference to calling a ghostscript binary either. In other words, I could remove the dinosaur ghostscript package, if that library was in a separate package. Recent discussions about security of ghostscript suggests that it isn't a wanted package either. -- You are receiving this mail because: You are on the CC list for the bug.

1 0