August 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1143125] systemd-vconsole-setup.service succeeds and fails several times on each boot
by bugzilla_noreply＠novell.com 01 Aug '19

01 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=1143125 http://bugzilla.suse.com/show_bug.cgi?id=1143125#c11 --- Comment #11 from Suse User <forumino(a)riseup.net> --- > BTW, did you activate or change any security features (such as selinux, apparmor) ? No. The only change I have made security-wise after the installation was to set in Yast->Security and Users->Miscellaneous Settings->File permissions from "Easy" to "Secure". But even before doing this the error messages related to vconsole were in the journal. Commenting out the line "MemoryDenyWriteExecute=yes" results in sucessfull messages only: # journalctl -b | grep vconsole Aug 01 18:54:45 acer systemd[1]: systemd-vconsole-setup.service: Succeeded. Aug 01 18:54:50 acer systemd[1]: systemd-vconsole-setup.service: Succeeded. Aug 01 18:55:00 acer systemd[1]: systemd-vconsole-setup.service: Succeeded. Aug 01 18:55:12 acer systemd[1]: systemd-vconsole-setup.service: Succeeded. Aug 01 18:55:22 acer systemd[1]: systemd-vconsole-setup.service: Succeeded. Aug 01 18:55:51 acer display-manager[1517]: /etc/vconsole.conf available Should I uncomment it or keep it commented? Or would it have any negative effects if uncommented? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1143147] AUDIT-0: calamares: polkit-untracked-privilege
by bugzilla_noreply＠novell.com 01 Aug '19

01 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=1143147 http://bugzilla.suse.com/show_bug.cgi?id=1143147#c6 --- Comment #6 from Mindaugas Baranauskas <opensuse.lietuviu.kalba(a)gmail.com> --- I did not tested yet in Wayland, but Calamares 3.2 series was supposed to support Wayland too: https://calamares.io/calamares-3.2-plan/ https://github.com/calamares/calamares/issues/747#issuecomment-309212388 https://www.debian.org/News/2019/20190706 - debian by default is with Wayland and live images includes Wayland. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1143870] New: futex-wait-multiple patchset for testing with Proton fsync
by bugzilla_noreply＠novell.com 01 Aug '19

01 Aug '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1143870 Bug ID: 1143870 Summary: futex-wait-multiple patchset for testing with Proton fsync Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: ahjolinna(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Valve just recently released proton 4.11 that features new fsnyc for improved multi-threaded gaming, which requires patches for the kernel to work proton changelog: https://github.com/ValveSoftware/Proton/wiki/Changelog#411-1 the forum announcement: https://steamcommunity.com/app/221410/discussions/0/3158631000006906163/ the kernel patch: https://lkml.org/lkml/2019/7/30/1399 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1123726] Package database refresh on a Debian client trigger the rebuilt of the channel repodata on the Spacewalk server
by bugzilla_noreply＠novell.com 01 Aug '19

01 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=1123726 http://bugzilla.suse.com/show_bug.cgi?id=1123726#c3 Philippe BIdault <philippe.bidault(a)getronics.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(philippe.bidault@ | |getronics.com) | --- Comment #3 from Philippe BIdault <philippe.bidault(a)getronics.com> --- Hi, Thanks for your reply !! Yes, indeed there are some 404 in the Apache proxy SSL log file. Here is the complete log following an "apt update" on the client : 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9/repodata/InRelease HTTP/1.1" 404 - 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9_updates/repodata/InRelease HTTP/1.1" 404 - 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9_security/repodata/InRelease HTTP/1.1" 404 - 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9/repodata/Release HTTP/1.1" 200 914 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9_updates/repodata/Release HTTP/1.1" 200 953 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9_security/repodata/Release HTTP/1.1" 200 977 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9/repodata/Release.gpg HTTP/1.1" 200 490 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9_updates/repodata/Release.gpg HTTP/1.1" 200 490 10.0.0.222 - - [01/Aug/2019:15:37:48 +0000] "GET ///XMLRPC/GET-REQ/debian-9_security/repodata/Release.gpg HTTP/1.1" 200 490 10.0.0.222 - - [01/Aug/2019:15:37:49 +0000] "GET ///XMLRPC/GET-REQ/debian-9/repodata/by-hash/SHA256/b78da06e87f1565010f76e0deec3913874eae6ce54db2e50810d49bcb238fc13 HTTP/1.1" 404 - 10.0.0.222 - - [01/Aug/2019:15:37:49 +0000] "GET ///XMLRPC/GET-REQ/debian-9/repodata/Packages.gz HTTP/1.1" 200 20562304 10.0.0.222 - - [01/Aug/2019:15:37:50 +0000] "GET ///XMLRPC/GET-REQ/debian-9_updates/repodata/by-hash/SHA256/4cbc1f114847c6366ce0ffcb8f8c85860e4ba3937a5ff5b41313361b69a514ba HTTP/1.1" 404 - 10.0.0.222 - - [01/Aug/2019:15:37:50 +0000] "GET ///XMLRPC/GET-REQ/debian-9_security/repodata/by-hash/SHA256/a18527b826007191d7eb015ce4f6ceff405381463cc1ab59416052a8d3ea820b HTTP/1.1" 404 - 10.0.0.222 - - [01/Aug/2019:15:37:50 +0000] "GET ///XMLRPC/GET-REQ/debian-9_updates/repodata/Packages.gz HTTP/1.1" 200 70758 10.0.0.222 - - [01/Aug/2019:15:37:50 +0000] "GET ///XMLRPC/GET-REQ/debian-9_security/repodata/Packages.gz HTTP/1.1" 200 1673678 So in fact, the 404 are for the InRelease, I am using Release file in the Channel Repodata. [root@spacewalk debian-9]# pwd /var/cache/rhn/repodata/debian-9 [root@spacewalk debian-9]# ls -lrt total 38000 -rw-r--r--. 1 root root 38896249 Aug 1 15:38 Packages_debroot -rw-r--r-- 1 root root 0 Aug 1 15:38 Packages -rw-r--r--. 1 root root 20 Aug 1 15:38 Packages.gz -rw-r--r-- 1 root root 862 Aug 1 15:38 Release -rw-r--r-- 1 root root 490 Aug 1 15:38 Release.gpg Do you think that I should create the InRelease file to avoid this issue of regenerating the repository metadata ? Regards, Philippe. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1143853] New: Can't access bootloader via YAST, error from perl-bootloader
by bugzilla_noreply＠novell.com 01 Aug '19

01 Aug '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1143853 Bug ID: 1143853 Summary: Can't access bootloader via YAST, error from perl-bootloader Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: eric.vanh(a)msg4.us QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Error message when (trying) accessing "BootLoader" in YAST: Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Caller: /usr/lib64/ruby/gems/2.5.0/gems/cfa-0.7.0/lib/cfa/augeas_parser.rb:455:in `report_activity_error!' Details: Augeas parsing error: Get did not match entire input at /etc/default/grub:11:0, lens /usr/share/augeas/lenses/dist/sysconfig.aug:65.12-.71: Background: Want to set my system to fips=1 /proc/sys/crypto doesn't exist (therefore fips_enabled doesn't either) Changed /etc/default/grab to add: fips=1 and boot=/dev/sda1 and root=/dev/sda3 Crash at boot: /boot/.vmlinuz-4.12(...)-default.hmac does not exist and at the end of the splash (I can't read earlier it goes too fast) I have: Starting dracut pre-pivot and cleanup hook... 888 dracut: FATAL: FIPS integrity test failed 888 dracut: Refusing to continue 888 dracut:-pre-pivot(435): Warning: /boot/.vmlinuz-4.12(...)-default.hmac does not exist 888 systemd-shutdown: .... 888 stoping disk 888 reboot: System halted So I have to "-e" the option at boot (change from fips=1 to fips=0) to be able to start the system. Since then, I can no longer access bootloader via YAST, But nanao /etc/default/grub and then upload it into boot via grub2-mkconfig -o /boot/grub2/grub.cfg works. I've cleaned up my /etc/default/grub file to a bare minimum (removed all fips option) and updated it via grub2-mkconfig -o /boot/grub2/grub.cfg but still can't access bootloader via YAST https://www.linuxquestions.org/questions/suse-opensuse-60/how-to-set-proc-s… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1074057] New: qemu can't capture keys properly under wayland
by bugzilla_noreply＠novell.com 01 Aug '19

01 Aug '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1074057 Bug ID: 1074057 Summary: qemu can't capture keys properly under wayland Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: gwang(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dimstar(a)opensuse.org, fcrozat(a)suse.com, qkzhu(a)suse.com, yfjiang(a)suse.com Found By: --- Blocker: --- Env: openSUSE Tumbleweed QEMU emulator version 2.10.0 Mutter 3.26.2-1.1 Steps: 1. Boot to the default GNOME session (by default wayland is enabled) 2. Launch libreoffice writer 3. Use QEMU monitor to send key "alt-f" Actual Result: There is no response on the libreoffice writer side. And if we press "alt-f" on the libreoffice writer directly, the File menu will be shown. It looks like qemu can't capture keys properly under wayland -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1143853] Can't access bootloader via YAST, error from perl-bootloader
by bugzilla_noreply＠novell.com 01 Aug '19

01 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=1143853 http://bugzilla.suse.com/show_bug.cgi?id=1143853#c1 David Diaz <dgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dgonzalez(a)suse.com Flags| |needinfo?(eric.vanh(a)msg4.us | |) --- Comment #1 from David Diaz <dgonzalez(a)suse.com> --- Hi Eric, thanks for the report. (In reply to Eric van Hollemeersch from comment #0) > Since then, I can no longer access bootloader via YAST, Could you please attach the YaST logs to have more information about what is happening? You can collect them running the `save_y2logs` command. More info available at https://en.opensuse.org/openSUSE:Report_a_YaST_bug#logfiles Thanks in advance! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1141522] VUL-0: CVE-2019-13602: vlc: An Integer Underflow in MP4_EIA608_Convert() in modules/demux/mp4/mp4.c allows remote attackers to cause a denial of service (heap-based buffer overflow and crash)
by bugzilla_noreply＠novell.com 01 Aug '19

01 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=1141522 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |obs:running:10715:important | |obs:running:10716:important -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1143549] VUL-1: CVE-2019-5459: vlc: integer underflow in VLC Media Player versions leads to an out-of-band read
by bugzilla_noreply＠novell.com 01 Aug '19

01 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=1143549 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |obs:running:10715:important | |obs:running:10716:important -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133290] LTO: vlc build fails
by bugzilla_noreply＠novell.com 01 Aug '19

01 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=1133290 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |obs:running:10716:important -- You are receiving this mail because: You are on the CC list for the bug.

1 0