February 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1114589] Add earlyoom package to the system
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1114589 http://bugzilla.suse.com/show_bug.cgi?id=1114589#c23 --- Comment #23 from Aleksey Kontsevich <akontsevich(a)gmail.com> --- (In reply to Mindaugas Baranauskas from comment #22) > EarlyOOM allows to set your own conditions in /etc/sysconfig/earlyoom , e.g. > you can set different percentage (or KB) for RAM and for SWAP, > also set whitelist and blacklist of programs. > > See configuration example in > https://build.opensuse.org/package/view_file/openSUSE:Factory/earlyoom/ > earlyoom.sysconfig > > -r option is for checking interval (seconds) > -m option is for RAM critical level (%) [or -M for KiB] > -s option is for SWAP critical level (%) [or -S for KiB] > more info: `man earlyoom` > > If you will find optimal values, we can set them as default -r is 3 -m set to 10 - 1.6 GB however it goes significantly below this level (about 700 MB) and system become unresponsive. if I do not want to swap at all, set -s to 0 or to 100? What happened to Linux?! In 2.x versions swap works perfect unloaded applications to swap and put them back immediately like a charm. Now forced to kill an app and restart it or even reboot PC to have it back. What is wrong here? Any way to fix? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1114589] Add earlyoom package to the system
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1114589 http://bugzilla.suse.com/show_bug.cgi?id=1114589#c22 --- Comment #22 from Mindaugas Baranauskas <opensuse.lietuviu.kalba(a)gmail.com> --- EarlyOOM allows to set your own conditions in /etc/sysconfig/earlyoom , e.g. you can set different percentage (or KB) for RAM and for SWAP, also set whitelist and blacklist of programs. See configuration example in https://build.opensuse.org/package/view_file/openSUSE:Factory/earlyoom/earl… -r option is for checking interval (seconds) -m option is for RAM critical level (%) [or -M for KiB] -s option is for SWAP critical level (%) [or -S for KiB] more info: `man earlyoom` If you will find optimal values, we can set them as default -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1114589] Add earlyoom package to the system
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1114589 http://bugzilla.suse.com/show_bug.cgi?id=1114589#c21 --- Comment #21 from Aleksey Kontsevich <akontsevich(a)gmail.com> --- (In reply to Mindaugas Baranauskas from comment #20) > Although now this package exist in default openSUSE Factory repository, > it does not mean it will be pre-installed (auto-installed) with some pattern. Mindaugas, however earlyoom does not work for me: my custom app has memory leak and it eats all the memory very fast and earlyoom does not kill it. After this I forced to kill it manually then to kill and restart plasma and firefox as they unloaded to swap and become unresponsive. Very inconvenient! Any ideas? Change some settings or earlyoom just unable to kill some apps? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162420] New: [Build 20200130] Vagrant not compatible to virtualbox 6.1
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1162420 Bug ID: 1162420 Summary: [Build 20200130] Vagrant not compatible to virtualbox 6.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1160594/modules/add_ box_virtualbox/steps/29 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_vagrant@64bit fails in [add_box_virtualbox](https://openqa.opensuse.org/tests/1160594/modules/add_b… ## Test suite description Maintainer: dancermak. Test vagrant, vagrant plugins and the vagrant boxes ## Reproducible Fails since (at least) Build [20191217](https://openqa.opensuse.org/tests/1117038) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1123248] ACPI error
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1123248 http://bugzilla.suse.com/show_bug.cgi?id=1123248#c10 Borislav Petkov <bpetkov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bpetkov(a)suse.com --- Comment #10 from Borislav Petkov <bpetkov(a)suse.com> --- Do those messages go away if you add: "blacklist gpio_ich" to /etc/modprobe.d/50-blacklist.conf and reboot? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1020664] USB Bluetooth stops working after "reset full-speed USB device number 3 using xhci_hcd"
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1020664 http://bugzilla.suse.com/show_bug.cgi?id=1020664#c20 Borislav Petkov <bpetkov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |bpetkov(a)suse.com Resolution|--- |NORESPONSE --- Comment #20 from Borislav Petkov <bpetkov(a)suse.com> --- Looks forgotten. Feel free to reopen if still of interest. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1106831] New: kernel crash when unloading bugdet_ci module
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1106831 Bug ID: 1106831 Summary: kernel crash when unloading bugdet_ci module Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 781630 --> http://bugzilla.opensuse.org/attachment.cgi?id=781630&action=edit journal excerpt After updating from openSUSE Leap 42.3 to 15.0 the system always crashes when unloading the budget_ci dvb module - see attachement. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1159706] New: puddletag - ASSERT: "PyList_CheckExact(py)" in file ../../qpy/QtCore/qpycore_chimera.cpp
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1159706 Bug ID: 1159706 Summary: puddletag - ASSERT: "PyList_CheckExact(py)" in file ../../qpy/QtCore/qpycore_chimera.cpp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 826644 --> http://bugzilla.opensuse.org/attachment.cgi?id=826644&action=edit coredump information Hi, using AcoustID in puddletag-1.2.40git.20190609T143128~aab842a-1.1.noarch on openSUSE Tumbleweed (latest snapshot) gives: ASSERT: "PyList_CheckExact(py)" in file ../../qpy/QtCore/qpycore_chimera.cpp, lin e 1638 This happens after the actual file(s) have been identified by AcoustID and the file list should be fetched. See attachement for the complete coredump information. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1160722] New: kdump fails to load
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1160722 Bug ID: 1160722 Summary: kdump fails to load Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with the latest Tumbleweed snapshot 20200110 kdump fails to load. Not sure, what "Permission denied" means in this context. load.sh[1509]: kexec_load failed: Permission denied load.sh[1509]: entry = 0x4ace9c740 flags = 0x3e0001 load.sh[1509]: nr_segments = 8 load.sh[1509]: segment[0].buf = 0x1912d20 load.sh[1509]: segment[0].bufsz = 0x70 load.sh[1509]: segment[0].mem = 0x4a1000000 load.sh[1509]: segment[0].memsz = 0x1000 load.sh[1509]: segment[1].buf = 0x191ad60 load.sh[1509]: segment[1].bufsz = 0x168 load.sh[1509]: segment[1].mem = 0x4a1001000 load.sh[1509]: segment[1].memsz = 0x1000 load.sh[1509]: segment[2].buf = 0x7f151aeca010 load.sh[1509]: segment[2].bufsz = 0x140e00c load.sh[1509]: segment[2].mem = 0x4a85f1000 load.sh[1509]: segment[2].memsz = 0x140f000 load.sh[1509]: segment[3].buf = 0x7f151c2dd610 load.sh[1509]: segment[3].bufsz = 0x89aaf0 load.sh[1509]: segment[3].mem = 0x4a9a00000 load.sh[1509]: segment[3].memsz = 0x3350000 load.sh[1509]: segment[4].buf = 0x190c6c0 load.sh[1509]: segment[4].bufsz = 0x4826 load.sh[1509]: segment[4].mem = 0x4ace97000 load.sh[1509]: segment[4].memsz = 0x5000 load.sh[1509]: segment[5].buf = 0x1905310 load.sh[1509]: segment[5].bufsz = 0x70e0 load.sh[1509]: segment[5].mem = 0x4ace9c000 load.sh[1509]: segment[5].memsz = 0x9000 load.sh[1509]: segment[6].buf = 0x1903ff0 load.sh[1509]: segment[6].bufsz = 0xc00 load.sh[1509]: segment[6].mem = 0x4acea5000 load.sh[1509]: segment[6].memsz = 0x4000 load.sh[1509]: segment[7].buf = 0x7f151ae72010 load.sh[1509]: segment[7].bufsz = 0x57000 load.sh[1509]: segment[7].mem = 0x4acea9000 load.sh[1509]: segment[7].memsz = 0x57000 kernel: ima: impossible to appraise a kernel image without a file descriptor; try using kexec_fi le_load syscall. kdump[1879]: FAILED to load kdump kernel: /sbin/kexec -p /boot/vmlinuz-5.4.7-1-default --append= " quiet no_console_suspend consoleblank=0 systemd.log_target=kmsg log_buf_len=10M printk.devkmsg=on modprobe.blacklist=n vidia modprobe.blacklist=nvidia_uvm modprobe.blacklist=nvidia_drm modprobe.blacklist=nvidia_modeset modprobe.blacklist=n ouveau modprobe.blacklist=nv elevator=deadline sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory nokaslr numa=off irqpoll nr_cpus=1 root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0 panic=1" --initrd=/boo t/initrd-5.4.7-1-default-kdump , Result: kexec_load failed: Permission denied entry = 0x4ace9c740 flags = 0x3e0001 nr_segments = 8 segment[0].buf = 0x1912d20 segment[0].bufsz = 0x70 segment[0].mem = 0x4a1000000 segment[0].memsz = 0x1000 segment[1].buf = 0x191ad60 segment[1].bufsz = 0x168 segment[1].mem = 0x4a1001000 segment[1].memsz = 0x1000 segment[2].buf = 0x7f151aeca010 segment[2].bufsz = 0x140e00c segment[2].mem = 0x4a85f1000 segment[2 systemd[1]: kdump.service: Main process exited, code=exited, status=255/EXCEPTION systemd[1]: kdump.service: Failed with result 'exit-code'. It succeeds at early startup, though: kdump[1578]: Loaded kdump kernel: /sbin/kexec -p /boot/vmlinuz-5.4.7-1-default --append=" quiet no_console_suspend consoleblank=0 systemd.log_target=kmsg log_buf_len=10M printk.devkmsg=on modprobe.blacklist=nvidia modprobe.blacklist=nvidia_uvm modprobe.blacklist=nvidia_drm modprobe.blacklist=nvidia_modeset modprobe.blacklist=nouveau modprobe.blacklist=nv elevator=deadline sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory nokaslr numa=off irqpoll nr_cpus=1 root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0 panic=1" --initrd=/boot/initrd-5.4.7-1-default-kdump -s, Result: systemd[1]: Started Load kdump kernel early on startup. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1154908] New: nfs dispatcher script references removed nfs.service
by bugzilla_noreply＠novell.com 01 Feb '20

01 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1154908 Bug ID: 1154908 Summary: nfs dispatcher script references removed nfs.service 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: --- Even NetworkManager 1.18.4 from Tumbleweed snaphot 20191018 still references nfs.service, which has been removed some time ago resulting in "Failed to get unit file state for nfs.service: No such file or directory" and an unusable dispatcher routine. -- You are receiving this mail because: You are on the CC list for the bug.

1 2