February 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1067988] xen net/sched/sch_generic crash
by bugzilla_noreply＠novell.com 04 Feb '19

04 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=1067988 alexis Pellicier <pellice(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #795886|application/octet-stream |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1067988] xen net/sched/sch_generic crash
by bugzilla_noreply＠novell.com 04 Feb '19

04 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=1067988 http://bugzilla.novell.com/show_bug.cgi?id=1067988#c19 --- Comment #19 from alexis Pellicier <pellice(a)gmail.com> --- Created attachment 795886 --> http://bugzilla.novell.com/attachment.cgi?id=795886&action=edit kernel logs -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124091] g++ internal compiler error: Illegal instruction
by bugzilla_noreply＠novell.com 04 Feb '19

04 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1124091 http://bugzilla.suse.com/show_bug.cgi?id=1124091#c4 --- Comment #4 from Markku Pulkkinen <markku.j.pulkkinen(a)gmail.com> --- The failure can be repeated by doing following test at console terminal: echo '#include <limits>' > test.c ; g++ -c test.c I suspect that GNU compiler tools or libraries (gmp, mpfr) are build for higher march than Sandybridge. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124091] g++ internal compiler error: Illegal instruction
by bugzilla_noreply＠novell.com 04 Feb '19

04 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1124091 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 1123642] When write some notes on Cyrillic in the Guest summary form for KVM and shutdown the guest then it can not start
by bugzilla_noreply＠novell.com 04 Feb '19

04 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1123642 http://bugzilla.suse.com/show_bug.cgi?id=1123642#c4 --- Comment #4 from James Fehlig <jfehlig(a)suse.com> --- (In reply to Krasimir Ivanov from comment #3) > Today I have checked it again as you suggested. You didn't answer my question in #2 about libvirt-daemon-hooks package. Could you please check that? Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120087] NFS server fails after a suspend system
by bugzilla_noreply＠novell.com 04 Feb '19

04 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1120087 http://bugzilla.suse.com/show_bug.cgi?id=1120087#c8 --- Comment #8 from Neil Brown <nfbrown(a)suse.com> --- Ok, that explains it - or most of it. There is a dependencies set up between exported filesystems and the nfs server. The intention is to make sure the nfs server doesn't start until those filesystems are mounted, but as a side effect, the nfs server is stopped in the filessytems get unmounted. That isn't really ideal. I'll see if I can find a way to fix that. Your real issue is why does the usb device disappear on suspend. That is probably what you want as a default, because it is quite possible that you might unplug the device and re-plug it while Linux is suspended. So Linux needs to assume that it has changed. If your intention is to keep the USB drive plugged in, then we should be able to tell Linux that. See: https://www.kernel.org/doc/html/v4.20/driver-api/usb/persist.html you should be able to set the device to "persist" across suspend/resume. That should leave the filesystem mounted and nfsd running. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124071] New: [Build 20190201] openQA test fails in podman_image
by bugzilla_noreply＠novell.com 03 Feb '19

03 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124071 Bug ID: 1124071 Summary: [Build 20190201] openQA test fails in podman_image Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/845039/modules/podma n_image/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: coolo(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com, rbrown(a)suse.com Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-docker_image@64bit fails in [podman_image](https://openqa.opensuse.org/tests/845039/modules/podman_image… ## Test suite description Maintainer: fvogt(a)suse.com This test's main job is to configure a docker host and install the docker image built within the current product and test it. ## Reproducible Fails since (at least) Build [20190129](https://openqa.opensuse.org/tests/843889) ## Expected result Last good: [20190126](https://openqa.opensuse.org/tests/841735) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?machine=64bit&distri=opens… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1124082] New: Please add CPU governor setting to YaST Kernel Settings module
by bugzilla_noreply＠novell.com 03 Feb '19

03 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124082 Bug ID: 1124082 Summary: Please add CPU governor setting to YaST Kernel Settings module Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: sb56637(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Hi there, I've been recently trying to set the CPU governor to "performance" for a low-latency audio workstation. While manually setting the governor is easy enough, making that change persistent after rebooting is no longer an easy or straightforward process, and much of the documentation available online is no longer applicable. It appears that the best way to accomplish this is by adding a new systemd service, which really feels like overkill. Since YaST Kernel Settings already has an option to choose the I/O scheduler, could you also please add an option to choose the governor? Thanks for considering this. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1102075] [Build 20180719] openQA test fails in rails
by bugzilla_noreply＠novell.com 03 Feb '19

03 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1102075 http://bugzilla.suse.com/show_bug.cgi?id=1102075#c7 --- Comment #7 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1102075) was mentioned in https://build.opensuse.org/request/show/670866 Factory / rubygem-rails-5.2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 928328] New: VUL-1: libnettle: off-by-one in the test suite
by bugzilla_noreply＠novell.com 03 Feb '19

03 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=928328 Bug ID: 928328 Summary: VUL-1: libnettle: off-by-one in the test suite Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: vpereira(a)novell.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Address Sanitizer found a problem in the des-compat-test.c the line: for (i=0; i<(NUM_TESTS-1); i++) should be: for (i=0; i<(NUM_TESTS-2); i++) we found a simila problem, in the 13.2, however in Factory it was already fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 10