May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1171535] Include stix2 in texlive
by bugzilla_noreply＠suse.com 14 May '20

14 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1171535 http://bugzilla.suse.com/show_bug.cgi?id=1171535#c2 --- Comment #2 from Seymour Metz <smetz3(a)gmu.edu> --- Any chance that texlive 2020 will be in the LEAP 15.2 stable repository? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171582] vagrant 2.2.7 doesn't work after last update
by bugzilla_noreply＠suse.com 14 May '20

14 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171582 Marcus Rückert <mrueckert(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrueckert(a)suse.com Assignee|ruby-devel(a)suse.de |dcermak(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1153931] ghc-bootstrap fails to build for Leap 15.2 for armv7
by bugzilla_noreply＠suse.com 14 May '20

14 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1153931 http://bugzilla.suse.com/show_bug.cgi?id=1153931#c3 --- Comment #3 from Ondřej Súkup <mimi.vx(a)gmail.com> --- (In reply to Guillaume GARDET from comment #2) > @Ondrej, any ETA? > > If there are some documented steps somewhere on how to do it, I could help. Oh.. originally ghc and ghc-bootstrap were in Peter Trommler care.. But unfortunately he stepped out of the project And now we are in Egg-Chicken problem + bonus is llvm :( for binaries needed for ghc bootsrap Peter had special project and package -> https://build.opensuse.org/package/show/devel:languages:haskell:bootstrap/g… used only for non x86 architectures .. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171667] New: Spelling Mistake in yast-control (sigle disk)
by bugzilla_noreply＠suse.com 14 May '20

14 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171667 Bug ID: 1171667 Summary: Spelling Mistake in yast-control (sigle disk) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: ada.lovelace(a)gmx.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 Build Identifier: I did not find the special file on Github. Therefore, I have created this bug. You have the following content in yast-control: SUSE Manager Server (sigle disk) I believe that should be a "single" disk. That is a spelling mistake. Reproducible: Always Actual Results: SUSE Manager Server (sigle disk) Expected Results: SUSE Manager Server (single disk) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171666] New: Can't load coretemp module / CPU temp monitoring is not working on 5.3.18-lp152.14-default (used to work on kernel-default-5.3.18-lp152.11.3)
by bugzilla_noreply＠suse.com 14 May '20

14 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171666 Bug ID: 1171666 Summary: Can't load coretemp module / CPU temp monitoring is not working on 5.3.18-lp152.14-default (used to work on kernel-default-5.3.18-lp152.11.3) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: miikka.veijonen(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- CPU temperature monitoring is not working anymore after I upgraded from kernel-default-5.3.18-lp152.11.3 to kernel 5.3.18-lp152.14-default. If I reboot back to old kernel the temperatures are showing up properly by using "sensors" program. This could be related: I'm unable to load coretemp or x86_pkg_temp_thermal on kernel 5.3.18-lp152.14-default: xxx:~ # modprobe coretemp modprobe: ERROR: could not insert 'coretemp': No such device xxx:~ # modprobe x86_pkg_temp_thermal modprobe: ERROR: could not insert 'x86_pkg_temp_thermal': No such device I tried to upgrade my kernel manually to 5.6.11-1-default from Tumbleweed and there coretemp and x86_pkg_temp_thermal modules are loaded automatically during system startup and CPU temperature monitoring is working (I can see the values by using sensors). PC: Lenovo Thinkpad X270 CPU: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171271] VUL-0: CVE-2020-12672: GraphicsMagick: heap-based buffer overflow in ReadMNGImage in coders/png.c.
by bugzilla_noreply＠suse.com 14 May '20

14 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1171271 http://bugzilla.suse.com/show_bug.cgi?id=1171271#c2 --- Comment #2 from Petr Gajdos <pgajdos(a)suse.com> --- I have sent a mail to upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171563] AUDIT-0: pam: new pam module pam_setquota.so
by bugzilla_noreply＠suse.com 14 May '20

14 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1171563 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|security-team(a)suse.de |matthias.gerstner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1165702] Yast installer stores device id in crypttab vs fstab uuid breaking encryption as id's are different in live system
by bugzilla_noreply＠suse.com 14 May '20

14 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1165702 http://bugzilla.suse.com/show_bug.cgi?id=1165702#c9 --- Comment #9 from Steffen Winterfeldt <snwint(a)suse.com> --- The fix is for Tumbleweed only, no backport to Leap 15.1 planned. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171341] New: texlive-kpathsea-bin rpm output with wrong permissions
by bugzilla_noreply＠novell.com 14 May '20

14 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171341 Bug ID: 1171341 Summary: texlive-kpathsea-bin rpm output with wrong permissions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: marina.latini(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, this is the additional rpm output while installing the package update: ----------------- Installing: texlive-kpathsea-bin-2019.20190407.svn50281-68.4.x86_64 ..........................................................................................................................................................................[done] Additional rpm output: setting /usr/lib/mktex/public to root:mktex 2755. (wrong permissions 0755) ----------------- Information for package texlive-kpathsea-bin: --------------------------------------------- Repository : Main Repository (OSS) Name : texlive-kpathsea-bin Version : 2019.20190407.svn50281-68.4 Arch : x86_64 Vendor : openSUSE Installed Size : 112.5 KiB Installed : Yes Status : up-to-date Source package : texlive-2019.20190407-68.4.src Summary : Binary files of kpathsea Description : Binary files of kpathsea System info: ------------ NAME="openSUSE Tumbleweed" VERSION_ID="20200501" ------------ -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1165702] Yast installer stores device id in crypttab vs fstab uuid breaking encryption as id's are different in live system
by bugzilla_noreply＠suse.com 14 May '20

14 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1165702 http://bugzilla.suse.com/show_bug.cgi?id=1165702#c8 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #8 from Steffen Winterfeldt <snwint(a)suse.com> --- fix: https://github.com/yast/yast-storage-ng/pull/1095 -- You are receiving this mail because: You are on the CC list for the bug.

1 0