February 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1052140] New: NetworkManager dispatcher script "nfs" is mounting nfs shares from fstab with option "noauto"
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1052140 Bug ID: 1052140 Summary: NetworkManager dispatcher script "nfs" is mounting nfs shares from fstab with option "noauto" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The NetworkManager dispatcher script "nfs" is mounting nfs shares from fstab, which have set option "noauto". In my environment this is a good thing, but it is not the expected behaviour. Perhaps we could have a new fstab option like "x-nm.mount" for nfs shares to explicitly control this behaviour? The reason for experimenting with fstab options for nfs shares is the really strange "cooperation" of systemd and NetworkManager. Having the "auto" option set and nfs.service is active, systemd tries to mount the shares on boot, before network is available. This gives lots of errors in the log, although NetworkManager succeeds in mounting the share, when running the dispatcher script. With "auto" in fstab and a deactivated nfs.service neither systemd nor NetworkManager are trying to mount nfs shares. With "noauto" in fstab and an activated nfs.service systemd ignores the shares, but NetworkManager's nfs dispatcher is mounting them nevertheless. I tried x-systemd.automount, too. This worked generally, but after a hibernate/resume cycle all nfs shares were inaccessible. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1161846] New: A library is missing for full KDE Plasma to work
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1161846 Bug ID: 1161846 Summary: A library is missing for full KDE Plasma to work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: prueba_hola(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 828298 --> http://bugzilla.opensuse.org/attachment.cgi?id=828298&action=edit Image for show Thermal Monitor KDE Plasma have Widget A Widget very popular is "Thermal Monitor" it provide: CPU Temp GPU Temp HDD Temp SSD Temp example: https://i.imgur.com/5HKRafc.png (the zone marked in orange, is Thermal Monitor) CPU and GPU will work without the library but HDD-SSD not The library missing is libqt4 The fix is easy, should be installed by default if you choose KDE in you opensuse Tumbleweed installer Note: I don't know if this issue happen or not in LEAP -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1161832] kernel: scsi_dh_alua: module verification failed: signature and/or required key missing - tainting kernel
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1161832 http://bugzilla.suse.com/show_bug.cgi?id=1161832#c3 --- Comment #3 from Suse User <suseino(a)riseup.net> --- *As of today = the system is up to date -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1161832] kernel: scsi_dh_alua: module verification failed: signature and/or required key missing - tainting kernel
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1161832 http://bugzilla.suse.com/show_bug.cgi?id=1161832#c2 Suse User <suseino(a)riseup.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(suseino(a)riseup.ne | |t) | --- Comment #2 from Suse User <suseino(a)riseup.net> --- > Does this still happen with the latest kernel? This was reported right after a system udpate, so - yes. And as of today - still yes: # uname -rvpio 5.4.14-1-default #1 SMP Thu Jan 23 08:54:47 UTC 2020 (fc4ea7a) i686 i386 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1160244] [META] -fno-common package failures
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1160244 Bug 1160244 depends on bug 1160287, which changed state. Bug 1160287 Summary: open-iscsi fails with -fno-common http://bugzilla.suse.com/show_bug.cgi?id=1160287 What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1160287] open-iscsi fails with -fno-common
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1160287 http://bugzilla.suse.com/show_bug.cgi?id=1160287#c5 Martin Liška <martin.liska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #5 from Martin Liška <martin.liska(a)suse.com> --- Then let's close it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1148788] VUL-0: CVE-2019-3687: permissions: easy profile allows everyone execute dumpcap and read all network traffic
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

1 0

[Bug 1161720] New: i915 hang continues in 5.4.12-1-default
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1161720 Bug ID: 1161720 Summary: i915 hang continues in 5.4.12-1-default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: cwdillon(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 828183 --> http://bugzilla.opensuse.org/attachment.cgi?id=828183&action=edit contents of /sys/class/drm/card0/error I dropped down to 5.4.12-default today when the latest Tumbleweed release came out and have already experienced graphical environment freeze with this error. Perhaps I misunderstood that Tumbleweed release managers applied the drm/i915/gt patch to 5.4.12 default kernel? I understand that this patch is not planned to be applied to 5.4 branch kernels by i915 drm managers. (https://www.spinics.net/lists/stable/msg351278.html) I hadn't experienced any freezes under 5.4.13 pre-release from Kernel:next (but I also don't any support for Bumblebee/NVIDIA in that kernel). Also attaching the contents of dmesg | grep i915: ``` [ 3.845376] i915 0000:00:02.0: vgaarb: deactivate vga console [ 3.847415] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 3.848292] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 4.529697] [drm] Initialized i915 1.6.0 20190822 for 0000:00:02.0 on minor 0 [ 4.681033] fbcon: i915drmfb (fb0) is primary device [ 4.725228] i915 0000:00:02.0: fb0: i915drmfb frame buffer device [ 9.671989] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 9.721605] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) [ 3021.917516] i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0 [ 3021.917518] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 3021.918523] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [ 3021.919248] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} [ 3021.919351] i915 0000:00:02.0: Resetting chip for hang on rcs0 [ 3021.921095] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} [ 3021.921814] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 16